AWS prescriptive-guidance documentation change
Summary
Updated terminology from 'IP-based controls' to 'IP-based rules', removed link from 'rate-based rules', changed 'Bot control deployment' section title to 'Implementation strategy', and standardized product name to 'Amazon CloudWatch'
Security assessment
Changes are editorial improvements (terminology consistency, link removal, section renaming) without addressing vulnerabilities or adding security features. No evidence of security incident remediation.
Diff
diff --git a/prescriptive-guidance/latest/bot-control/monitoring.md b/prescriptive-guidance/latest/bot-control/monitoring.md index c1ff0ed89..47713e041 100644 --- a//prescriptive-guidance/latest/bot-control/monitoring.md +++ b//prescriptive-guidance/latest/bot-control/monitoring.md @@ -7 +7 @@ -Tracking top rulesTracking top labels and namespacesCreating math expressionsUsing anomaly detectionUsing CloudWatch metricsBuilding a dashboard +Tracking top rulesTracking top labels and namespacesCreating math expressionsUsing anomaly detectionUsing Amazon CloudWatch metricsBuilding a dashboard @@ -25 +25 @@ Next, this guide provides recommendations for how to start monitoring bot traffi -Tracking the top-hit rules can highlight trends and potentially anomalous activities. Increased rates for a specific rule might indicate a potential false positive or targeted activity that you should investigate. The most common rule for tracking would be [IP-based controls](./static-controls.html#ip-based-controls), geo-blocking rules (a spike here can show traffic from unusual countries, which might not be automatically blocked), and [Rate-based rules](./static-controls.html#rate-based-rules). These rules would always have inherent variation, but an anomaly in the traffic pattern can be indicative of bot activity. Take this into consideration if you're manually setting the thresholds. +Tracking the top-hit rules can highlight trends and potentially anomalous activities. Increased rates for a specific rule might indicate a potential false positive or targeted activity that you should investigate. The most common rule for tracking would be [IP-based rules](./static-controls.html#ip-based-controls), geo-blocking rules (a spike here can show traffic from unusual countries, which might not be automatically blocked), and rate-based rules. These rules would always have inherent variation, but an anomaly in the traffic pattern can be indicative of bot activity. Take this into consideration if you're manually setting the thresholds. @@ -91 +91 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Bot control deployment +Implementation strategy