What best practice should first be applied to address this issue?
Contact AWS Support for a limit increase.
Use the AWS CLI to get the metrics.
Analyze the applications and remove the API call.
Retry the call with exponential backoff.
Explanations:
A ThrottlingException usually indicates that the API rate limit has been exceeded, but a limit increase is not the first action to take. It’s better to handle the throttling by using proper retries with backoff before requesting a limit increase.
Using the AWS CLI might bypass the issue momentarily, but it doesn’t address the underlying cause of the throttling. The problem persists and needs proper handling through retry strategies.
Removing the API call might reduce throttling, but it is not a solution for improving performance or ensuring data retrieval in the case of valid API usage. The real solution is to manage the rate of API calls.
Using exponential backoff is the recommended best practice for handling ThrottlingException errors. This method reduces the frequency of retries and gives the API time to recover, helping to avoid exceeding rate limits.
If I had to guess, I’d say the answer is:
Retry the call with exponential backoff.
I calculate that the answer is:
Retry the call with exponential backoff.