Skip to content
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

Closed
blakestoddard opened this issue Jul 21, 2016 · 6 comments
Closed

Support for Object ACL's on S3 Object Creation #7744

blakestoddard opened this issue Jul 21, 2016 · 6 comments

Comments

@blakestoddard
Copy link
Contributor

Affected Resource(s)

Please list the resources as a list, for example:

  • aws_s3_bucket_object

Terraform Configuration Files

resource "aws_s3_bucket_object" "object" {
    bucket = "bucket-name"
    key = "test.txt"
    source = "./test.txt"
}.

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?

@catsby
Copy link
Contributor

catsby commented Jul 21, 2016

Seems like a reasonable thing to provider here, thanks!

@JonRoma
Copy link

JonRoma commented Jul 26, 2016

+1

I find this a rather large omission!

@stack72
Copy link
Contributor

stack72 commented Aug 10, 2016

Closed via #8091

@stack72 stack72 closed this as completed Aug 10, 2016
@dbeckham
Copy link

dbeckham commented Sep 8, 2016

Issue #8091 addresses canned ACL's, but not object or bucket ACLs that can be set through the put-object-acl or put-bucket-acl API commands, which this ticket is specifically asking for.

@yermulnik
Copy link

Can this be re-opened?

@ghost
Copy link

ghost commented Apr 7, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants