Closed antonysouthworth-halter closed 12 months ago
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. 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.
Community Note
Description
The
aws_s3_bucket_object
resource type allows us to manage individual objects in an S3 bucket with Terraform. However, one part which is missing from this resource is the ability to set specific ACLs for the object. The resource type only allows you to specify a canned ACL (e.g.private
/public-read
/bucket-owner-full-control
, docs). There does not appear to be a way to set more specific ACLs.Use case: Creating an Elasticache Redis cluster from a local backup file. This requires uploading the backup file to S3 and ensuring the bucket and object have sufficient ACLs such that the Elasticache service can read the file.
At the moment, I get around this by using the AWS CLI with
provisioner "local-exec"
, which is not ideal because Terraform doesn't know anything about what local-exec does.I guess the ideal would be to add a
grant
directive that basically behaves like the one foraws_s3_bucket
.New or Affected Resource(s)
Potential Terraform Configuration
References
(none)