API Gateway stage has no method-level throttling configured

Severity: Low
Service: API Gateway
Check ID: APIGW_THROTTLING_NOT_CONFIGURED

What this check finds

Without throttling, a single client can exhaust Lambda concurrency or backend capacity causing downstream failures. Method-level throttling settings act as the last line of defence before requests reach your backend, even when a usage plan is in place.

Passing looks like: API Gateway throttling configured.

How to fix it

Configure default throttling on the stage or individual methods.

AWS CLI

aws apigateway update-stage --rest-api-id API_ID --stage-name STAGE --patch-operations op=replace,path=/*/*/throttling/burstLimit,value=100 op=replace,path=/*/*/throttling/rateLimit,value=50

Names in capitals are placeholders for your own resource. Review a command before you run it.

AWS console

API Gateway → select API → Stages → select stage → Default route settings → Throttling.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to API Gateway stage has no method-level throttling configured
Framework	Controls
NIST SP 800-53 Rev5 (Moderate)	SC-5 Denial-of-Service Protection
NIST Cybersecurity Framework 2.0	PR.IR-04 Adequate resource capacity for availability is maintained
ISO/IEC 27001:2022 Annex A	A.8.20 Networks security

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More API Gateway checks

All API Gateway checks