A company uses AWS Config rules to identify Amazon S3 buckets that are not compliant with the company's data protection policy. The S3 buckets are hosted in several AWS Regions and several AWS account

Question

Options

• ADeploy an AWS Config aggregator with organization-wide resource data aggregation. Create an
• BDeploy an AWS Config aggregator with organization-wide resource data aggregation. Create an
• CDeploy an AWS Config aggregator that scopes only the accounts and Regions that the company
• DDeploy an AWS Config aggregator that scopes only the accounts and Regions that the company

• A
  82% (18)
• B
  5% (1)
• C
  5% (1)
• D
  9% (2)

Explanation

An AWS Config aggregator with organization-wide aggregation enables centralized visibility and monitoring of compliance for all accounts and Regions within the organization. By combining this with an AWS Lambda function that automatically remediates noncompliant S3 buckets (either by reconfiguring them to meet the policy or deleting them if necessary), this solution provides an automated and scalable way to handle both existing and future noncompliant buckets across the entire organization. This setup meets the requirement to remediate both current and newly created noncompliant S3 buckets.

No community discussion yet for this question.