A large manufacturing firm uses AWS for its production environment consisting of a web application for internal users & an online sales application for external vendors. For this, they are using EC2 instances in various regions. Any unplanned changes to an EC2 instance with downtime can impact sales application drastically. The CTO is looking for a consolidated dashboard for critical configuration changes made across multiple AWS accounts in the firm. You are planning to use AWS Config Aggregator to meet this requirement. Which of the following will be additional configuration required on Aggregator to fetch configuration data from all accounts?

Answer options:

A.Specify accounts & regions individually in the Aggregator to collect AWS Config configuration and compliance data without any authorization.
B.Create an AWS Organization for all these accounts & authorize an aggregator account to collect AWS Config configuration and compliance data.
C.Create an AWS Organization for all these accounts so that the Aggregator can collect AWS Config configuration and compliance data without any authorization.
D.Specify accounts & regions individually in Aggregator & authorize aggregator account to collect AWS Config configuration and compliance data.

Correct Answer – D
AWS Config uses an aggregator to collect data from all accounts in various regions for multi-account multi-region data aggregation. Accounts that are not part of AWS Organizations need to be individually added so that the Aggregator can be authorized to collect data from these accounts.
Option A is incorrect. When individual accounts add to the aggregator, additional authorization is required to collect AWS Config configuration and compliance data.
Option B is incorrect as AWS Organizations are not required to be created for all accounts to get aggregated views in AWS Config. If an AWS Organization is created for all these accounts, additional authorization to collect AWS Config configuration and compliance data is not required.
Option C is incorrect as AWS Organizations are not required to be created for all accounts to get aggregated views in AWS Config. We can also specify multiple accounts individually in the aggregator to get an aggregated view in AWS config.
For more information on Authorization for Aggregator Accounts, refer to the following URL-
https://docs.aws.amazon.com/config/latest/developerguide/authorize-aggregator-account-console.html