API Gateway Stage Missing Throttling

What this rule checks

Detects API Gateway stages that configure no method-level rate or burst limits, leaving backends exposed to traffic spikes and uncontrolled cost.

How to fix it

1. 1Add MethodSettings with ThrottlingRateLimit and ThrottlingBurstLimit (e.g. for HttpMethod "*")
2. 2Tune per-method limits for hot paths

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

new apigateway.CfnStage(this, 'Stage', {
  restApiId: 'abcdef1234',
  deploymentId: 'deploy1234',
  stageName: 'prod',
});

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

new apigateway.CfnStage(this, 'Stage', {
  restApiId: 'abcdef1234',
  deploymentId: 'deploy1234',
  stageName: 'prod',
  methodSettings: [
    {
      httpMethod: '*',
      resourcePath: '/*',
      throttlingRateLimit: 100,
      throttlingBurstLimit: 200,
    },
  ],
});

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

In .cdk-insights.json:

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

Or inline in your CDK code:

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

Use the rule ID apigateway-throttling-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 API Gateway rules