This could be due to Configuration recorder not being configured for all the regions.
Configuration Recorder is a component of AWS Config that operates at the regional level, capturing and forwarding configuration details from resources within specific AWS regions to AWS Config for further analysis and monitoring.
Use the below command to check the configuration recorder status:
You can use the CLI command
aws configservice describe-configuration-recorders
if the response is empty, which means the policy and collection is working as expected and the customer should follow the remediation steps and configure configuration recorder for all the regions.
Response:
{
"ConfigurationRecorders": []
}
Configuration recorder status for all the region:
aws configservice describe-configuration-recorder-status
Configuration recorder status for one region:
aws configservice describe-configuration-recorder-status --region <region-name>