CRITICAL

Ensure AWS Config recorder is running

Config recorder should be in recording state to capture configuration changes.

Security Impact

Stopped recorder means no configuration changes are being tracked.

How to Remediate

Start Config recorder if stopped: aws configservice start-configuration-recorder --configuration-recorder-name NAME

Affected Resources

AWS::Config::ConfigurationRecorder

Compliance Frameworks

SOC 2PCI-DSSHIPAANIST 800-53

How TigerGate Helps

TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all AWS Config resources across your AWS accounts every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for SOC 2, PCI-DSS, HIPAA compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
aws-config-10
Service
AWS Config
Category
Configuration Management
Severity
CRITICAL

Automate This Check

TigerGate automatically scans your AWS environment for this and 575+ other security checks.

Start Free Trial

Related AWS Config Checks

View all checks
aws-config-1high

Ensure AWS Config is enabled in all regions

aws-config-2medium

Ensure AWS Config is recording all resource types

aws-config-3medium

Ensure AWS Config uses S3 bucket with versioning

aws-config-4medium

Ensure AWS Config S3 bucket is encrypted

aws-config-5high

Ensure AWS Config rules are configured for critical controls