-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Allow to enforce object ownership on S3 buckets #26566
Comments
I can try to take a look at this if that's alright. |
@wiegandf does the following not work? If not, that's a bug resource "aws_s3_bucket" "b" {
bucket = "my-tf-test-bucket"
}
resource "aws_s3_bucket_ownership_controls" "b" {
bucket = aws_s3_bucket.b.bucket
rule {
object_ownership = "BucketOwnerEnforced"
}
} |
Creating them in separate resources doesn't work when you want to enforce BucketOwnerEnforced on all new s3 buckets. |
Hey sorry haven't had time to work on this if someone else wants to. @wiegandf One question for someone else that wants to pick this up, should there be a default value for this (or is one set by AWS?) if this is not set on bucket creation? |
If you go to the AWS console, you can see that BucketOwnerEnforced is the default object ownership when creating s3 buckets (with ACLs disabled). |
28353 |
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
We would like to follow the best practices by AWS and disable ACL and enforce object ownership. See references below. I know that we could set it with aws_s3_bucket_ownership_controls, but this would not allow to enforce bucket creation with e.g. BucketOwnerEnforced (as described in the AWS example).
New or Affected Resource(s)
Potential Terraform Configuration
This could also be the default value when leaving acl undefined. Currently, acl is deprecated but is
private
by default.References
The text was updated successfully, but these errors were encountered: