Avoiding duplicative CW and CT logs when registering an account to Control Tower
I currently have multiple AWS accounts under a single OU. I want to launch Control Tower in a NEW management account, and then register the existing OU to the Control Tower. What will happen to the existing Cloud Watch and Cloud Trail configurations on my accounts when their OU joins Control Tower? As I understand it, the same trails will be routed to the centralized logging account. Do I need to then manually disable the OU / account level CW and CT configurations I previously created? Is there best-practice guidance on this aspect of OU / account registration?
- 최신
- 최다 투표
- 가장 많은 댓글
I want to launch Control Tower in a NEW management account, and then register the existing OU to the Control Tower.
This will mean that the accounts you want to enroll in AWS Control Tower will have to leave your current AWS Organization and if you have existing account-level CloudTrail, it would still be enabled and still work after leaving your current AWS Organization and joining the AWS Organization of the new management account.
There are separate Amazon CloudWatch Log Groups set up by AWS Control Tower which will not impact your existing CloudWatch configurations. You can review the mandatory controls from Control Tower
When you configure Control Tower, you will Optionally configure AWS CloudTrail. If you have chosen for AWS Control Tower to create your organizational-level trail or you create it yourself, then you will be subject to additional charges for Cloud Trail duplicate management events. You should just choose either organizational-level Cloudtrail or account-level CloudTrail.
