AWS connect medium security documentation change
Summary
Added documentation about browser enterprise policy requirements for Chrome/Edge version 147+ to allow local network access for screen recording functionality.
Security assessment
This change addresses a security-related browser policy change (Local Network Access restrictions) that will break screen recording functionality in future browser versions. It provides specific registry commands and policy configurations to maintain functionality, indicating proactive documentation for an upcoming security-related change that could impact monitoring capabilities.
Diff
diff --git a/connect/latest/adminguide/sr-system-req.md b/connect/latest/adminguide/sr-system-req.md index cce58a570..cb3fab239 100644 --- a//connect/latest/adminguide/sr-system-req.md +++ b//connect/latest/adminguide/sr-system-req.md @@ -7 +7 @@ -System requirementsNetwork requirements +System requirementsNetwork requirementsBrowser enterprise policy for local network access @@ -59,0 +60,21 @@ When Windows multi-session configuration is enabled allowing multiple agents to +## Browser enterprise policy for local network access + +Starting with Google Chrome version 147 (released April 7, 2026) and Microsoft Edge version 147 (released April 10, 2026), Chromium-based browsers enforce Local Network Access (LNA) restrictions on WebSocket connections. This restriction blocks the local WebSocket connection between the Contact Control Panel and the Amazon Connect Client Application, causing screen recordings to fail. + +To ensure screen recording works on Chrome 147 or later and Edge 147 or later, deploy the **LoopbackNetworkAllowedForUrls** enterprise policy to your agents' workstations. This policy pre-grants loopback network access permission for your Contact Control Panel domain, so agents are not blocked or prompted. Configure this policy with your Amazon Connect Contact Control Panel URL. Example policy value: `[*.]my.connect.aws` + + * For Google Chrome, see [LoopbackNetworkAllowedForUrls](https://chromeenterprise.google/policies/#LoopbackNetworkAllowedForUrls) in the Chrome enterprise policy documentation. + + * For Microsoft Edge, see [LoopbackNetworkAllowedForUrls](https://learn.microsoft.com/en-us/deployedge/microsoft-edge-browser-policies/loopbacknetworkallowedforurls) in the Edge enterprise policy documentation. + + + + +The following example commands set the registry policy for the domain `[*.]my.connect.aws` on Windows: + + + reg add "HKLM\SOFTWARE\Policies\Google\Chrome\LoopbackNetworkAllowedForUrls" /v 1 /t REG_SZ /d "[*.]my.connect.aws" + reg add "HKLM\SOFTWARE\Policies\Microsoft\Edge\LoopbackNetworkAllowedForUrls" /v 1 /t REG_SZ /d "[*.]my.connect.aws" + +For more details on this browser change, see [New permission prompt for Local Network Access](https://developer.chrome.com/blog/local-network-access) in the Chrome developer documentation. +