-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Ability to manage S3 Bucket Ownership Controls #94
Comments
As a work around for the race condition could you use |
As I have mentioned on the description, yes, I have considered using |
I am also waiting for this feature. I've made this PR #101. Feel free to edit if necessary. |
#101 has been just merged and v2.8.0 has been just released. I also added |
Setting |
Note, AWS added new functionality related to S3 object ownership during 2021 re:invent, which allows enforcing object ownership. The implementation in this module was created three months prior and does not yet support enforcement. |
Understood. Is there an issue open concerning this feature request I could subscribe to? |
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. |
Is your request related to a new offering from AWS?
Yes: https://docs.aws.amazon.com/AmazonS3/latest/userguide/about-object-ownership.html#enable-object-ownership
I would like to ensure that objects placed into an S3 bucket in one AWS account by a principal from another AWS account are set to be owned by the bucket owner, even if AWS principal from another account did not explicitly set the
bucket-owner-full-control
canned ACL on the object during upload.Feature supported by AWS provider for Terraform since v3.10.0:
Is your request related to a problem? Please describe.
Creating the
aws_s3_bucket_ownership_controls
resource outside of this module causes a race condition withaws_s3_bucket_public_access_block
resource and possiblyaws_s3_bucket_policy
, that are optionally created by this module, requiring two-step apply.Describe the solution you'd like.
I'd like to see an optional
aws_s3_bucket_ownership_controls
resource added to this module, creation and configuration of which can be controlled by an input variable.Describe alternatives you've considered.
I have tried creating the
aws_s3_bucket_ownership_controls
resource outside of this module, but it tends to have a race condition withaws_s3_bucket_public_access_block
resource optionally created by this module, requiring two-step apply. Currently there's no way to wait for theaws_s3_bucket_public_access_block
oraws_s3_bucket_policy
creation, since they are not exposed as output, so I feel adding optionalaws_s3_bucket_ownership_controls
resource to this module would be a cleaner solution, allowing for explicit dependencies to be specified.Additional context
Possible module variable:
BucketOwnerPreferred
orObjectWriter
string
null
The text was updated successfully, but these errors were encountered: