What should a solutions architect do to meet these requirements with the LEAST operational overhead?
Add S3 Same-Region Replication rules in each S3 bucket that stores VPC flow logs to replicate objects to the destination S3 bucket. Configure the destination S3 bucket to allow objects to be received from the S3 buckets in other accounts.
Set up an IAM user in the Management account. Grant permissions to the IAM user to access the S3 buckets that contain the VPC flow logs. Run the aws s3 sync command in the AWS CLI to copy the objects to the destination S3 bucket.
Use an S3 inventory report to specify which objects in the S3 buckets to copy. Perform an S3 batch operation to copy the objects into the destination S3 bucket in the Management account with a single request.
Create an AWS Lambda function in the Management account. Grant S3 GET permissions on the source S3 buckets. Grant S3 PUT permissions on the destination S3 bucket. Configure the function to invoke when objects are loaded in the source S3 buckets.
Explanations:
S3 Same-Region Replication rules will continuously replicate the VPC flow log objects from each source S3 bucket to the destination bucket in the Management account, requiring minimal operational overhead after setup.
This option requires manually running theaws s3 synccommand, which is not automated and requires ongoing manual intervention, resulting in high operational overhead.
S3 inventory reports do not provide real-time data aggregation and require additional steps to copy objects, leading to increased complexity and operational overhead for continuous data aggregation.
Configuring a Lambda function to trigger on object creation events would add complexity and is less efficient for continuous aggregation. Lambda also has limits on execution time and invocation frequency, impacting scalability.