Redshift Encryption Disabled

What this rule checks

Detects Redshift clusters without at-rest encryption.

How to fix it

1. 1Set Encrypted: true and specify a KmsKeyId

import { aws_redshift as redshift } from 'aws-cdk-lib';

new redshift.CfnCluster(this, 'Cluster', {
  clusterType: 'single-node',
  dbName: 'analytics',
  masterUsername: 'admin',
  masterUserPassword: '{{resolve:secretsmanager:redshift:SecretString:password}}',
  nodeType: 'ra3.xlplus',
  encrypted: false,
});

import { aws_redshift as redshift, aws_kms as kms } from 'aws-cdk-lib';

new redshift.CfnCluster(this, 'Cluster', {
  clusterType: 'single-node',
  dbName: 'analytics',
  masterUsername: 'admin',
  masterUserPassword: '{{resolve:secretsmanager:redshift:SecretString:password}}',
  nodeType: 'ra3.xlplus',
  encrypted: true,
  kmsKeyId: new kms.Key(this, 'RedshiftKey').keyId,
});

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID redshift-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 Redshift rules