AWS connect documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in network considerations section
Security assessment
Terminology adjustment without security context - maintains existing network security guidance
Diff
diff --git a/connect/latest/adminguide/using-ccp-vdi.md b/connect/latest/adminguide/using-ccp-vdi.md index ee2202381..15da0a5b7 100644 --- a//connect/latest/adminguide/using-ccp-vdi.md +++ b//connect/latest/adminguide/using-ccp-vdi.md @@ -33 +33 @@ If you use Citrix, Amazon WorkSpaces, or Omnissa cloud desktops, you can create - * **Network** —Each hop that traffic goes through between endpoints increases the possibility of failure and adds opportunity to introduce latency. VDI environments are particularly susceptible to call quality issues if the underlying route is not optimized or the pipe isn't either fast or wide enough. While AWS Direct Connect can improve call quality from the edge router to AWS, it will not address internal routing issues. You may need to upgrade or optimize your private LAN/WAN, or redirect to an external device to circumvent call audio issues. In most scenarios, if this is required, the CCP is not the only application that is having issues. + * **Network** —Each hop that traffic goes through between endpoints increases the possibility of failure and adds opportunity to introduce latency. VDI environments are particularly susceptible to call quality issues if the underlying route is not optimized or the pipe isn't either fast or wide enough. While Direct Connect can improve call quality from the edge router to AWS, it will not address internal routing issues. You may need to upgrade or optimize your private LAN/WAN, or redirect to an external device to circumvent call audio issues. In most scenarios, if this is required, the CCP is not the only application that is having issues.