Multiple Lambda Functions Without X-Ray Tracing

What this rule checks

Detects stacks with several Lambda functions and no X-Ray tracing configuration, losing visibility into distributed request flows.

How to fix it

1. 1Enable X-Ray tracing on Lambda functions (tracing: lambda.Tracing.ACTIVE) for distributed-request visibility

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID stack-lambda-xray-tracing-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