Check ID:
Provider: AWS
Service:
Severity: MEDIUM
Categories:
Resource type:
config_recorder_all_regions_enabledProvider: AWS
Service:
configSeverity: MEDIUM
Categories:
logging, forensics-readyResource type:
OtherWhat this check verifies
AWS accounts have AWS Config recorders active and healthy in each Region. It identifies Regions with no recorder, a disabled recorder, or a recorder in a failure state.Risk
Gaps in Config recording create blind spots. Changes in unmonitored Regions aren’t captured, weakening integrity and auditability. Adversaries can alter resources or stage assets unnoticed, enabling misconfigurations and delaying incident response.Recommendation
Enable AWS Config in every Region with continuous recording and maintain healthy recorder status.Remediation
- Terraform
- Native IaC
- Dashboard steps
References
- https://repost.aws/es/questions/QUGcgeerhcTamRkwgdwh_tLQ/enable-aws-config
- https://www.tenable.com/audits/items/CIS_Amazon_Web_Services_Foundations_v1.5.0_L2.audit:6a5136528bd329139e5969f8f1e5ffbc
- https://aws.amazon.com/blogs/mt/aws-config-best-practices/
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = config_recorder_all_regions_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks