A startup initially operated in one AWS Region and created a regional AWS CloudTrail trail (via the AWS CLI) that delivers logs to an Amazon S3 bucket. After adding resources in multiple Regions, the engineer observes that logs from the new Regions are not delivered to S3. With minimal operational effort, how should this be fixed?

The correct solution is to update the existing CloudTrail trail to apply to all Regions. When a CloudTrail trail is created as "regional" (the default when not specified via CLI), it only records events from the Region in which it was created. To capture events from all AWS Regions, the trail needs to be configured as a "multi-Region trail." This can be done by updating the existing trail, which is the most efficient approach. Creating a new CloudTrail trail for each new Region (or one that applies to all Regions) would result in multiple trails, increasing management overhead and potentially leading to duplicate logs or missed events. Modifying the S3 bucket to receive notifications is incorrect because the S3 bucket is merely the destination; the CloudTrail trail itself is responsible for collecting the logs from the various Regions.