docs(logs): clarify encryption default for log groups#21060
Merged
mergify[bot] merged 2 commits intoaws:mainfrom Jul 14, 2022
Merged
docs(logs): clarify encryption default for log groups#21060mergify[bot] merged 2 commits intoaws:mainfrom
mergify[bot] merged 2 commits intoaws:mainfrom
Conversation
The default encryption for CloudWatch Logs is not performed via a KMS AWS-managed key which is what is usually implied by "master key". Updating the documentation to clarify that this is server-side encryption hopefully clarifies why "KMS key ID" shows as "-" in the Console for created Log Groups and why the `cloudwatch-log-group-encrypted` Config Rule shows as non-compliant.
|
|
TheRealAmazonKendra
approved these changes
Jul 14, 2022
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The default encryption for CloudWatch Logs is not performed via a KMS
AWS-managed key which is what is usually implied by "master key".
Updating the documentation to clarify that this is server-side
encryption hopefully clarifies why "KMS key ID" shows as "-" in the
Console for created Log Groups and why the
cloudwatch-log-group-encryptedConfig Rule shows as non-compliant.Based on https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/data-protection.html#encryption-rest
All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integto deploy the infrastructure and generate the snapshot (i.e.yarn integwithout--dry-run)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license