Any new buckets you create will now always automatically • be set to private • not allow ACLs to be set

This is a breaking change and if the Lucee tests are creating any sort of temp buckets and then setting items into them, additional work is now required to get a bucket that is • public by default • or allows ACLs

I had to update the Ortus s3sdk library last week as its tests started failing due to this

Glancing at the error messages you put in the ticket, that's exactly what you're hitting 🙂

I know what needs to change in S3, but I'm not sure how Lucee interacts with S3. The Ortus S3sdk just makes directly HTTP calls to the S3 REST API. If Lucee is bundling the Java sdk for S3, I'm not 100% sure what the changes will look like for you.

You will need to change the

objectOwnership

of the bucket from its new default of

BucketOwnerEnforced

(which means the owner of the bucket enforces the ACLs, and objects in the bucket are not allowed to set their own ACL to

ObjectWriter

. This can be done when the bucket is created. (It's the

x-amz-object-ownership

HTTP header in the REST API)

Secondly, if you intend to set any public ACLs, you'll need to modify one or all of these 4 bucket settings • BlockPublicAcls • IgnorePublicAcls • BlockPublicPolicy • RestrictPublicBuckets The annoying this is these can NOT be set when creating the bucket (at least not in the AWS S3 REST API), so in my S3sdk I had to made a second call to set the

PublicAccessBlockConfiguration

settings on the bucket. Once this is done, THEN the bucket can also be updated to have a public default ACL as well if you need (this is 3 total calls if you're keeping track)

If you're using the Java S3 SDK, they may have this all wrapped up into a single call to the SDK. That's how I did it in the Ortus SDK to keep backwards compat, but basically that's what you need to do in order to be able to set object ACLs in a new bucket.

thanks @bdw429s