Steps to migrate from traditional to multi account CloudTrail #28
-
This message was extracted from a discussion that originally took place in Gruntwork Community Slack. Names and URLs have been removed where appropriate From a customer Hey there, I have a short question and I hope that I did not miss the documentation for that. As far as I know you added support for the AWS organization cloud trail to the Is there a migration path or documentation available which describes which steps are required to move from a traditional multi account cloud trail setup to organization trail with the Gruntwork module. Thanks in advance and best regards |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
From a grunt Hi person, I'd actually advise you to use v0.48.1 or later due to a couple of bugs in the initial release of the Organizations CloudTrail feature. The bugs were resolved in that version. Do note the No other specific steps are required to migrate. You can bump the version of I hope this helps! |
Beta Was this translation helpful? Give feedback.
From a grunt
Hi person,
I'd actually advise you to use v0.48.1 or later due to a couple of bugs in the initial release of the Organizations CloudTrail feature. The bugs were resolved in that version. Do note the
WARNING
about undeleting the KMS key to ensure that old CloudTrail logs remain readable after updating.No other specific steps are required to migrate. You can bump the version of
terraform-aws-security
(being sure to review the release notes between your current version andv0.48.1
in case something else changed), then addcloudtrail_is_organization_trail = true
toaccount-baseline-root
, which I assume you're using, and setenable_cloudtrail = false
inaccount-baseline-app
anda…