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.

  To ensure proper network communication to the Frame Platform there are two Backends available depending on which one    should be used for the connection for services and VMs please refer to the corresponding networking requirements:
  USE (located in the United states- Location AWS Datacenter  Virginia) 
  DEU ( located in European Union - Location AWS Datacenter Frankfurt)

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.

  Dizzion is in the process of migrating from *.nutanix.com to *.difr.com domain. For the
  time being, the additional difr.com domains will need to be whitelisted in addition to the
  existing nutanix.com domains. At a later time, once Dizzion has confirmed there is no
  dependencies on the nutanix.com domains, we will send out a communication notifying
  customers that all nutanix.com domains can be safely removed from your whitelist
  configurations.

  IMPORTANT: For IMG Domains, Customers can whitelist new IMG difr domains but
  should NOT change SAML 2 configurations to use new difr.com domains. SAML 2
  configurations should continue to use img.console.nutanix.com and
  img.frame.nutanix.com until further direction from Dizzion.

USE: Private Networking (Public Cloud)

FRP8 Networking - EU

The following table lists the required protocols and ports for Frame accounts using Private Networking and FRP8, specifically for organizations electing to use Dizzion's EU control plane.

DEU: Private Networking (Public Cloud)

FRP7 Networking End of Life

FRP7 reached end-of-life (EOL) as of June 30, 2024. Refer to the EOL Announcement of December 18, 2023 for further details.