Lambda Deprecated Runtime

What this rule checks

Detects Lambda functions using runtimes that have reached or are approaching end-of-life.

How to fix it

1. 1Upgrade to a currently supported runtime
2. 2Track AWS Lambda runtime deprecation announcements

import { aws_lambda as lambda } from 'aws-cdk-lib';

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

import { aws_lambda as lambda } from 'aws-cdk-lib';

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

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID lambda-runtime-deprecated 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