-
-
Notifications
You must be signed in to change notification settings - Fork 121
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bucket cannot have ACLs set with ObjectOwnership's BucketOwnerEnforced setting #96
Comments
I have opened a PR to fix the issue on the latest version of Cloudposse's S3 Bucket module. This implicates on this module having to use the Cloudposse's latest S3 Log Storage |
The fix for this issue was merged on the s3 bucket module, but we still need to make sure this gets to S3 Log Storage either as a fix for the old version OR as a new release for the latest one. If only the latter happens, then we need to give this PR an attention to actually get rid of the issue |
The same issue happens with https://github.com/cloudposse/terraform-aws-cloudfront-s3-cdn as well. |
Bumping this: terraform-aws-cloudfront-cdn/main.tf Line 18 in e6a8c2a
to 1.4.0
will fix the issue for new infrastructure (I have tested this). According to the documentation we should be able to bump up to this new module with the minimum of fuss for existing infrastructure as well, as from https://github.com/cloudposse/terraform-aws-s3-log-storage/releases/tag/1.0.0 |
Hey @scott-doyland-burrows, thanks for sharing that! I'll test it when able. |
Found a bug? Maybe our Slack Community can help.
Describe the Bug
Cannot create a new Cloudfront CDN using this module, the
apply
command fails with the following error:Expected Behavior
terragrunt apply
command should not fail with that error.Steps to Reproduce
Steps to reproduce the behavior:
terragrunt apply
with the bare minimum inputsScreenshots
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:
Additional Context
From my initial research, it looks like AWS changed the default value for new S3 Buckets' ownership controls to
BucketOwnerEnforced
. This creates a conflict that prevents the Bucket from being created, sinceBucketOwnerEnforced
conflicts with having an ACL defined on the Bucket.The text was updated successfully, but these errors were encountered: