ElastiCache Encryption Disabled

What this rule checks

Detects ElastiCache clusters without at-rest or in-transit encryption.

How to fix it

1. 1Set AtRestEncryptionEnabled: true
2. 2Set TransitEncryptionEnabled: true

import { aws_elasticache as elasticache } from 'aws-cdk-lib';

new elasticache.CfnReplicationGroup(this, 'Redis', {
  replicationGroupDescription: 'cache',
  cacheNodeType: 'cache.t3.micro',
  engine: 'redis',
  numCacheClusters: 2,
  atRestEncryptionEnabled: false,
  transitEncryptionEnabled: false,
});

import { aws_elasticache as elasticache } from 'aws-cdk-lib';

new elasticache.CfnReplicationGroup(this, 'Redis', {
  replicationGroupDescription: 'cache',
  cacheNodeType: 'cache.t3.micro',
  engine: 'redis',
  numCacheClusters: 2,
  atRestEncryptionEnabled: true,
  transitEncryptionEnabled: true,
});

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID elasticache-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 ElastiCache rules