AWS connect documentation change
Summary
Updated references from 'AWS Direct Connect' to 'Direct Connect' throughout the document, likely reflecting branding/terminology standardization
Security assessment
The changes are purely terminological updates (removing 'AWS' from service names) without altering technical content or security recommendations. No security vulnerabilities, mitigations, or security features are being addressed or added.
Diff
diff --git a/connect/latest/adminguide/ccp-networking.md b/connect/latest/adminguide/ccp-networking.md index 14e8d8cde..e05ac0771 100644 --- a//connect/latest/adminguide/ccp-networking.md +++ b//connect/latest/adminguide/ccp-networking.md @@ -5 +5 @@ -Option 1 (recommended): Replace Amazon EC2 and CloudFront IP range requirements with a domain allowlistOption 2 (not recommended): Allow IP address rangesAbout Amazon Connect IP address rangesStateless firewallsAllow upload of time-off balances and allowances in Amazon Connect schedulingAllow DNS resolution for softphonesPort and protocol considerationsRegion selection considerationsAgents using Amazon Connect remotelyRerouting audioUsing AWS Direct Connect +Option 1 (recommended): Replace Amazon EC2 and CloudFront IP range requirements with a domain allowlistOption 2 (not recommended): Allow IP address rangesAbout Amazon Connect IP address rangesStateless firewallsAllow upload of time-off balances and allowances in Amazon Connect schedulingAllow DNS resolution for softphonesPort and protocol considerationsRegion selection considerationsAgents using Amazon Connect remotelyRerouting audioUsing Direct Connect @@ -41 +41 @@ The following sections describe the two primary connectivity options for using t - * Using AWS Direct Connect + * Using Direct Connect @@ -292 +292 @@ When rerouting audio to an existing device, consider the location of the device -## Using AWS Direct Connect +## Using Direct Connect @@ -294 +294 @@ When rerouting audio to an existing device, consider the location of the device -Contact Control Panel (CCP) network connectivity issues are most often rooted in your route to AWS using private WAN/LAN, ISP, or both. While AWS Direct Connect does not solve issues specific to private LAN/WAN traversal to your edge router, it can help solve for latency and connectivity issues between your edge router and AWS resources. AWS Direct Connect provides a durable, consistent connection rather than relying on your ISP to dynamically route requests to AWS resources. It also allows you to configure your edge router to redirect AWS traffic across dedicated fiber rather than traversing the public WAN. +Contact Control Panel (CCP) network connectivity issues are most often rooted in your route to AWS using private WAN/LAN, ISP, or both. While Direct Connect does not solve issues specific to private LAN/WAN traversal to your edge router, it can help solve for latency and connectivity issues between your edge router and AWS resources. Direct Connect provides a durable, consistent connection rather than relying on your ISP to dynamically route requests to AWS resources. It also allows you to configure your edge router to redirect AWS traffic across dedicated fiber rather than traversing the public WAN.