Are you facing "An unexpected internal error occurred with AWS config"? Look no further for the solution is here!
As part of our Server Support Services, we have previously fixed numerous AWS related errors for our customers.
In this context, we shall look into why this error occurs and how to get rid of it.
What triggers "An unexpected internal error occurred with AWS config"?
This is an AWS Config console error.
Different factors could trigger this error in AWS as seen below;
i. Switching to a different AWS region could cause this issue. This happens because the Config rules does not exist in the destination Region. When this is the case , you will get an AWS API Error code as shown below;
Followed by the cloudTrail Error Message;
The ConfigRule '<Config rule name>' provided in the request is invalid. Please check the configRule name.
ii. Another reason why this error happen is during the deletion of a remediation while there is a remediation in progress. This is true when the PutRemediationConfigurations API call ResourceType parameter was specified in creation but not in deletion. When this is the case , you will get an AWS API Error code as shown below;
Followed by the Error Message;
Remediation action is in progress.
No RemediationConfiguration for rule EXAMPLE_Config_Rule_Name exists.
How to fix "An unexpected internal error occurred with AWS config"
As earlier mentioned, the most common reason why this error occurs is due to changes in the AWS Region. An easy fix would be to switch back to the AWS Region that has the same AWS Config rule. If you do not know how to go about choosing an AWS region, follow the instructions below;
1. Choose a service, to see the service's console in the AWS Management Console.
2. Next choose the name of the displayed Region on the Navigation bar. Once you choose a region, it will be the default region in the console.
In cases where a remediation process is ongoing, it is best to stop the process with the stop-automation-execution command. Waiting for the process to complete can also help fix this error.
Finally, using the ResourceType parameter in the DeleteRemediationConfiguration API is mandatory if the ResourceType parameter in the PutRemediationConfigurations API exist.