Private Connectivity

Enable customers the option to maintain Fabric Remote Connection routing within Canadian geographic boundries

Enable customers to create 25G Remote Virtual Circuits between select Metros. This will first be enabled for customers to connect to themselves for Data Center Interconnect use cases, but will be expanded to connect to 3rd parties in later releases.

Enable customers the option to maintain Fabric Remote Connection routing within Continental United States geographic boundaries

It would be great to have the workflow for creating shared Fabric connections automated similar to how it works on AWS. The proposed workflow is as follows: Creation: User creates Fabric connection in Fabric portal towards Equinix Metal. Automation generates a connection that is pending for approval on the Equinix Metal portal. (Should also be able to do auto approval when using automation tools such as Terraform) User approves the connection on the Equinix Metal portal and can then associate the virtual circuit with their internal VLAN. Deletion: User deletes Connection in Equinix Metal portal which also automatically deletes the connection on the Fabric portal.

Support a dedicated (HA pair) port option for Fabric and other interconnection needs in Metal.

Connect to Equinix Metal from ECX, allowing you to create connections between your bare metal compute infrastructure in a Layer 2 VLAN and other clouds, colocation or network providers.