A company provides specialized analytics services to customers. The analytics run on Amazon EC2 instances that need to be launched and terminated in response to requests from customers. A solutions architect is creating automation to manage the EC2 instances that handle customer requests. However, when the automation scripts attempt to launch many EC2 instances at the same time, a RequestLimitExceeded error frequently occurs.
What should the solutions architect do to handle this error?
When dealing with a RequestLimitExceeded error, the appropriate approach is to implement an exponential backoff strategy. This strategy helps manage the API request rate by gradually increasing the wait time between retries, allowing the API token bucket to refill and thus reducing the likelihood of hitting the request limit again. This is particularly effective for handling request rate limits as it ensures that retries are spaced out, providing time for the system to recover and process the requests without overwhelming the API.
A- Exponential Backoff A RequestLimitExceeded error for Amazon EC2 APIs usually indicates request rate limiting or resource rate limiting API throttling. You can use a combination of retry logic and exponential backoff strategies to work around this issue. https://aws.amazon.com/premiumsupport/knowledge-center/ec2-launch-multiple-requestlimitexceeded/
The answer is A -- I had to do this myself. see: https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html . I'm 100% sure. AWS will very rarely approve increases to this limit
A - If an API request exceeds the API request rate for its category, the request returns the RequestLimitExceeded error code. To prevent this error, ensure that your application doesn't retry API requests at a high rate. You can do this by using care when polling and by using exponential backoff retries. https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#api-request-rate
Not A, exponential backoff strategy only slows down the retry API, but it will not solve the problem as the automation script has to launch many EC2 instances at the same time anyway https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-api-troubleshooting.html#api-request-rate If an API request exceeds the API request rate for its category, the request returns the RequestLimitExceeded error code. To prevent this error, ensure that your application doesn't retry API requests at a high rate. You can do this by using care when polling and by using exponential backoff retries. Ans C https://docs.aws.amazon.com/AWSEC2/latest/APIReference/throttling.html If you exceed an API throttling limit, you get the RequestLimitExceeded error code. Adjusting API throttling limits You can request an increase for API throttling limits for your AWS account. To request a limit adjustment, contact the AWS Support Center.
I was thinking the same, but, even though if you request an increase for the API, it does not guarantee that you will not have that error again as everything has a limit, you can not request for an infinite amount of API call, thats why we have to implement exponential backoff. for that reason I changed my answer from C to A
RequestLimitExceeded error for Amazon EC2 APIs usually indicates request rate limiting or resource rate limiting API throttling. You can use a combination of retry logic and exponential backoff strategies to work around this issue.
I will vote for C simply because it will resolve the EC2 API call. A will not solve the problem of excessive API call.
The answer is A
Both A and C appear to be correct. As a solutions architect though i would apply the workaround to handle the error before thinking of requesting an increase. so for me A seems the best ans. - https://aws.amazon.com/premiumsupport/knowledge-center/ec2-launch-multiple-requestlimitexceeded/