AWS Security ChangesHomeSearch

AWS AmazonCloudWatch documentation change

Service: AmazonCloudWatch · 2026-02-13 · Documentation low

File: AmazonCloudWatch/latest/monitoring/Acting_Alarm_Changes.md

Summary

Removed detailed alarm actions documentation and simplified content

Security assessment

The change restructures documentation without altering security implications. Removed content about alarm actions doesn't indicate resolution of vulnerabilities.

Diff

diff --git a/AmazonCloudWatch/latest/monitoring/Acting_Alarm_Changes.md b/AmazonCloudWatch/latest/monitoring/Acting_Alarm_Changes.md
index 888823cf4..f442f0e87 100644
--- a//AmazonCloudWatch/latest/monitoring/Acting_Alarm_Changes.md
+++ b//AmazonCloudWatch/latest/monitoring/Acting_Alarm_Changes.md
@@ -5,2 +4,0 @@
-Alarm actions and notificationsMuting Alarm Actions
-
@@ -13,66 +10,0 @@ When an alarm evaluates, it might change from one state to another, such as ALAR
-## Alarm actions and notifications
-
-The following table shows the actions executed for alarms along with their behavior for multiple time series (or contributors) alarms:
-
-Action Type | Multiple Time Series Alarm support | More Information  
----|---|---  
-SNS notifications | Contributor Level | [Amazon SNS event destinations](https://docs.aws.amazon.com/sns/latest/dg/sns-event-destinations.html)  
-EC2 actions (stop, terminate, reboot, recover) | Not supported | [Create alarms to stop, terminate, reboot, or recover an EC2 instance](./UsingAlarmActions.html)  
-Auto Scaling actions | Not supported | [Step and simple scaling policies for Amazon EC2 Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html)  
-Systems Manager OpsItem creation | Alarm Level | [Configure CloudWatch alarms to create OpsItems](https://docs.aws.amazon.com/systems-manager/latest/userguide/OpsCenter-create-OpsItems-from-CloudWatch-Alarms.html)  
-Systems Manager Incident Manager incidents | Alarm Level | [Creating incidents automatically with CloudWatch alarms](https://docs.aws.amazon.com/incident-manager/latest/userguide/incident-creation.html#incident-tracking-auto-alarms)  
-Lambda function invocation | Contributor Level | [Invoke a Lambda function from an alarm](./alarms-and-actions-Lambda.html)  
-CloudWatch investigations investigation | Alarm Level | [Start a CloudWatch investigations from an alarm](./Start-Investigation-Alarm.html)  
-  
-The content of alarm notifications differs between single-metric alarms and multi-time series alarms:
-
-  * Single-metric alarms include both a state reason and detailed state reason data, showing the specific datapoints that caused the state change.
-
-  * Multi-time series alarms provide a simplified state reason for each contributor, without the detailed state reason data block.
-
-
-
-
-###### Example Notification Content Examples
-
-Single-metric alarm notification includes detailed data:
-    
-    
-    {
-      "stateReason": "Threshold Crossed: 3 out of the last 3 datapoints [32.6 (03/07/25 08:29:00), 33.8 (03/07/25 08:24:00), 41.0 (03/07/25 08:19:00)] were greater than the threshold (31.0)...",
-      "stateReasonData": {
-        "version": "1.0",
-        "queryDate": "2025-07-03T08:34:06.300+0000",
-        "startDate": "2025-07-03T08:19:00.000+0000",
-        "statistic": "Average",
-        "period": 300,
-        "recentDatapoints": [41, 33.8, 32.6],
-        "threshold": 31,
-        "evaluatedDatapoints": [
-          {
-            "timestamp": "2025-07-03T08:29:00.000+0000",
-            "sampleCount": 5,
-            "value": 32.6
-          }
-          // Additional datapoints...
-        ]
-      }
-    }
-
-Multiple time series Metrics Insights Alarm SNS notification for Contributor example:
-    
-    
-    {
-      "AlarmName": "DynamoDBInsightsAlarm",
-      "NewStateValue": "ALARM",
-      "NewStateReason": "Threshold Crossed: 1 datapoint was less than the threshold (1.0). The most recent datapoint which crossed the threshold: [0.0 (01/12/25 13:34:00)].",
-      "StateChangeTime": "2025-12-01T13:42:04.919+0000",
-      "OldStateValue": "OK",
-      "AlarmContributorId": "6d442278dba546f6",
-      "AlarmContributorAttributes": {
-        "TableName": "example-dynamodb-table-name"
-      }
-      // Additional information...
-    }
-            
-
@@ -81,11 +13 @@ Additionally, CloudWatch sends events to Amazon EventBridge whenever alarms chan
-## Muting Alarm Actions
-
-Alarm mute rules allow you to automatically mute alarm actions during predefined time windows, such as maintenance periods or operational events. CloudWatch continues monitoring alarm states while preventing unwanted notifications. For more information, see [Alarm Mute Rules](./alarm-mute-rules.html). 
-
-###### Mute rules vs. disabling alarm actions
-
-Alarm mute rules temporarily mute actions during scheduled time windows and automatically unmute when the window ends. In contrast, the `DisableAlarmActions` API permanently disables alarm actions until you manually call `EnableAlarmActions`. The `EnableAlarmActions` API does not unmute alarms that are muted by active mute rules. 
-
-###### Note
-
-Muting an alarm does not stop CloudWatch from sending alarm events for alarm create, update, delete, and state changes to Amazon EventBridge. 
+For more information about alarm actions, see [Alarm actions](./alarm-actions.html).
@@ -100,0 +23,2 @@ Muting an alarm does not stop CloudWatch from sending alarm events for alarm cre
+  * [Stop, terminate, reboot, or recover an EC2 instance](./UsingAlarmActions.html)
+
@@ -112 +36 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please
-Suppressing composite alarm actions 
+Create a composite alarm