OpenSearch Encryption Disabled

What this rule checks

Detects OpenSearch domains without at-rest encryption or node-to-node encryption.

How to fix it

1. 1Enable EncryptionAtRestOptions with a KMS key
2. 2Enable NodeToNodeEncryptionOptions

import { aws_opensearchservice as opensearch } from 'aws-cdk-lib';

new opensearch.Domain(this, 'Domain', {
  version: opensearch.EngineVersion.OPENSEARCH_2_11,
  encryptionAtRest: { enabled: false },
  nodeToNodeEncryption: false,
});

import { aws_opensearchservice as opensearch } from 'aws-cdk-lib';

new opensearch.Domain(this, 'Domain', {
  version: opensearch.EngineVersion.OPENSEARCH_2_11,
  encryptionAtRest: { enabled: true },
  nodeToNodeEncryption: 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 opensearch-encryption-disabled and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID opensearch-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 OpenSearch rules