‘AWS Config is currently experiencing unusually high traffic’ error can occur if you are using the API call GetResourceConfigHistory or ListDiscoveredResources with an AWS Lambda function.

Here at Bobcares, we have seen several such AWS related queries as part of our AWS Support Services for AWS users, and online service providers.

Today we’ll take a look at the causes for this error and see how to fix it.

Facts about AWS Lambda function

AWS Lambda is a serverless computing tool provided by Amazon Web Services.

Also, it is a mainly runs code in response to events and automatically manages the computing resources required by that code.

Moreover, you can use Lambda to run small application codes without actually installing and running a server. These codes that you run on AWS Lambda is called as AWS Lambda functions.

Below are the steps to create an AWS Lambda function.

1. First, open the AWS Lambda console.
2. Then choose ‘Create a function’.
3. For Function name, enter my-function.
4. Finally, select the Create function.

What causes error ‘AWS Config is currently experiencing unusually high traffic’ to occur

Here is an error message that appeared while analyzing some config rules in the AWS Console.

~~
“AWS Config is currently experiencing unusually high traffic. Try your request again or contact AWS Support.”
~~

Below are the causes for this error to occur.

• If you are using the API call GetResourceConfigHistory with an AWS Lambda function and Lambda limit exceeds.
• If you are using the API call ListDiscoveredResources with an AWS Lambda function and if there is a high rate within a short interval that exceeds the throttle rate in the account per Region.

How we fix the error ‘AWS Config is currently experiencing unusually high traffic’

Here are some of the suggestions our Support Engineers provide to our customers to resolve this error.

• Make use of earlierTime parameter if the Lambda function retrieves the old state of your resources. As a result, this will limit the history period using timestamps with the GetResourceConfigHistory API.
• Consider using the BatchGetResourceConfig API call instead of GetResourceConfigHistory if the Lambda function determines the current configuration of the resources
• Implement a sleep time so that it reduces the frequency of API calls.
• Try implementing exponential backoff and then retry the request.

[Need any further assistance in fixing AWS errors? – We are here to help you.]

Conclusion

In short, this error can occur if you are using the API call GetResourceConfigHistory or ListDiscoveredResources with an AWS Lambda function. Today, we saw the solution to this error.