Failed to create S3 bucket. AWS Portal: The bucket does not allow ACLs.
Hello
This is my first question here because I am stuck. I am trying to get Deadline AWS Portal Link and AWS Asset Server up and running. I remember being successful about two years ago. I've been fuzzing around for the past two days and now I am confronted with an error which I haven't seen back then.
I am running Deadline 10.2.0.10 components. I know it's not the latest and that it could be a source of error, however, that's the version I'm stuck with for the time being.
I can see that the buckets get created AWS S3 and I can also enable ACL's but AWS Portal and Asset Server keep creating new ones. Please help.
Thanks and best regards, Michael
- 最新
- 最多得票
- 最多評論
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.
相關內容
AWS 官方已更新 2 年前- AWS 官方已更新 3 年前
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!