Other Articles
- IAM - Enable User MFA
- IAM - Enforce Key Rotation
- IAM - Enforce Active Key Limit
- IAM - Disable Unused User Credentials
- IAM - Enforce Group Permission
- IAM - Enforce Password Length
- IAM - Prohibit Password Reuse
- IAM - Check Root Access Keys Existence
- IAM - Enable Root MFA
- IAM - Establish Support Role
- IAM - Enable Key Rotation
- Purge Expired Certificates
- EC2 Volume – Enable EBS Volume Backup
- EC2 Volume – Enable EBS Encryption
- EFS – Enable EFS Storage Backup
- S3 Bucket – Enable S3 Bucket Versioning
- S3 Bucket – Enable S3 Bucket Encryption
- S3 Bucket – Block S3 Bucket Public Access
- RDS DB Instance – Encryption of Storage
- RDS DB Instance – Enable Deletion Protection
- RDS DB Instance – Enable Auto Minor Version Upgrade
- DynamoDB Table – Enable Table Encryption
- DynamoDB Table – Enable Table Point In Time Recovery
- DynamoDB Table – Enable Table Deletion Protection
- EKS Cluster – Enable Secrets Encryption
- OpenSearch Domain – Enable Encryption at Rest
- RDS DB Cluster – Retain Backups for 7 Days
- RDS DB Cluster – Encryption of Storage
- RDS DB Cluster – Enable Deletion Protection
- EC2 Instance – Monitor CPU Utilization
- ECS Service – Monitor CPU Utilization
- ECS Service – Monitor Memory Utilization
- RDS DB Instance – Monitor Free Storage Space
- RDS DB Instance – Monitor CPU Utilization
- SQS Queue – Monitor Message Age
- SQS Queue – Monitor Message Visibility
- DynamoDB Table – Monitor Table Read Capacity
- DynamoDB Table – Monitor Table Write Capacity
- DynamoDB Table – Monitor Table Latency
- Enable CloudTrail
- Encrypt CloudTrail Logs
- EC2 VPC – Ensure Flow Logs are Enabled
- EKS Cluster – Enable Control Plane Logging
- CloudWatch Log Group – Configure Retention
- Load Balancer – Enable Access Logs
- RDS DB Instance – Block Public Access
- EC2 Security Group – Restrict Public SSH and RDP Access
- EC2 Security Group – Restrict Public Database Access
- EKS Cluster – Restrict Public Endpoint
- EC2 VPC – Restrict Default Security Group Traffic
- Load Balancer – Redirect HTTP Traffic to HTTPS
- Load Balancer – Use Strong TLS Policies
- OpenSearch Domain – Enable Node-to-Node Encryption
- OpenSearch Domain – Enforce HTTPS
- OpenSearch Domain – Restrict Public Access
- RDS DB Cluster – Block Public Access
- EC2 Instance – Enable Deletion Protection
- ECS Service – Enable Auto Scaling
- Load Balancer – Enable Deletion Protection
- Enable AWS Security Hub
- Enable GuardDuty
- CloudFront Distribution – Enforce HTTPS for Viewers
- CloudFront Distribution – Require TLS 1.2 for Viewers
- CloudFront Distribution – Associate a WAF Web ACL
- CloudFront Distribution – Protect S3 Origin Access
- KMS Key – Avoid Pending Deletion
- SNS Topic – Enable Encryption
- SNS Topic – Restrict Topic Policy Access
CloudWatch Log Group – Enable KMS Encryption
Secure Configuration Checks > AWS
This check ensures that every Amazon CloudWatch log group is encrypted with an AWS KMS key. Logs often hold sensitive data, so you should control who can read them.
Check Details
- Resource: CloudWatch Log Group
- Check: Enable log group KMS encryption (
KmsEncryptionEnabled) - Risk: Log data cannot be protected with your own key and key policy
Remediation via AWS Console
-
Open the Amazon CloudWatch console.
-
Navigate to Logs > Log Management and select the affected log group.
-
Check the KMS key ID in the log group details to verify whether a KMS key is associated.
-
For new log groups, click Create log group, provide a name, select the required KMS key, and create the log group.
Note: AWS does not support associating a KMS key with an existing log group through the console. Use the AWS CLI to associate a key with an existing log group.
Remediation via AWS CLI
-
Log in to the AWS Management Console and click the CloudShell icon (
>_) in the top-right corner.
-
List the log groups that have no KMS key:
aws logs describe-log-groups \ --query 'logGroups[?!kmsKeyId].logGroupName' \ --output table
The command covers one region. Add
--region <region>to check another. -
If you have no suitable key, create one with a policy that lets CloudWatch Logs use it:
cat > key-policy.json <<EOF { "Version": "2012-10-17", "Statement": [ { "Sid": "EnableIAMPermissions", "Effect": "Allow", "Principal": {"AWS": "arn:aws:iam::<account-id>:root"}, "Action": "kms:*", "Resource": "*" }, { "Sid": "AllowCloudWatchLogs", "Effect": "Allow", "Principal": {"Service": "logs.<region>.amazonaws.com"}, "Action": [ "kms:Encrypt*", "kms:Decrypt*", "kms:ReEncrypt*", "kms:GenerateDataKey*", "kms:Describe*" ], "Resource": "*", "Condition": {"ArnLike": {"kms:EncryptionContext:aws:logs:arn": "arn:aws:logs:<region>:<account-id>:log-group:*"}} } ] } EOF aws kms create-key \ --policy file://key-policy.json \ --description "CloudWatch Logs encryption" \ --query 'KeyMetadata.Arn' \ --output text -
Associate the key with the log group:
aws logs associate-kms-key \ --log-group-name <log-group-name> \ --kms-key-id <kms-key-arn>
-
Verify that the key is associated:
aws logs describe-log-groups \ --log-group-name-prefix <log-group-name> \ --query 'logGroups[*].[logGroupName,kmsKeyId]' \ --output table
Replace <log-group-name> with the log group name, for example /aws/lambda/my-function.
Replace <kms-key-arn> with the key ARN, <region> with the region and <account-id> with your account ID.
Repeat steps 4 and 5 for each log group.
Updated on 04 November, 2026