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

legobrick · web-flow · commit 7e3874b74fd3 · 2025-05-21T12:18:09.000+02:00
diff --git a/modules/log_ingestion.s3.cft.yaml b/modules/log_ingestion.s3.cft.yaml
@@ -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.
 
       {

Original file line number	Diff line number	Diff line change
`@@ -358,8 +358,7 @@ Outputs:`
`358`	`358`	`Value: !Sub \|`
`359`	`359`	`IMPORTANT: MANUAL ACTION REQUIRED`
`360`	`360`
`361`		`- Please add the following statement to your KMS key policy to allow Sysdig to decrypt logs.`
`362`		`- This is necessary when KMS encryption is enabled for your S3 bucket and the KMS key is in a different account.`
	`361`	`+ Add the following statement to the KMS key policy used by CloudTrail`
`363`	`362`	`Without this policy addition, Sysdig may not be able to read your encrypted logs.`
`364`	`363`
`365`	`364`	`{`