Skip to content

DOCS-1785 - Add manual S3 Event Notification step for existing CloudTrail buckets - #7074

Open
amee-sumo wants to merge 2 commits into
mainfrom
DOCS-1785-Add-a-manual-S3-Event-notification-step-for-existing-CloudTrail-buckets
Open

DOCS-1785 - Add manual S3 Event Notification step for existing CloudTrail buckets#7074
amee-sumo wants to merge 2 commits into
mainfrom
DOCS-1785-Add-a-manual-S3-Event-notification-step-for-existing-CloudTrail-buckets

Conversation

@amee-sumo

Copy link
Copy Markdown
Collaborator

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

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/DOCS-1785

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
@amee-sumo amee-sumo self-assigned this Aug 28, 2026
@cla-bot cla-bot Bot added the cla-signed Contributor approved, listed in .clabot file label Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed Contributor approved, listed in .clabot file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant