Creating MVE Connections to AWS Direct Connect with Aruba EdgeConnect SD-WAN
You can create a network connection from an MVE (an Aruba EC-V) to AWS with Virtual Cross Connections (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF.
You initiate the AWS connection through the Megaport portal, accept the connection in AWS, and create an interface for the EC-V in Aruba Orchestrator.
Aruba provides documentation for their SD-WAN product, including Orchestrator and cloud connections, at Aruba (SilverPeak) Documentation Library.
Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
Create an MVE (Aruba EC-V). For details, 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 with a capacity of 500 Mbps or less can support one private or public virtual interface. A Hosted Connection with a capacity of 1 Gbps or more 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 Aruba SD-WAN does not include automatically configure the MVE in Aruba and you need to manually create a LAN interface and define VLANs, IP addresses, MD5 values, and BGP peers in the Aruba Orchestrator console.