Lambda X-Ray Tracing Disabled

What this rule checks

Detects Lambda functions without active X-Ray tracing, reducing observability into latency and errors.

How to fix it

1. 1Set TracingConfig.Mode to Active on the function
2. 2Grant the function the AWSXRayDaemonWriteAccess managed policy

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

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

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

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

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID lambda-tracing-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 Lambda rules