AWS AmazonCloudWatch documentation change
Summary
Updated CPU threshold in example from 50% to 80% and fixed CLI command syntax
Security assessment
Threshold adjustment is operational tuning without security implications. CLI syntax fix prevents user errors but doesn't address vulnerabilities.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-insights-alarm-create.md b/AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-insights-alarm-create.md index d075937a0..a3f65b85b 100644 --- a//AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-insights-alarm-create.md +++ b//AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-insights-alarm-create.md @@ -76 +76 @@ To create an alarm that performs an SSM Incident Manager action, you must have c -Use the `put-metric-alarm` command and specify a Metrics Insights query in the `metrics` parameter. For example, the following command sets an alarm that goes into ALARM state if any of your instances go above 50% in CPU utilization. +Use the `put-metric-alarm` command and specify a Metrics Insights query in the `metrics` parameter. For example, the following command sets an alarm that goes into ALARM state if any of your instances go above 80% in CPU utilization. @@ -79 +79 @@ Use the `put-metric-alarm` command and specify a Metrics Insights query in the ` - aws cloudwatch put-metric-alarm —alarm-name Prod-App-CPU-Alarm —evaluation-periods 1 —comparison-operator GreaterThanThreshold —metrics '[{"Id":"m1","Expression":"SELECT MAX(CPUUtilization) FROM \"AWS/EC2\" WHERE tag.Environment = '\''Prod'\'' AND tag.Application = '\''OrderService'\''", "Period":60}]' —threshold 80 + aws cloudwatch put-metric-alarm --alarm-name Prod-App-CPU-Alarm --evaluation-periods 1 --comparison-operator GreaterThanThreshold --metrics '[{"Id":"m1","Expression":"SELECT MAX(CPUUtilization) FROM \"AWS/EC2\" WHERE tag.Environment = '\''Prod'\'' AND tag.Application = '\''OrderService'\''", "Period":60}]' --threshold 80