AWS Config: Deploying across Multiple AWS Accounts, Regions, and Organizations

Deploying AWS Config Across Multiple AWS Organizations, Accounts and Regions

One of our AWS Managed Services customers has a multi-AWS Organization account structure - three Organizations in total.

While not a common deployment strategy, in this particular case it satisfied the client’s specific charge-backup requirements for the various geographical regions where the client operates.

Since resources exist in several AWS Organizations and multiple AWS accounts, we needed a simple way to provide a ‘compliance’ dashboard.

Ensuring Continuous Compliance with AWS Config

Monitoring for Compliance using AWS Config

Recently, a large Canadian manufacturer asked us to help them design and implement a compliance monitoring solution that needed to monitor resources across twelve AWS accounts.

We met the customer’s requirements by deploying AWS Config in a centralized account and setting up the aggregation of resource data into a single AWS account.

Deployment Strategy

In order to consolidate all AWS Config data into a single AWS account, we deployed an AWS Aggregator into one account. After deploying the Aggregator, we authorized the aggregation of data into the central account.