AWS AmazonCloudWatch documentation change
Summary
Changed terminology from 'outlier detection' to 'anomaly detection' in billing context
Security assessment
This change only updates terminology from 'outlier detection' to 'anomaly detection' without modifying security-related content. No security vulnerabilities, configurations, or features are mentioned.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md b/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md index 7f68d215b..f485b8503 100644 --- a//AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md +++ b//AmazonCloudWatch/latest/monitoring/cloudwatch_billing.md @@ -519 +519 @@ If you create a metric alarm that contains a metric math expression, which refer -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). +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).