AWS AmazonCloudWatch documentation change
Summary
Changed terminology from 'anomaly detection' to 'outlier detection' in billing context
Security assessment
Change appears to be a terminology update (anomaly -> outlier detection) without addressing security vulnerabilities or introducing security features. No security implications identified in billing context.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md b/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md index f807c3f87..a6628cff6 100644 --- a//AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md +++ b//AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md @@ -522 +522 @@ If you create a metric alarm that contains a metric math expression, which refer -If you create an anomaly detection alarm, where your alarm analyzes past metric data to create a model of expected values, you incur a cost for each alarm-metric that's referenced in your alarm plus two additional metrics, one for the upper and lower band metrics that the anomaly detection model creates. For information about how to create an anomaly detection alarm, see [Creating a CloudWatch alarm based on anomaly detection](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create_Anomaly_Detection_Alarm.html). +If you create an outlier detection alarm, where your alarm analyzes past metric data to create a model of expected values, you incur a cost for each alarm-metric that's referenced in your alarm plus two additional metrics, one for the upper and lower band metrics that the outlier detection model creates. For information about how to create an outlier detection alarm, see [Creating a CloudWatch alarm based on outlier detection](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create_Anomaly_Detection_Alarm.html).