‘We are unable to complete the request at this time’ is one the common error message that the AWS Config console throws.

Here at Bobcares, we have seen several such AWS related errors as part of our Server Management Services for web hosts, AWS users, and online service providers.

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

What causes ‘We are unable to complete the request at this time’ error to occur

Let us take a deep look into the causes of this error message in AWS.

1. If the AWS Config aggregator limit (PutConfigurationAggregator) exceeds.

For instance, the below error message indicates that the number of aggregators exceeds the limit.

~~
The configuration aggregator ‘<aggregator_name>’ could not be created because the account already contains ’50’ configuration aggregators. Consider deleting configuration aggregators or contact AWS Config to increase the limit.”
~~

2. In case, if you are calling the StartConfigRulesEvaluation API more than one time every minute.

For instance, below is the cloudtrail error message.

~~
You have exceeded the maximum request rate. Try again at a later time.
~~

How we fix the error ‘We are unable to complete the request at this time’

Here is the solution that our Support Engineers follow to resolve this error.

1. The configuration aggregator’s default limit is 50. So we either delete the aggregator or request a limit increase.

We follow the below steps to delete the aggregator.

• Initially, we choose the aggregator name.
• After that, we choose Actions and then choose Delete.
  Here a warning message will be displayed. Deleting aggregator results in the loss of all aggregated data. You cannot recover this data but data in the source account(s) is not impacted.
• Finally, we choose ‘Delete’ to confirm the selection.

2. Normally, the StartConfigRulesEvaluation API call is restricted to one time every minute.

So, we suggest to wait for the current evaluation to complete, or wait one minute, and then try again.

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

Conclusion

In short, this error occurs when the AWS Config aggregator limit (PutConfigurationAggregator) exceeds or if you are calling the StartConfigRulesEvaluation API more than one time every minute. Today, we saw how our Support Engineers fix this error.