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

Add default AES256 encryption and enable versioning for buckets in audit-logs, release-pipeline, and staging-bucket stacks #3673

Merged
merged 1 commit into from
May 4, 2023

Conversation

amogh09
Copy link
Contributor

@amogh09 amogh09 commented May 4, 2023

Summary

Add default AES256 encryption and enable versioning for buckets in audit-logs, release-pipeline, and staging-bucket CFN templates. AES256 Encryption is already enabled on the buckets by default so the encryption change in the stack template should be a no-op. Versioning will be enabled when the stack is updated.

Only the release-pipeline stack actually exists, so we will only update that stack.

Implementation details

Update the CFN templates with BucketEncryption and VersioningConfiguration properties.

Testing

New tests cover the changes: no

Description for the changelog

Add default AES256 encryption and enable versioning for buckets in audit-logs, release-pipeline, and staging-bucket stacks.

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@amogh09 amogh09 changed the base branch from master to dev May 4, 2023 18:55
@amogh09 amogh09 marked this pull request as ready for review May 4, 2023 19:16
@amogh09 amogh09 requested a review from a team as a code owner May 4, 2023 19:16
@amogh09 amogh09 merged commit 04e734a into aws:dev May 4, 2023
@Realmonia Realmonia mentioned this pull request May 9, 2023
Realmonia pushed a commit to Realmonia/amazon-ecs-agent that referenced this pull request May 16, 2023
Realmonia pushed a commit to Realmonia/amazon-ecs-agent that referenced this pull request May 21, 2023
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 this pull request may close these issues.

4 participants