AWS AmazonCloudWatch documentation change
Summary
Changed 'outlier detection' to 'anomaly detection' in network health monitoring context
Security assessment
Terminology update in technical explanation of network monitoring. No security enhancements or vulnerabilities addressed in the change.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/nw-monitor-how-it-works.md b/AmazonCloudWatch/latest/monitoring/nw-monitor-how-it-works.md index 048911ccf..5fc59de05 100644 --- a//AmazonCloudWatch/latest/monitoring/nw-monitor-how-it-works.md +++ b//AmazonCloudWatch/latest/monitoring/nw-monitor-how-it-works.md @@ -59 +59 @@ Network Synthetic Monitor publishes a network health indicator (NHI) metric that -The NHI binary value is based on a statistical measure of the health of the AWS-controlled network path from the AWS hosted resource, where the monitor is deployed, to the Direct Connect location. Network Synthetic Monitor uses outlier detection to calculate availability drops or lower performance along the network paths. +The NHI binary value is based on a statistical measure of the health of the AWS-controlled network path from the AWS hosted resource, where the monitor is deployed, to the Direct Connect location. Network Synthetic Monitor uses anomaly detection to calculate availability drops or lower performance along the network paths. @@ -65 +65 @@ NHI is not accurate for Direct Connect attachments that use intermediary routing -Each time that you create a new monitor, add a probe, or re-activate a probe, the NHI for the monitor is delayed by a few hours while AWS collects data to perform outlier detection. +Each time that you create a new monitor, add a probe, or re-activate a probe, the NHI for the monitor is delayed by a few hours while AWS collects data to perform anomaly detection.