Are you facing AWS error "AWS Config is currently experiencing unusually high traffic. Try your request again or contact AWS Support."? This article will show you how to fix this issue.

AWS Config is currently experiencing unusually high traffic error is triggered when an API call GetResourceConfigHistory or ListDiscoveredResources is used with an AWS Lambda function.

As part of our Server Support Services, we have helped customers fix numerous AWS errors.

In this context, we shall look into why this error occurs and how to fix it.

More about AWS error "AWS Config is currently experiencing unusually high traffic

When an API call GetResourceConfigHistory is used along a Lambda function, this error will be triggered. You will see an error message signifying that;

ThrottlingException

Rate exceeded

Another reason why this error happens is in a situation whereby there is  high rate within a short interval of time which exceeds the throttle rate of an AWS account per Region.

How to fix AWS error "AWS Config is currently experiencing unusually high traffic"

Solving this error can be approached in different ways.

Using an earlierTime parameter to limit the history period by means of a timestamp with the GetResourceConfigHistory API can help to resolve this issue. Alternatively, by using BatchGetResourceConfig API call instead of GetResourceConfigHistory in a case where your Lambda function determines the current configuration of your resources can resolve this problem.

Similarly, if the rate of throttle per AWS account is exceeded, then a reduction in the frequency at which the API is called can help fix this issue. This requires an implementation of a sleep time mode.

Finally, implementing exponential backoff should be adopted while trying to run a request.

Need support in fixing AWS errors? We can help.