DOCS-1785 - Add manual S3 Event Notification step for existing CloudTrail buckets - #7074
Open
amee-sumo wants to merge 2 commits into
Open
Conversation
Clarify that using an existing S3 bucket for CloudTrail logs requires manually adding an S3 Event Notification, since the CloudFormation template only automates this for newly created buckets. DOCS-1785
This file contains hidden or 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
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.
Purpose of this pull request
This pull request clarifies that when an existing S3 bucket is used for CloudTrail logs, an S3 Event Notification must be manually created afterward, since the CloudFormation template only automates this for newly created buckets. Adds a callout in the deployment steps, a cross-reference in the prerequisites doc, and a troubleshooting table row.
Select the type of change
Ticket (if applicable)
https://sumologic.atlassian.net/browse/DOCS-1785