Skip to content

fix(cloud_logs) - Clarifying KMS key output issue #155

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 21, 2025
Merged

fix(cloud_logs) - Clarifying KMS key output issue #155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions modules/log_ingestion.s3.cft.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -358,8 +358,7 @@ Outputs:
Value: !Sub |
IMPORTANT: MANUAL ACTION REQUIRED

Please add the following statement to your KMS key policy to allow Sysdig to decrypt logs.
This is necessary when KMS encryption is enabled for your S3 bucket and the KMS key is in a different account.
Add the following statement to the KMS key policy used by CloudTrail
Without this policy addition, Sysdig may not be able to read your encrypted logs.

{
Expand Down
Loading