> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating MVE Connections to AWS Direct Connect with Aruba EdgeConnect SD-WAN

> This help topic describes how to create a VXC from an MVE to AWS Direct Connect and integrate the connection with Aruba EdgeConnect SD-WAN.

You can create a network connection from an MVE (an Aruba EC-V) to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF.

You start the AWS connection through the Megaport Portal, accept the connection in AWS, and create an interface for the EC-V in Aruba Orchestrator.

<Tip>
  Aruba provides documentation for their SD-WAN product, including Orchestrator and cloud connections, at the [Aruba Documentation Library](https://arubanetworking.hpe.com/techdocs/sdwan/).
</Tip>

## Before you begin

Before you can create a connection to AWS, you need to satisfy these requirements:

* Create an MVE (Aruba EC-V). For more information, see [Creating an MVE](/mve/aruba/creating).

* 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](/cloud/mve/aruba/aws/mve-aws-hosted) -- 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)](/cloud/mve/aruba/aws/mve-aws-hvif) -- 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.

<Note>
  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.
</Note>