- Newest
- Most votes
- Most comments
Hi THere
This is likely because of the new default behavior for S3 buckets.
I think you will need to update Deadline. See https://forums.thinkboxsoftware.com/t/alert-aws-portal-bucket-cannot-have-acls-set-with-objectownership/30592 and https://docs.thinkboxsoftware.com/products/deadline/10.2/1_User%20Manual/manual/release-notes.html#deadline-release
We are aware of an issue when trying to launch AWS Portal infrastructure where it will rollback with a error “Bucket cannot have ACL set with ObjectOwnership’s BucketOwnerEnforced”. The error relates to Amazon S3 updating the default bucket settings to automatically enable Block Public Access (BPA) and disable Access Control Lists (ACLs) 6. We have released Deadline (10.2.1.1) 7 which fixes the above issue by disabling the ACL by default on new S3 buckets.
I'm not familiar with this app but is there an option to brig your own bucket as a workaround? If so, maybe you can manually configure the bucket beforehand.
Relevant content
- Accepted Answerasked 5 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
Thanks a lot Matt-B! These announcements seem almost too obvious to overlook. And yet... Really happy that you pointed me in the right direction! Cheers!