-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Support for Object ACL's on S3 Object Creation #7744
Comments
Seems like a reasonable thing to provider here, thanks! |
+1 I find this a rather large omission! |
Closed via #8091 |
Issue #8091 addresses canned ACL's, but not object or bucket ACLs that can be set through the |
Can this be re-opened? |
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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Currently, when you control the lifecycle of a bucket with Terraform, the only place that you are able to set the ACL is at the bucket level, through the
aws_s3_bucket
resource. If you create a private bucket and want to upload an object that is publicly accessible, which is common, you are stuck to using the AWS Console to mark that object as public or edit the ACL for it.The AWS CLI supports a
put-object-acl
command which allows you to edit the ACL of an object that already exists in a bucket. Could something similar be implemented so that object permissions could be modified through Terraform?The text was updated successfully, but these errors were encountered: