Add support for an additional CloudTrail Trail configuration #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fernandogoncalves-me
force-pushed
the
cloudtrail
branch
from
8a077ba
to
5071c98
Compare
fernandogoncalves-me
force-pushed
the
cloudtrail
branch
from
f429507
to
ab1c609
Compare
fernandogoncalves-me
force-pushed
the
cloudtrail
branch
from
554c150
to
373bb5c
Compare
marwinbaumannsbp
approved these changes
Dec 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We would like to be able to push logs to a bucket managed by our Security Team.
This change adds the capacity to create an additional CloudTrail Trail to publish logs to a different S3 bucket than the one in the
loggingaccount of the AWS Organization.