AWS Security ChangesHomeSearch

AWS connect documentation change

Service: connect · 2026-05-19 · Documentation low

File: connect/latest/adminguide/set-routing-criteria.md

Summary

Updated link text from 'one-click drill-downs' to 'one-choose drill-downs'

Security assessment

Change only modifies navigation link text without altering security content or configurations. No security implications.

Diff

diff --git a/connect/latest/adminguide/set-routing-criteria.md b/connect/latest/adminguide/set-routing-criteria.md
index 384865511..8c39670fd 100644
--- a//connect/latest/adminguide/set-routing-criteria.md
+++ b//connect/latest/adminguide/set-routing-criteria.md
@@ -83 +83 @@ An advantage of choosing this option is that it uses the agent's userID (such as
-The main downside of routing criteria is that it impacts queue metrics (SLA, queue time, and more). If a contact in QueueA is waiting specifically for Agent12, then it won't get picked up by other agents that are available. It may breach your defined SLAs. The way you'd see this occurring is by looking at the real-time metrics report; see [Use one-click drill-downs](./one-click-drill-downs.html).
+The main downside of routing criteria is that it impacts queue metrics (SLA, queue time, and more). If a contact in QueueA is waiting specifically for Agent12, then it won't get picked up by other agents that are available. It may breach your defined SLAs. The way you'd see this occurring is by looking at the real-time metrics report; see [Use one-choose drill-downs](./one-choose-drill-downs.html).