AWS systems-manager documentation change
Summary
Added entry about Automation using execution identity instead of service-linked role for CloudWatch alarm monitoring
Security assessment
The change emphasizes proper permission configuration for execution identities but doesn't reference a specific security vulnerability. It improves security documentation by guiding users to implement least privilege access.
Diff
diff --git a/systems-manager/latest/userguide/systems-manager-release-history.md b/systems-manager/latest/userguide/systems-manager-release-history.md index 5a3d66100..e5dd6e7e8 100644 --- a//systems-manager/latest/userguide/systems-manager-release-history.md +++ b//systems-manager/latest/userguide/systems-manager-release-history.md @@ -14,0 +15 @@ Change| Description| Date +Automation now uses execution identity for CloudWatch alarm monitoring| Systems Manager Automation now uses your runbook execution identity for CloudWatch alarm monitoring. It no longer uses the SSM service-linked role for this operation. Make sure your execution identity has the required permissions. For more information, see [Configuring CloudWatch alarm monitoring for Automation](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-cw-alarm-monitoring.html).| July 8, 2026