SQS Encryption Disabled

What this rule checks

Detects SQS queues without encryption.

How to fix it

1. 1Enable server-side encryption with KMS
2. 2Use SQS-managed keys (SSE-SQS) or customer managed keys

import * as sqs from 'aws-cdk-lib/aws-sqs';

// inside your Stack
new sqs.Queue(this, 'Queue', {
  encryption: sqs.QueueEncryption.UNENCRYPTED,
});

import * as sqs from 'aws-cdk-lib/aws-sqs';

// inside your Stack
new sqs.Queue(this, 'Queue', {
  encryption: sqs.QueueEncryption.KMS_MANAGED,
});

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID sqs-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 SQS rules