Reuse a bucket for one or both logging integrations

AWS announced on November 18 that Control Tower can send AWS Config and AWS CloudTrail logs to an existing Amazon S3 bucket instead of a bucket created and managed by Control Tower.

The option applies when setting up or updating a landing zone on version 4.0 or later. Each integration can use a custom or Control Tower-managed bucket, and the same custom bucket can serve both integrations.

Ownership, Region and policy requirements still apply

The user guide requires the existing bucket to be in the landing zone's home Region. It must be owned by an account in the AWS organization, excluding the management account, and have the required log-delivery bucket policy.

A standard S3 bucket ARN is required; access-point ARNs are not supported. AWS says customers manage a custom bucket's configuration and protection, and Control Tower controls do not cover that bucket.

The announcement lists availability in all commercial AWS Regions, AWS GovCloud (US) Regions and the AWS European Sovereign Cloud where Control Tower is available.

Config bucket changes can require baseline updates

AWS says the buckets are preserved through landing zone updates, resets and decommissioning. When switching a custom bucket used by AWS Config, affected accounts' enabled baselines must also be updated to use the new bucket before deleting the old one.

The guide treats CloudTrail differently: changing only its custom bucket does not cause source drift on enabled baselines. Review the integration-specific instructions rather than assuming a landing zone change completes every account's transition.