CloudWatch Logs Encryption Disabled

What this rule checks

Detects CloudWatch Log Groups not encrypted with a customer-managed KMS key.

How to fix it

1. 1Set KmsKeyId on the LogGroup to encrypt with a customer-managed key

import { LogGroup, RetentionDays } from 'aws-cdk-lib/aws-logs';

new LogGroup(this, 'AppLogs', {
  retention: RetentionDays.ONE_MONTH,
});

import { LogGroup, RetentionDays } from 'aws-cdk-lib/aws-logs';
import { Key } from 'aws-cdk-lib/aws-kms';

const logKey = new Key(this, 'LogKey', { enableKeyRotation: true });
new LogGroup(this, 'AppLogs', {
  retention: RetentionDays.ONE_MONTH,
  encryptionKey: logKey,
});

CDK Insights pinpoints the exact file and line in your CDK source for every finding, so you can jump straight to the fix.

Affected resource types

Intentional? Suppress this finding

Sometimes a flag is deliberate — a genuinely public endpoint, say. You can dismiss cloudwatch-logs-encryption-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "cloudwatch-logs-encryption-disabled", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::cloudwatch-logs-encryption-disabled',
  reason: 'Why this is intentional',
});

Use the rule ID cloudwatch-logs-encryption-disabled shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More CloudWatch rules