[Solved] You configured API Gateway throttling with rateLimit: 200 and burstLimit: 300.... What is the most likely cause? | AWS

AWS - API Gateway

You configured API Gateway throttling with rateLimit: 200 and burstLimit: 300. However, clients report receiving HTTP 429 errors even when sending 150 requests per second. What is the most likely cause?

AThe usage plan or API key limits are lower than throttling settings

BThe API Gateway cache is full, causing throttling

CThe backend service is down, causing 429 errors

DThe rateLimit and burstLimit values are too high

Step-by-Step Solution

Solution:

Step 1: Understand causes of HTTP 429 in API Gateway
429 errors mean throttling triggered due to exceeding limits.
Step 2: Check usage plan and API key limits
Usage plans or API keys can have lower throttling limits overriding global settings, causing 429 errors at lower rates.
Final Answer:
The usage plan or API key limits are lower than throttling settings -> Option A
Quick Check:
Usage plan limits override throttling [OK]

Quick Trick: Check usage plan limits if throttling occurs unexpectedly [OK]

Common Mistakes:

Blaming backend service for 429 errors
Assuming cache affects throttling
Thinking high limits cause throttling

Master "API Gateway" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More AWS Quizzes

What is the most likely cause?

Step 1: Understand causes of HTTP 429 in API Gateway

Step 2: Check usage plan and API key limits

Final Answer:

Quick Check:

Want More Practice?