Private Networking (Public Cloud)

Customers using public cloud infrastructure can create a Frame account using Frame-managed networking, Private Networking so users must access the Frame workload VMs using the private IP addresses of the Frame workload VMs. Since the Frame workload VMs have no public IP addresses, the customer must provide a network path between the end user and the private Frame workload VMs. For egress to the Internet, these workload VMs communicate directly to the Internet through a NAT gateway in the public cloud infrastructure.

Customers who choose to create a Frame account in their own managed network where all users access the Frame workload VMs within their private network must follow the networking requirements defined below.

If users must access network resources on-premises or in a private network, a private network connection (e.g., VPN, direct connection, SD-WAN, VPC/VNET peering) with the appropriate routing must be implemented.

FRP8 Networking

FRP8 is a udp-based protocol for all communication between the end user and the Frame workload VMs.

The following table describes the required protocols and ports for Frame accounts using Private Networking and FRP8.