Lambda Dead Letter Queue Missing

What this rule checks

Detects Lambda functions without dead letter queue configuration.

How to fix it

1. 1Configure a dead letter queue (SQS or SNS)
2. 2Set up monitoring for DLQ messages
3. 3Implement retry logic for failed invocations

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

// inside your Stack
new lambda.Function(this, 'Fn', {
  runtime: lambda.Runtime.NODEJS_22_X,
  handler: 'index.handler',
  code: lambda.Code.fromInline('exports.handler = async () => {};'),
});

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

// inside your Stack
const dlq = new sqs.Queue(this, 'Dlq', {
  encryption: sqs.QueueEncryption.KMS_MANAGED,
});
new lambda.Function(this, 'Fn', {
  runtime: lambda.Runtime.NODEJS_22_X,
  handler: 'index.handler',
  code: lambda.Code.fromInline('exports.handler = async () => {};'),
  deadLetterQueue: dlq,
});

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 lambda-dlq-missing and the reason is kept in the report, not silently hidden.

In .cdk-insights.json:

{
  "ignoreRules": [
    { "id": "lambda-dlq-missing", "reason": "Why this is intentional" }
  ]
}

Or inline in your CDK code:

Validations.of(scope).acknowledge({
  id: 'cdk-insights::lambda-dlq-missing',
  reason: 'Why this is intentional',
});

Use the rule ID lambda-dlq-missing shown above — not the CDK-* ID from SARIF / GitHub code scanning. To dismiss every finding on one construct instead, use ignorePaths. Suppression docs →

More Lambda rules