API Gateway throttles requests
I have an API Gateway resource connecting to lambda and I see that consecutive requests to the API are throttled. I don't have caching enabled and the rate of requests is far below the throttling level.
API Gateway configuration
The lambda also has been configured without an upper bound on invocations.
- 최신
- 최다 투표
- 가장 많은 댓글
If you are confident that the throughput is below the rate and the burst limit for a particular API resource/method combination, then you may be hitting the overall account level limits for your account - https://docs.aws.amazon.com/apigateway/latest/developerguide/limits.html
In that case, you will need to open a support ticket with AWS support and apply for an increase in quotas.
API Gateway throttles requests to your API using the token bucket algorithm, where a token counts for a request. Specifically, API Gateway examines the rate and a burst of request submissions against all APIs in your account, per Region.
In the token bucket algorithm, a burst can allow pre-defined overrun of those limits, but other factors can also cause limits to be overrun in some cases.
When request submissions exceed the steady-state request rate and burst limits, API Gateway begins to throttle requests. Clients may receive 429 Too Many Requests error responses at this point. Upon catching such exceptions, the client can resubmit the failed requests in a way that is rate limiting.
Refer to the below link for additional details: https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html -- [1]
Thanks for taking the time to reply. In my case, the API is still under development and currently, it's just me querying the API. How can I disable this throttle for specific resources using the API? Also, I don't see this behaviour when I use HTTP integration. This only shows up with lambdas.
관련 콘텐츠
AWS 공식업데이트됨 일 년 전
Hi Indranil Thanks for taking the time to reply. I did have a look at this table before, but my system is still under dev and the peak load is probably 10rps on a resource/method. Also, I don't see this behaviour if I use HTTP integration. Only shows up with lambda.
In that case lambda is the one getting throttled. But 10 RPS is too low. Can you take a look at this Support Knowledge Center article - https://aws.amazon.com/premiumsupport/knowledge-center/lambda-troubleshoot-throttling/
The account level quotas for lambda functions are here - https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html
Are there other lambda functions running in the account that are using up the account level lambda concurrency limits?