AWS AmazonCloudWatch: CloudWatch Omni: Editor grant includes InvokeIntegration, scope-down guidance
Summary
Updates the custom grant actions table to state that the Editor permission level now includes cloudwatch:InvokeIntegration (and that Space Admin includes PutIntelligenceConfiguration), and adds an Important note urging admins to scope down Editor grants to specific integrations and Slack channels.
Security assessment
The changed line documents that a broad permission level (Editor) implicitly carries cloudwatch:InvokeIntegration, i.e. an over-permissive grant that could let a member send notifications to arbitrary Slack channels. The new guidance to scope the grant down to named integrations/channels is IAM least-privilege hardening documentation, not a fix for a specific disclosed vulnerability.
Evidence
+Editor includes `cloudwatch:InvokeIntegration`. A member or access profile with Editor can send notifications through any integration in the space, to any Slack channel. To keep a member or profile limited to named integrations or channels, scope down its Editor grant to those integrations and channels.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/omni-custom-grant-actions.md b/AmazonCloudWatch/latest/monitoring/omni-custom-grant-actions.md index 8f8d9dd..433cdfd 100644 --- a//AmazonCloudWatch/latest/monitoring/omni-custom-grant-actions.md +++ b//AmazonCloudWatch/latest/monitoring/omni-custom-grant-actions.md @@ -14,0 +15,4 @@ A member who holds a Custom grant and a Viewer, Editor, or Space Admin grant get +Important + +Editor includes `cloudwatch:InvokeIntegration`. A member or access profile with Editor can send notifications through any integration in the space, to any Slack channel. To keep a member or profile limited to named integrations or channels, scope down its Editor grant to those integrations and channels. + @@ -46,2 +50,2 @@ CloudWatch | `cloudwatch:ListIntegrations`, `cloudwatch:GetIntegration`, `cloudw -CloudWatch | `cloudwatch:InvokeIntegration` | Send a message through an integration. Can be limited to named integrations and, for Slack, to channels. | Access profiles that alerts use to notify. No permission level includes it. -CloudWatch | `cloudwatch:GetIntelligenceConfiguration`, `cloudwatch:PutIntelligenceConfiguration` | Read the account's intelligence configuration, and turn intelligence features on or off. | Viewer includes `cloudwatch:GetIntelligenceConfiguration`. Editor includes `cloudwatch:PutIntelligenceConfiguration`. +CloudWatch | `cloudwatch:InvokeIntegration` | Send a message through an integration. Can be limited to named integrations and, for Slack, to channels. | Members and access profiles that send notifications, such as the access profiles that alerts use. Editor includes it. To limit a member or profile to named integrations or channels, scope down its Editor grant to those integrations and channels. +CloudWatch | `cloudwatch:GetIntelligenceConfiguration`, `cloudwatch:PutIntelligenceConfiguration` | Read the account's intelligence configuration, and turn intelligence features on or off. A save that enables automatic investigations also needs `cloudwatch:InvokeIntegration`. So does a save that adds or changes a Slack or PagerDuty notification. | Viewer includes `cloudwatch:GetIntelligenceConfiguration`. Space Admin includes `cloudwatch:PutIntelligenceConfiguration`.