MEDIUM

Ensure AWS Config aggregator is configured for multi-account

Config aggregator should be configured for organizations or multi-account environments.

Security Impact

Without aggregator, compliance status requires checking each account separately.

How to Remediate

Create organization aggregator or add individual accounts to aggregator.

Affected Resources

AWS::Config::ConfigurationAggregator

Compliance Frameworks

SOC 2PCI-DSSNIST 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, NIST 800-53 compliance

  • Drift Detection

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

Check Details

Check ID
aws-config-7
Service
AWS Config
Category
Multi-Account
Severity
MEDIUM

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