SAP-C02 · Question #392
A company is building a software-as-a-service (SaaS) solution on AWS. The company has deployed an Amazon API Gateway REST API with AWS Lambda integration in multiple AWS Regions and in the same…
The correct answer is C. The company reached its API Gateway account limit for calls per second. The company reached its API Gateway account limit for calls per second. This is because Amazon API Gateway has a default account-level limit of 10,000 requests per second (RPS) and a default per-method limit of 5,000 RPS. If the company's premium tier customers are making more…
Question
A company is building a software-as-a-service (SaaS) solution on AWS. The company has deployed an Amazon API Gateway REST API with AWS Lambda integration in multiple AWS Regions and in the same production account. The company offers tiered pricing that gives customers the ability to pay for the capacity to make a certain number of API calls per second. The premium tier offers up to 3,000 calls per second, and customers are identified by a unique API key. Several premium tier customers in various Regions report that they receive error responses of 429 Too Many Requests from multiple API methods during peak usage hours. Logs indicate that the Lambda function is never invoked. What could be the cause of the error messages for these customers?
Options
- AThe Lambda function reached its concurrency limit.
- BThe Lambda function its Region limit for concurrency.
- CThe company reached its API Gateway account limit for calls per second.
- DThe company reached its API Gateway default per-method limit for calls per second.
How the community answered
(25 responses)- A4% (1)
- B8% (2)
- C72% (18)
- D16% (4)
Explanation
The company reached its API Gateway account limit for calls per second. This is because Amazon API Gateway has a default account-level limit of 10,000 requests per second (RPS) and a default per-method limit of 5,000 RPS. If the company's premium tier customers are making more than 10,000 requests per second in total across all API methods and regions, they would be receiving the error message of 429 Too Many Requests. This indicates that the API Gateway account is reaching its capacity limit, and the Lambda function is not being invoked because API Gateway is blocking the requests before they reach the Lambda function. https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request- throttling.html#apig-request-throttling-account-level-limits
Community Discussion
No community discussion yet for this question.