1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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 :
répondu il y a 3 mois
Contenus pertinents
- demandé il y a 20 jours
- demandé il y a un an
- demandé il y a 10 mois
- demandé il y a un an
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 6 mois
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.