AWS connect documentation change
Summary
Replaced 'Amazon Connect' with 'Connect Customer' in multiple locations including network setup, latency testing, and VDI references
Security assessment
Purely branding/naming changes without any modifications to security protocols, vulnerabilities, or security-related configurations. The 300ms latency threshold remains unchanged.
Diff
diff --git a/connect/latest/adminguide/network-ts.md b/connect/latest/adminguide/network-ts.md index 83048212a..0e2d5955c 100644 --- a//connect/latest/adminguide/network-ts.md +++ b//connect/latest/adminguide/network-ts.md @@ -11 +11 @@ Get startedRun the Endpoint Test UtilityInvestigate network components and devic -Network issues are the number one reason for call quality and disconnect problems in contact centers. Before reading this topic, we recommend that you review [Set up your network to use the Amazon Connect Contact Control Panel (CCP)](./ccp-networking.html) to verify that your network is setup correctly for Amazon Connect. +Network issues are the number one reason for call quality and disconnect problems in contact centers. Before reading this topic, we recommend that you review [Set up your network to use the Connect Customer Contact Control Panel (CCP)](./ccp-networking.html) to verify that your network is setup correctly for Connect Customer. @@ -34 +34 @@ Run the [Endpoint Test Utility](./check-connectivity-tool.html) tool from the af - * This tool helps determine the latency between your Amazon Connect instance and the agent browser. For a successful test, the status is **Success**. The average latency should be not be more than 300 ms. Latency that is above this value could result in potential audio quality issues. + * This tool helps determine the latency between your Connect Customer instance and the agent browser. For a successful test, the status is **Success**. The average latency should be not be more than 300 ms. Latency that is above this value could result in potential audio quality issues. @@ -42 +42 @@ You can also test latency by using the different AWS Regions to test connectivit - * Check whether the agent's workstation is set up correctly: verify they are using a supported browser and verify network connectivity across required ports for media streams. The following image shows the results for an agent workstation that meets all of requirements for Amazon Connect + * Check whether the agent's workstation is set up correctly: verify they are using a supported browser and verify network connectivity across required ports for media streams. The following image shows the results for an agent workstation that meets all of requirements for Connect Customer @@ -57 +57 @@ You can also test latency by using the different AWS Regions to test connectivit - * If there is a VDI setup, follow recommendations in [Use Amazon Connect in a VDI environment](./using-ccp-vdi.html). Were there any changes made? Does the issue occur in a non-VDI setup (in a simple desktop environment). + * If there is a VDI setup, follow recommendations in [Use Connect Customer in a VDI environment](./using-ccp-vdi.html). Were there any changes made? Does the issue occur in a non-VDI setup (in a simple desktop environment).