AWS systems-manager documentation change
Summary
Updated CloudWatch alarm behavior documentation to clarify automation cancellation when alarms enter ALARM state and added link to monitoring documentation
Security assessment
Change describes operational behavior of automation systems without addressing vulnerabilities or weaknesses. No security implications identified.
Diff
diff --git a/systems-manager/latest/userguide/visual-designer-tutorial.md b/systems-manager/latest/userguide/visual-designer-tutorial.md index 1c960767b..af647906c 100644 --- a//systems-manager/latest/userguide/visual-designer-tutorial.md +++ b//systems-manager/latest/userguide/visual-designer-tutorial.md @@ -206 +206 @@ You can view information about a runbook by choosing the runbook name. - 8. (Optional) Choose an Amazon CloudWatch alarm to apply to your automation for monitoring. To attach a CloudWatch alarm to your automation, the IAM principal that starts the automation must have permission for the `iam:createServiceLinkedRole` action. For more information about CloudWatch alarms, see [Using Amazon CloudWatch alarms](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/AlarmThatSendsEmail.html). If your alarm activates, the automation is stopped. If you use AWS CloudTrail, you will see the API call in your trail. + 8. (Optional) Choose a CloudWatch alarm to apply to your automation for monitoring. If your alarm enters `ALARM` state, the automation is canceled and any defined `onCancel` steps run. If you use AWS CloudTrail, you will see the `StopAutomationExecution` API call in your trail. For more information, see [Configuring Automations to monitor CloudWatch Alarms](./automation-cw-alarm-monitoring.html).