AWS AmazonCloudWatch documentation change
Summary
Changed terminology from 'outlier detection' to 'anomaly detection' in the description of CloudWatch usage metrics features.
Security assessment
This is a terminology update from 'outlier detection' to 'anomaly detection'. No security vulnerabilities, incidents, or security features are mentioned. The change appears to be a branding or terminology standardization.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/CloudWatch-Service-Quota-Integration.md b/AmazonCloudWatch/latest/monitoring/CloudWatch-Service-Quota-Integration.md index 83ba00b81..2b0773dc3 100644 --- a//AmazonCloudWatch/latest/monitoring/CloudWatch-Service-Quota-Integration.md +++ b//AmazonCloudWatch/latest/monitoring/CloudWatch-Service-Quota-Integration.md @@ -7 +7 @@ -CloudWatch collects metrics that track the usage of some AWS resources and APIs. These metrics are published in the `AWS/Usage` namespace. Usage metrics in CloudWatch allow you to proactively manage usage by visualizing metrics in the CloudWatch console, creating custom dashboards, detecting changes in activity with CloudWatch outlier detection, and configuring alarms that alert you when usage approaches a threshold. +CloudWatch collects metrics that track the usage of some AWS resources and APIs. These metrics are published in the `AWS/Usage` namespace. Usage metrics in CloudWatch allow you to proactively manage usage by visualizing metrics in the CloudWatch console, creating custom dashboards, detecting changes in activity with CloudWatch anomaly detection, and configuring alarms that alert you when usage approaches a threshold.