What could be the cause of the error messages for these customers?

By:
In: SAP-C02
Tagged:
With: 1 Comment
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?

The Lambda function reached its concurrency limit.

The Lambda function its Region limit for concurrency.

The company reached its API Gateway account limit for calls per second.

The company reached its API Gateway default per-method limit for calls per second.

Explanations:

The logs indicate that the Lambda function is never invoked, suggesting that the issue lies before invocation, not a concurrency limit.

Similar to option A, if the Lambda function was never invoked, it cannot have reached its Region limit for concurrency.

The company could have reached its API Gateway account limit for calls per second, leading to 429 errors, especially during peak usage.

While the per-method limit could be a factor, the problem seems to stem from an overall account limit rather than a specific method limit.

2025-10-17

1 Comment

  1. Tyler
    Author

    I organize that the answer is:
    The company reached its API Gateway account limit for calls per second.

Leave a Reply to Tyler Cancel reply

Your email address will not be published. Required fields are marked *

three × three =