The support rep had us try using the IAM policy from the Immutable Buckets section on this page https://www.veeam.com/kb3151 but that didn't work either.
The standard read-only keys work fine with new buckets created in 12.3.1 that don’t have ‘Automatic Bucket Creation’ enabled so perhaps it's a new bug with v12.3.x which first became more visible in 12.3.1 due to the auto bucket creation being enabled by default for all new S3 compatible repositories.
Perhaps the read-only key functionality wasn't regression tested with a newly created bucket with this feature enabled?
The standard read-only keys work fine with new buckets created in 12.3.1 that don’t have ‘Automatic Bucket Creation’ enabled so perhaps it's a new bug with v12.3.x which first became more visible in 12.3.1 due to the auto bucket creation being enabled by default for all new S3 compatible repositories.
Perhaps the read-only key functionality wasn't regression tested with a newly created bucket with this feature enabled?
Statistics: Posted by gtelnet — Apr 07, 2025 8:26 pm
