AWS AmazonCloudWatch documentation change
Summary
Updated network monitoring explanation to use 'outlier detection' instead of 'anomaly detection'
Security assessment
Terminology change in network health calculation methodology. No security vulnerabilities addressed or security features documented in the modified text.
Diff
diff --git a/AmazonCloudWatch/latest/monitoring/nw-monitor-how-it-works.md b/AmazonCloudWatch/latest/monitoring/nw-monitor-how-it-works.md index 1db229be7..0aaeb5048 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 anomaly 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 outlier detection to calculate availability drops or lower performance along the network paths. @@ -65 +65 @@ NHI is not accurate for AWS Direct Connect attachments that use intermediary rou -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. +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.