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

Enhancement: include expected_bucket_owner #226

Closed
houserx-jmcc opened this issue Apr 3, 2024 · 0 comments · Fixed by #238
Closed

Enhancement: include expected_bucket_owner #226

houserx-jmcc opened this issue Apr 3, 2024 · 0 comments · Fixed by #238

Comments

@houserx-jmcc
Copy link
Contributor

Describe the Feature

From AWS docs:

Because Amazon S3 identifies buckets based on their names, an application that uses an incorrect bucket name in a request could inadvertently perform operations against a different bucket than expected. To help avoid unintentional bucket interactions in situations like this, you can use bucket owner condition. Bucket owner condition enables you to verify that the target bucket is owned by the expected AWS account, providing an additional layer of assurance that your S3 operations are having the effects you intend.

Expected Behavior

The config for aws_s3_bucket_server_side_encryption_configuration includes the ability to specify expected_bucket_owner.

Use Case

See docs quote above, recommended AWS best practice to ensure the correct bucket/account is being accessed.

Describe Ideal Solution

This is surfaced via a variable or automatically set based on the account context if available.

Alternatives Considered

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants