Kinesis Encryption Disabled

What this rule checks

Detects Kinesis Data Streams without server-side KMS encryption.

How to fix it

1. 1Set StreamEncryption with EncryptionType: KMS and a KeyId

import { aws_kinesis as kinesis } from 'aws-cdk-lib';

new kinesis.Stream(this, 'Stream', {
  shardCount: 1,
  encryption: kinesis.StreamEncryption.UNENCRYPTED,
});

import { aws_kinesis as kinesis, aws_kms as kms } from 'aws-cdk-lib';

new kinesis.Stream(this, 'Stream', {
  shardCount: 1,
  encryption: kinesis.StreamEncryption.KMS,
  encryptionKey: new kms.Key(this, 'StreamKey'),
});

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 kinesis-encryption-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID kinesis-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 Kinesis rules