Skip to main content
You can create a network connection from an MVE for Arista VeloCloud SD-WAN (an Edge) to AWS with a Virtual Cross Connects (VXC) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted Virtual Interface (Hosted VIF). You start the AWS connection through the Megaport Portal, accept the connection in AWS, and create a subinterface for the edge in Orchestrator.
Arista provides documentation for their SD-WAN product, including cloud connections, at VeloCloud SD-WAN Documentation.

​
Before you begin

Before you can create a connection to AWS, you need to satisfy these requirements:
  • Create an MVE (Edge). For more information, see Creating an MVE.
  • In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations.

​
Creating a connection to AWS from the MVE

With an MVE already created, you can create a connection to AWS. The VXC connection can be one of two AWS models:
  • Hosted Connections — A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
  • Hosted Virtual Interfaces (Hosted VIFs) — Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. Hosted VIF connections share bandwidth.
Click the link for your preferred connection type for detailed configuration steps.
Creating a connection from the MVE instance to AWS is very similar to creating a connection from a Port or an MCR. The primary difference is the process with Arista VeloCloud SD-WAN does not automatically configure the MVE in Orchestrator and you need to manually create a subinterface and define VLANs, IP addresses, MD5 values, and BGP peers in the Orchestrator console.
Last modified on August 21, 2026