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

Warning on S3 Bucket Encryption no longer makes sense #633

Open
miguelut opened this issue Feb 14, 2025 · 0 comments
Open

Warning on S3 Bucket Encryption no longer makes sense #633

miguelut opened this issue Feb 14, 2025 · 0 comments

Comments

@miguelut
Copy link

Issue #278 is really no longer applicable and W41 should be removed. All S3 buckets encrypt objects by default with the SSE-S3/AES256 algorithm if no encryption is specified when the bucket is created.

This also creates an issue with CloudFormation templates that will be deployed in the Security OU created by AWS Control Tower because the elective control AWS-GR_AUDIT_BUCKET_ENCRYPTION_ENABLED is enabled by default in that account. Having that control puts an explicit deny on s3:PutEncryptionConfiguration for everyone except the Control Tower service role. So CloudFormation templates that conform to this rule will fail in the Security OU, whereas non-conforming templates will succeed and still result in encrypted buckets.

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

No branches or pull requests

1 participant