Setting up a VPN¶
A Virtual Private Network (VPN) securely connects a user to an existing network (usually at the office). Once this connection is established, users running on Frame can securely access resources from the network such as file servers or license servers. With the Frame platform, there are two options for setting up a VPN connection:
A. Install Remote-Access VPN Client Software on Frame¶
Installing a software VPN client will allow you to quickly publish a VPN client to all of your users. Simply install the VPN client software in the Sandbox and test the connection before publishing to your production instances. When setting up your VPN client, you must use a split-tunnel configuration to ensure Frame’s stream-related traffic does not get rerouted. If Frame’s traffic gets rerouted through a VPN, our systems will lose connection to the VM resulting in a complete disconnection.
Once the client has been published, users will need to log in to the VPN client in order to access on-premises resources.
It is also possible to automatically prompt users to login via VPN when they start a session on Frame by using pre-session scripts.
Frame works with Cisco AnyConnect, GlobalProtect, OpenVPN, and SonicWall services. Any other VPN clients that support split-tunnel configurations should work as well.
B. Add a VPN Gateway for Site-to-Site Connection¶
A VPN gateway is a connection point for one or multiple VPN tunnels. Frame allows you to setup a VPN gateway in your VPC/VNet. There are additional charges for running a VPN gateway 24/7, however, this ensures that your VPC/VNet will always be securely connected to the end-point it was configured for.
Learn more about VPN gateways by checking out the documentation below: