Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

AWS API throttling rate exceeded | Resolved

by | Oct 29, 2021

AWS API throttling rate exceeded error giving you trouble?

At Bobcares, as a part of our AWS Support Service, we have a solution for every query you may have.

Let’s take a look at how our Support Techs helped out a client with the Rate exceeded error recently.

What is AWS API throttling rate exceeded error?

Did you know that cannot exceed the maximum allowed number of allowed API request rates per account as well as per AWS Region? In fact, this is regardless of whether the calls came from an application, the AWS CLI, or the AWS Management Console.

In case we exceed the rate, we will wind up with a “Rate Exceeded” error and throttled API calls.

AWS API throttling rate exceeded


Furthermore, it is also possible to receive errors due to API calls made directly to Elastic Beanstalk or other AWS services like AWS Cloudformation.

How to solve AWS API throttling rate exceeded error?

  • Check with API calls are throttled
  • Check “describe” calls in the Elastic Beanstalk environment
  • Verify calls from third-party applications
  • Via error retries and exponential backoffs
  • Request for service limit increase

Check with API calls are throttled

  1. First, we will identify the throttling error and note the timeframe of the error in the Elastic Beanstalk event stream.
  2. Then, we will use AWS CloudTrail to examine events with the RequestLimitExceeded errors. We will also validate the eventSource. EventName and the userAgent.

Check “describe” calls in the Elastic Beanstalk environment

Interestingly, too many “describe” calls can cause an increase in API requests. In other words, we can validate the describe calls in the Elastic Beanstalk environment using either of the following approaches:

  • With EnvironmentResourceDescription as seen below:
    $ aws ec2 describe-instances --filters Name="tag:elasticbeanstalk:environment-id",Values="Your_Environment_ID"
  • With DescribeInstances API call via filters for the Elastic Beanstalk tags. For instance:
    $ aws ec2 describe-instances --filters Name="tag:elasticbeanstalk:environment-name",Values="Your_Environment_Name"

Verify calls from third-party applications

Third-party applications can also make continuous calls to any AWS service managed by Elastic Beanstalk.

Our Support Engineers recommend checking whether your third=party applications are making unnecessary calls with the help of CloudTrail. All we need to do is check the user agent that is making the calls.

Via error retries and exponential backoffs

We can also use exponential backoffs and error retries to limit the number of API calls. Additionally, each AWS SDK also implements an automatic retry logic as well as exponential backoff algorithms.

Request for service limit increase

Before we can request for a service limit increase in the AWS Service center, we have to do the following:

  • First, identify the API call as well as the call rate.
  • Then, try using exponential backoffs or error retries.
  • Include the AWS Region, the use-case for a limit increase, and timeframe specific to throttling issues while requesting service limit increase.

[Looking for assistance with AWS? Give us a call today.]


At the end of the day, we learned all about resolving API throttling and Rate exceeded errors from the skilled Support Engineers at Bobcares.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.



Submit a Comment

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

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.