Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a parameter to the CFN stack for S3 changelog to disable accumulating the events #86

Merged
merged 2 commits into from
May 16, 2024

Conversation

volatilecat
Copy link
Contributor

@volatilecat volatilecat commented May 16, 2024

@volatilecat volatilecat requested review from anelson and Veetaha May 16, 2024 12:00
Comment on lines +42 to +43
* *DisableEventCollection* - if you decide to disable the protection policy for your S3 bucket, you can set this
to `true` to stop accumulating S3 update events in the SQS queue.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* *DisableEventCollection* - if you decide to disable the protection policy for your S3 bucket, you can set this
to `true` to stop accumulating S3 update events in the SQS queue.
* *DisableEventCollection* - if you decide to disable the protection policy for your S3 bucket, you can set this
to `true` to stop accumulating S3 update events in the SQS queue.
**IMPORTANT**: If you set this parameter to `true`, then no more objects will be scanned on this bucket. If you set it back to `false`, then any new objects after the parameter is set to `false` will be available to scan, but all changes made to the bucket during the time when this parameter was set to `true` will not be scanned, unless you manually initiate a full scan of the entire bucket.

@volatilecat volatilecat merged commit b872700 into master May 16, 2024
4 checks passed
@volatilecat volatilecat deleted the feat/9142-disable-event-rule-param branch May 16, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants