> ## 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 an AWS Hosted VIF for an MVE with Aruba EdgeConnect SD-WAN

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

export const Gloss = ({term, anchor, langDir = 'en'}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Gloss -';
  if (typeof term !== 'string') {
    term = String(term);
  }
  if (typeof anchor !== 'string') {
    anchor = String(anchor);
  }
  if (!term || term === 'undefined') {
    console.error(`${errorPrefix} the \`term\` property is required — rendering an empty string instead`);
    return <></>;
  }
  if (!anchor || anchor === 'undefined') {
    console.error(`${errorPrefix} the \`anchor\` property is required — rendering an empty string instead`);
    return <></>;
  }
  const lang = langDir === 'en' ? '/' : '/' + langDir + '/';
  const glossaryPage = lang + 'glossary/#' + anchor;
  return <a href={glossaryPage}>{term}</a>;
};

export const Image = ({src, alt = '', caption, width, height, shadow}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  const img = <img className={['mega-image-style', shadow ? 'shadow' : ''].join(' ')} src={src} alt={alt} width={width} height={height} style={{
    display: 'block'
  }} />;
  return caption ? <figure>
      {img}
      <figcaption style={{
    textAlign: 'center',
    width
  }}>{caption}</figcaption>
    </figure> : img;
};

export const InlineImage = ({src, alt, height = 16, shadow, width}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: InlineImage -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  if (typeof alt !== 'string') {
    alt = String(alt);
  }
  if (alt === 'undefined') {
    console.error(`${errorPrefix} \`alt\` is required (use "" for decorative images) — rendering an empty string instead`);
    return <></>;
  }
  if (height) {
    height = height.toString().replaceAll(/\D/g, '');
  }
  if (width) {
    width = width.toString().replaceAll(/\D/g, '');
  }
  return <img className={['inline-icon', shadow ? 'shadow' : null, 'm-0'].filter(Boolean).join(' ')} src={src} alt={alt} height={height} width={width} style={{
    display: 'inline',
    verticalAlign: 'middle',
    maxHeight: height ? `${height}px` : undefined,
    maxWidth: width ? `${width}px` : undefined,
    height: height ? `${height}px` : undefined,
    width: width ? `${width}px` : undefined
  }} />;
};

export const Link = ({href, children}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Link -';
  if (typeof href !== 'string') {
    href = String(href);
  }
  if (!href || href === 'undefined') {
    console.error(`${errorPrefix} the \`href\` property is required — rendering an empty string instead`);
    return <></>;
  }
  if (href.includes('{') || href.toUpperCase().includes('%7B')) {
    console.error(`${errorPrefix} could not resolve a variable in href "${href}" — rendering an empty string instead`);
    return <></>;
  }
  const isExternal = (/^https?:\/\//).test(href);
  return <a href={href} className="link" target={isExternal ? '_blank' : undefined} rel={isExternal ? 'noreferrer' : undefined}>
      {children ?? href}
      {isExternal && <span className="sr-only"> (opens in a new tab)</span>}
    </a>;
};

Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.

<Note>
  AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
</Note>

**To create a connection to an AWS Hosted VIF from the Megaport Portal**

1. In the <Link href="https://portal.megaport.com">Megaport Portal</Link>, go to the **Services** page and select the MVE for the connection.

2. Click **+Connection** then click **Cloud**.

3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
   You can use the Select Destination Port search field to narrow the selection.
   <Image src="/images/cloud/megaport/aws/aws-hosted-vif.png" alt="Add Hosted VIF connection" shadow={true} width={700} />

4. Specify the connection details:

   * **Connection Name** -- The name of your VXC to be shown in the <Link href="https://portal.megaport.com">Megaport Portal</Link>.

     <Tip>
       Match this to the AWS Connection Name on the next screen for easy mapping.
     </Tip>

   * **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.

   * **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.

   * **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).

     <Note>
       If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
     </Note>

   * **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aruba/creating-mve-manual#creating-mve).

   * **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
     This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.

   * **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).

     Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term,  the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.

     For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).

   * **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
     To add a tag:
     1. Click **Add Tags**.
     2. Click  **Add New Tag**.
     3. Enter details into the fields:
        * **Key** -- string maximum length 128. Valid values are a-z 0-9 \_ : . / \ -
        * **Value** -- string maximum length 256. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
     4. Click **Save**.
        If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
     <Warning>
       Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
     </Warning>

   <Image src="/images/cloud/mve/portal-cloud-create-details.png" alt="Connection details" shadow={true} width={550} />

5. Click **Next**.

6. Specify the details for the AWS service.

   <Image src="/images/cloud/mve/aws-hv-connection-details-mp.png" alt="AWS connection details" shadow={true} width={700} />

   Here are details for each field:

   * Select **Public** or **Private**.
     * **Private** -- Access private AWS services such as a VPC, EC2
       instances, load balancers, RDS DB instances, on private IP address
       space.
     * **Public** -- Access public AWS services such as Amazon Simple Storage
       Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive
       [Amazon's global IP
       prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html)
       (approximately 2,000 prefixes).

       <Note>
         Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
       </Note>

   * **AWS Connection Name** -- This is a text field and will be the name
     of your virtual interface that appears in the AWS console. The AWS
     Connection Name is automatically populated with the name specified in a
     previous step.

   * **AWS Account ID** -- This is the ID of the account you want to
     connect. You can find this value in the management section of your
     AWS console.

   * **Customer ASN** (optional) -- Specify the ASN used for BGP peering sessions on any VXCs connected to the MVE. This value is defined when you configure the MVE and, once defined, it cannot be changed.

   * **BGP Auth Key** (optional) -- Specify the BGP <Gloss term="MD5" anchor="md5" /> key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
     <Note>
       The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
     </Note>

   * **Customer IP Address** -- The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.

   * **Amazon IP Address** -- The IP address space in CIDR format
     assigned in the AWS VPC network for peering. This field is
     optional for private connections and if left blank, Megaport automatically assigns an
     address.

   * **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).

     Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.

7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.

8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.

9. Review the Important Information section and confirm agreement with the Service Agreements.

   If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.

   The promotional discount appears below the Standard Term discount.  This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing.  If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.

   <Image src="/images/snippets/add-promo-code.png" alt="Add Promo Code" shadow={true} width={750} />

   If you entered an incorrect promotion code, you can remove it by clicking **Remove**.

10. Click **Order Now**.

The AWS VXC appears as a connection for the MVE in the Megaport Portal.

<Image src="/images/cloud/mve/aruba/aws/aws-vxc-mve.png" alt="VXC details" shadow={true} width={700} />

Next, accept the connection in AWS.

#### Accepting the Virtual Interface for Private Connections

A few minutes after ordering a private Hosted VIF VXC, the corresponding inbound VIF request is visible on the AWS Direct Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with the target AWS port.) If your VIF doesn't appear after a few minutes, confirm you are viewing the correct region.

**To review and accept the private virtual interface**

1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
   of the interface to display the configuration and peering details.

   <Image src="/images/cloud/mcr/aws-hv-accept-virtual-interface.png" alt="Accepting AWS Virtual Interfaces" shadow={true} width={800} />

   The name and account ID of the VIF should match the values supplied in
   the Portal and the BGP ASN should match the Customer ASN configured with
   the VXC. The Amazon ASN is the default region's AWS ASN and
   not the value specified during the configuration - this is
   updated when the virtual interface is accepted and assigned.

2. Click **Accept**.

3. Select the gateway type and then the specific gateway for this new
   virtual interface.
   <Image src="/images/cloud/mcr/aws-hv-aws-gateway.png" alt="Specify a gateway" shadow={true} width={600} />

4. Click **Accept virtual interface**.

The state of the connection changes from *confirming* to *pending*, and then changes to *available* once BGP is established. Note that sometimes there is a delay in the *available* BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.

#### Accepting the Virtual Interface for Public Connections

Several minutes after ordering a public Hosted VIF VXC, the
corresponding inbound VIF request appears on the **AWS Direct
Connect > Virtual Interfaces** page in the AWS console. (This is specific to the region associated with the target AWS port.)

**To review and accept the public virtual interface**

1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
   of the interface to display the configuration and peering details.
2. Review the configuration details and click **Accept**, and when
   prompted, click **Confirm**.

The state of the connection changes from *confirming* to *verifying*. At
this point, the connection needs to be verified by Amazon - a process
that can take up to 72 hours. When verified, the state changes to
*available*.

## Adding AWS connection details to Aruba Orchestrator

After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Aruba Orchestrator. This involves adding a LAN interface and configuring BGP settings, ASNs, VLANs, and MD5 values.

**To add a LAN interface in Aruba Orchestrator**

1. Collect the connection details from the Megaport Portal.

   To display the details, click the gear icon <InlineImage src="/images/cloud/mve/aruba/aws/gear-icon.png" alt="Gear icon" /> for the AWS connection from your MVE and click the **Details** view. Note the values for the **A-End VLAN**, **Customer Address** (and **CIDR**), **Amazon Address**, and **Customer ASN**.

   <Image src="/images/cloud/mve/aruba/aws/aws-connection-details-mp.png" alt="AWS connection details" shadow={true} width={700} />

2. Log in to Aruba Orchestrator.

3. Go to Configuration > Networking | Deployment.

4. Locate the appliance by the hostname and click the Edit (pencil) icon.

   <Image src="/images/mve/aruba/aruba-edit-icon.png" alt="Edit appliance" shadow={true} width={700} />

5. If you do not have a wan0 LAN side interface: Click **+Add** next to LAN Interfaces and in the Interface drop-down menu, choose wan0.

   If you already have a wan0 LAN interface, click **+IP** to add a new configuration.

6. In the **VLAN** field, enter the A-End VLAN for the AWS connection from the Megaport Portal.

7. (Optional) Select a preconfigured Label or select None.

8. In the **IP/Mask** field, enter the IP address and mask for the MVE side of the AWS connection.

   This value is the Customer Address from the AWS connection details in the Portal.

9. For the Next Hop, enter the IP address for the Amazon side of the connection.

10. Specify in and out bandwidth values.

    The bandwidth must be equal to or less than the MVE bandwidth limit.

    This image shows sample configuration values.

    <Image src="/images/cloud/mve/aruba-add-interface.png" alt="Aruba LAN interface details" shadow={true} width={900} />

11. Click **Apply**.

12. If prompted, reboot the appliance.

    A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.

Once the device is reachable from Orchestrator, you can configure a BGP session.

1. In Orchestrator, go to Configuration > Networking | Routing | BGP.

2. Click the Edit (pencil) icon for the appliance.

3. Move the slider to **Enable BGP**.

4. Provide the autonomous system number (ASN).

   This is the Customer ASN (your local MVE), collected in Step 1.

5. In the **Router ID** field, enter a system IP as required by your network design.

   You can use any IP address on the MVE, such as the loopback 0 IP specified during the initial acceptance of the appliance, the interface IP on the MVE side of the VXC, or the transit IP address.

   <Image src="/images/mve/aruba/aruba-enable-bgp.png" alt="Aruba enable BGP" shadow={true} width={900} />

6. In the BGP Peers section, click **Add** and provide the following information:

   * **Peer IP** -- This is the Amazon IP address, collected in Step 1 from the connection details.
   * **Local Interface** -- Choose the associated LAN interface (the interface is in the format *wan0+VLAN*).
   * **Peer ASN** -- This is the AWS ASN. By default, this value is 64512.
   * **Peer Type** -- Choose Branch.
   * **Enable <Gloss term="MD5" anchor="md5" /> Password** -- If required, select this and then enter and confirm your MD5 password.

   <Image src="/images/cloud/mve/aruba-add-bgp-peer.png" alt="Add BGP peer for Aruba" shadow={true} width={500} />

7. Click **Add**.

8. Click **Apply**.

It takes several seconds for the configuration to be pushed to the appliance.
Click the refresh icon to update the data from the appliance.

When successful, the Peer State is *Established*:

<Image src="/images/cloud/mve/aruba/aruba-bgp-status-established.png" alt="BGP peer state for Aruba" shadow={true} width={1000} />

You can also check the BGP status for the VIF in the AWS console and verify the AWS BGP session is up:

<Image src="/images/cloud/mve/aruba/aws/aruba-bgp-status-aws.png" alt="BGP peer state for Aruba in AWS console" shadow={true} width={900} />

## Validating your AWS connection

You can review connection details, including the connection state, from the CLI with these commands:

* `show interface wan0.<subinterface id>` -- Displays configuration details and current status for the appliances.
* `show bgp neighbors` or `show bgp summary` -- Displays configuration details and current status for the BGP neighbors.

**To start a CLI session from Orchestrator**

1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
   <Image src="/images/mve/aruba/cli-appliance-menu.png" alt="BGP peer state for Aruba" shadow={true} width={600} />

2. Choose CLI Session from the menu.
   <Image src="/images/mve/aruba/cli-cli-session.png" alt="BGP peer state for Aruba" shadow={true} width={600} />

3. Enter **enable** mode to use the recommended CLI commands to display configuration details.