Multi-Account Multi-Region Data Aggregation - AWS Config

Multi-Account Multi-Region Data Aggregation

An aggregator is an AWS Config resource type that collects AWS Config configuration and compliance data from the following:

  • Multiple accounts and multiple AWS Regions.

  • Single account and multiple AWS Regions.

  • An organization in AWS Organizations and all the accounts in that organization which have AWS Config enabled.

Use an aggregator to view the resource configuration and compliance data recorded in AWS Config. An aggregator uses an Amazon S3 bucket to store aggregated data. It periodically retrieves configuration snapshots from the source accounts and stores them in the designated S3 bucket. The following image displays how an aggregator collects AWS Config data from multiple accounts and Regions.

The image depicts the AWS Config data aggregation proces. It invovles collecting data from multiple source accounts and AWS Regions, aggregating resource configuration information and compliance data, and presenting an aggregated view to help with management.

Use Cases

  • Compliance Monitoring: You can aggregate compliance data to assess the overall compliance postures of your organization, or across accounts and Regions.

  • Change Tracking: You can track changes to resources over time across your organization, or across accounts and Regions.

  • Resource Relationships: You can analyze resource dependencies and relationships across your organization, or across accounts and Regions.


Aggregators provide a read-only view into the source accounts and Regions that the aggregator is authorized to view by replicating data from the source accounts into the aggregator account. Aggregators do not provide mutating access into a source account or region. For example, this means that you cannot deploy rules through an aggregator or push snapshot files to a source account or region through an aggregator.

Using aggregators does not incur any additional costs.


A source account is the AWS account from which you want to aggregate AWS Config resource configuration and compliance data. A source account can be an individual account or an organization in AWS Organizations. You can provide source accounts individually or you can retrieve them through AWS Organizations.

A source region is the AWS Region from which you want to aggregate AWS Config configuration and compliance data.

An aggregator account is an account where you create an aggregator.

Authorization refers to the permissions you grant to an aggregator account and region to collect your AWS Config configuration and compliance data. Authorization is not required if you are aggregating source accounts that are part of AWS Organizations.

Region Support

Currently, multi-account multi-region data aggregation is supported in the following Regions:

Region Name Region Endpoint Protocol
US East (Ohio) us-east-2 HTTPS
US East (N. Virginia) us-east-1 HTTPS
US West (N. California) us-west-1 HTTPS
US West (Oregon) us-west-2 HTTPS
Africa (Cape Town) af-south-1 HTTPS
Asia Pacific (Hong Kong) ap-east-1 HTTPS
Asia Pacific (Hyderabad) ap-south-2 HTTPS
Asia Pacific (Jakarta) ap-southeast-3 HTTPS
Asia Pacific (Melbourne) ap-southeast-4 HTTPS
Asia Pacific (Mumbai) ap-south-1 HTTPS
Asia Pacific (Osaka) ap-northeast-3 HTTPS
Asia Pacific (Seoul) ap-northeast-2 HTTPS
Asia Pacific (Singapore) ap-southeast-1 HTTPS
Asia Pacific (Sydney) ap-southeast-2 HTTPS
Asia Pacific (Tokyo) ap-northeast-1 HTTPS
Canada (Central) ca-central-1 HTTPS
Canada West (Calgary) ca-west-1 HTTPS
Europe (Frankfurt) eu-central-1 HTTPS
Europe (Ireland) eu-west-1 HTTPS
Europe (London) eu-west-2 HTTPS
Europe (Milan) eu-south-1 HTTPS
Europe (Paris) eu-west-3 HTTPS
Europe (Spain) eu-south-2 HTTPS
Europe (Stockholm) eu-north-1 HTTPS
Europe (Zurich) eu-central-2 HTTPS
Israel (Tel Aviv) il-central-1 HTTPS
Middle East (Bahrain) me-south-1 HTTPS
Middle East (UAE) me-central-1 HTTPS
South America (São Paulo) sa-east-1 HTTPS
AWS GovCloud (US-East) us-gov-east-1 HTTPS
AWS GovCloud (US-West) us-gov-west-1 HTTPS