Centralize AWS Config for Resource Monitoring
Specification & Description
Enable AWS Config recording across all AWS Organizations accounts and operational regions, delivering configuration snapshots and history to a centralized S3 bucket and aggregating compliance data in the Security account.
Technical Specifications
AWS Config continuously records resource configurations and configuration changes over time, forming the inventory and compliance evaluation layer for landing zone detective controls.
1. Dual Delegated Administrator Principals
- AWS Config requires registering both
config.amazonaws.com(for organization configuration aggregators) andconfig-multiaccountsetup.amazonaws.com(for organization Config rules and conformance packs) as delegated administrators in the Security account.
2. Member Account Recorders and Cost Optimization
- Registering a delegated administrator does not automatically start configuration recorders in member accounts. Deploy configuration recorders and delivery channels across all accounts and regions (via CloudFormation StackSets, Control Tower, or Terraform).
- Set
includeGlobalResourceTypes = truein only one designated home region per account to avoid duplicate recording charges for global IAM resources.
3. Centralized Organization Aggregator
- Provision an organization aggregator (
OrganizationAggregationSourcewithAllAwsRegions = true) in the Security delegated administrator account using an IAM role withAWSConfigRoleForOrganizations.
Security Rationale
Configuration drift and unapproved resource changes introduce persistent security exposure. Centralized AWS Config recording and aggregation provide the resource inventory and change timeline required for incident response, continuous compliance, and Security Hub standards evaluations.
Business & Security Impact
Without centralized AWS Config recording and aggregation, unauthorized infrastructure changes go undetected and multi-account security posture evaluations lack authoritative resource state.
Operational & Implementation Notes
This control remains in draft status while multi-region recorder rollout patterns (Control Tower vs custom CloudFormation StackSets) are finalized. Note that AWS Config DescribeConfigurationRecorders and DescribeDeliveryChannels return camelCase keys (name, recordingGroup) whereas DescribeConfigurationAggregators returns PascalCase keys (ConfigurationAggregatorName, OrganizationAggregationSource).
Related Controls & Guardrails (2)
Compliance Framework Mappings (6)
Regulatory baselines and industry standards mapped to this control specification.
| Framework / Standard | Mapped Requirements & Controls | Controls |
|---|---|---|
NIST 800-53 Rev 5NIST 800-53 | CM-2CM-3CM-6CM-8 | 4 |
CIS AWS Foundations Benchmark v3.0CIS AWS | 3.3 | 1 |
ISO 27001:2022ISO 27001 | A.8.9 | 1 |
PCI DSS v4.0PCI DSS | 2.2.111.5.2 | 2 |
SOC 2SOC 2 | CC7.1CC8.1 | 2 |
AWS Foundational Security Best PracticesAWS FSBP | Config.1 | 1 |
* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.
Automated Detection & Rule Logic
Detection Engine: aws-api • Automated: Yes
Verify delegated administrator registrations for both config.amazonaws.com
and config-multiaccountsetup.amazonaws.com, confirm an organization
aggregator with AllAwsRegions = true exists in the Security account, and
verify active configuration recorders and delivery channels across accounts
and regions.
Preventative Enforcement Policies
Remediation Guide & Automation
Register the Security account as delegated administrator for both `config.amazonaws.com` and `config-multiaccountsetup.amazonaws.com`, deploy an organization-wide configuration aggregator in the Security account, and enable configuration recorders and delivery channels across all member accounts and regions targeting the central Log Archive S3 bucket.
Step-by-Step Instructions
- From the Organizations Management account, enable trusted access and register the Security account as delegated administrator for both config.amazonaws.com and config-multiaccountsetup.amazonaws.com.
- In the Security delegated administrator account, create an IAM role trusting config.amazonaws.com with AWSConfigRoleForOrganizations and create an organization configuration aggregator covering all AWS regions.
- Across all accounts and enabled regions, deploy an AWS Config recorder and delivery channel targeting the central Log Archive S3 bucket (and optional SNS topic).
- Enable includeGlobalResourceTypes in only the primary home region per account to avoid duplicate IAM global resource recording charges.
- Attach the protective SCP to the Organization Root preventing member accounts from stopping or deleting Config recorders, delivery channels, or aggregators.