Has anyone run into AWS API rate limit due to operating multiple small clusters in same AWS account? What is the best practice? Cluster information: Kubernetes version: 1.11 Cloud being used: AWS Host OS: Linux

Thanks, so, Is it better to have fewer bigger K8s clusters than more smaller clusters to avoid exceeding those limits? How do you do team and work load isolation in such multi tenant K8s environment?

No :-/ Kubernetes tries to cope with that and react nicely. But of course that can still happen. What limit are you hitting? What is the problem it causes? As a very common alternative, every time more companies are using several AWS accounts and Amazon is making that use case more easy with time…

AWS API rate limit due to K8s

General Discussions

miker256 October 18, 2019, 1:06am 2

AWS has API-call rate limits, which apply to your whole account. They aren’t published, and they vary based on AWS load.

https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-request-throttling.html

Topic		Replies	Views
Service quantity limitation General Discussions	0	391	May 4, 2021
K8s on AWS, AWS api calls? General Discussions	0	425	October 15, 2019
Kubernetes + AWS Lambda General Discussions	1	499	January 28, 2021
IP Address Exhaustion in one AZ on EKS General Discussions	0	675	May 27, 2022
How to prevent "Too many requests" Exception General Discussions	3	7124	June 26, 2021

AWS API rate limit due to K8s

Related topics