Workspace streaming through Direct Connect

0

Hello All, Regarding AWS workspaces. After authentication, I know that the streaming takes place via the streaming gateway, through the internet.

we have an on-premise connection to AWS using Direct connect.

users are using the workspace client to connect to the workspace instances. Can we change the routing of the streaming to use the Direct connect instead of the public internet ? so that the connection is between the client and the workspace via direct connect ?

Amr
已提问 3 个月前250 查看次数
1 回答
1

Hi, The use of a public virtual interface (VIF) provides access to the WorkSpaces service for streaming traffic. Using a public VIF to transport WorkSpaces streaming traffic offers a reliable network transport option for users accessing WorkSpaces from an on-premises network. This provides a consistent user experience by mitigating common network connection issues like latency and packet loss. That a look at how you create Direct connect Public VIF and what the requirements are such Peering IPs etc

Reference :

profile pictureAWS
已回答 3 个月前
profile pictureAWS
专家
已审核 3 个月前
  • In shameless self-promotion, an explanation of Public VIF on Direct Connect: https://www.youtube.com/watch?v=X_4ekgRc4C8&t=328s

  • as far as I understand, the Workspaces instance has a public IP assigned to its management interface, How can I force the streaming traffic to use Direct connect public VIF ? Sorry but I did not work on Direct connect before so I have little knowledge in this part

  • Packets are routed on the network via the "best" path - which is usually the shortest (i.e. least number of other networks between the source and destination). By using a Public VIF you are normally creating a shorter path between your network and AWS. A Public VIF uses public IP addresses so basically it becomes a shortcut "around" the internet for AWS-specific IP addresses.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则