You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Describe the Feature
From AWS docs:
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
The text was updated successfully, but these errors were encountered: