Skip to main content
This topic describes the API procedure to create a VXC from an MVE to AWS, including how to look up AWS locations and order VXCs on specific vNICs. You can set up two types of AWS connections to an MVE: an AWS Hosted VIF and an AWS Hosted Connection. You can distinguish the type of connection supported by partner locations using the connectType parameter. Hosted VIF connections are connectType=AWS and Hosted Connections are connectType=AWSHC. The MVE to AWS deployment includes these tasks:
  1. Look up AWS location details To create a VXC to AWS, you first need to identify the productUid of the port you want to connect to. You can look up AWS locations for the B-End of the connection with the v2/dropdowns/partner/megaports endpoint.
  2. Create and deploy a VXC With the port details identified, you can create the VXC to AWS from the MVE. Configuration details are specified in the Body of the request. Some of the key information you need to specify include the productUid of the MVE, the productUid of the AWS port, and the AWS account ID.
Before you begin, obtain a valid access token. For more information, see Creating an API Key.

​
Look up AWS location details

Use the API to look up the productUid of the port you want to connect to. The response includes details of the available ports. You need the port details to create the VXC. In the API response, available ports that accept VXCs are listed as "vxcPermitted": true. To look up AWS location details
  1. Expand the Locations folder in the left navigation and click GET Partner Megaports.
  2. Click Send to make a GET request to the API server.
    This request returns all the interfaces Megaport has with Cloud Service Providers. You can search by clicking the magnifying glass and entering a location, data center, or other parameter in the search field. The connectType indicates the Cloud Service Provider. AWS includes “AWS” for Hosted VIFs and “AWSHC” for Hosted Connections. You can filter the results by connectType and vxcPermitted.
    This example uses a port in the region eu-west-2 (London) that accepts VXCs ("vxcPermitted": true).

​
Create and deploy a VXC Hosted VIF

With the port details, create the VXC to AWS from the MVE. You specify the configuration details in the Body of the request. The first productUid identifies the MVE ID and the bEnd: productUid identifies the AWS port location from the Partner Megaports lookup. You also need to provide your AWS account number in the request. This example uses the Hosted VIF connection type, connectType=AWS.
To test your request before you order and see pricing details, use the /v3/networkdesign/validate endpoint with the same Body configuration.
To create a VXC
  1. Create a request with the POST Buy AWS - Hosted VIF (v3) endpoint:
  2. Update the Body of the request with the productUid of the MVE, the name of the VXC, the productUid of the AWS port, and the AWS account ID (ownerAccount).
    You can also change additional values, such as rate limit, contract term, VLAN ID, ASN values, authKey, and IP addressing. The vNIC is determined by vNicIndex, innerVlan identifies VLAN number run within the vNIC, in this case 103.
The vNIC number relates to the following MVE interfaces:
  • vNIC 0 = interface 1 on the MVE
  • vNIC 1 = interface 2 on the MVE
  • vNIC 2 = interface 3 on the MVE
  • vNIC 3 = interface 4 on the MVE
  • vNIC 4 = interface 5 on the MVE
Here is a sample request:
After sending the request, you will receive a successful response when the VXC has been ordered. Here is a sample response:
The VXC will now appear in the Megaport Portal. For this example, the AWS Hosted VIF will appear in the AWS portal account under Direct Connect - Virtual Interfaces. The account holder can accept the Virtual Interface and connect it to a Virtual Private Gateway or a Direct Connect Gateway and then to their VPCs.

​
Create and deploy a VXC Hosted Connection

With the port details, create the VXC to AWS from the MVE. You specify the configuration details in the Body of the request. The first productUid identifies the MVE ID and the bEnd: productUid identifies the AWS port location from the Partner Megaports lookup. You also need to provide your AWS account number in the request. This example uses the Hosted Connection connection type, connectType=AWSHC.
To test your request before you order and see pricing details, use the /v3/networkdesign/validate endpoint with the same Body configuration.
To create a VXC
  1. Create a request with the POST Buy AWS - Hosted Connection (v3) endpoint:
  2. Update the Body of the request with the productUid of the MVE, the name of the VXC, the productUid of the AWS port, and the AWS account ID (ownerAccount).
    You can also change additional values, such as rate limit, contract term, VLAN ID, ASN values, authKey, and IP addressing. The vNIC is determined by vNicIndex, innerVlan identifies VLAN number run within the vNIC, in this case 666.
The vNIC number relates to the following MVE interfaces:
  • vNIC 0 = interface 1 on the MVE
  • vNIC 1 = interface 2 on the MVE
  • vNIC 2 = interface 3 on the MVE
  • vNIC 3 = interface 4 on the MVE
  • vNIC 4 = interface 5 on the MVE
Here is a sample request:
After sending the request, you will receive a successful response when the VXC has been ordered. Here is a sample response:
The VXC will now appear in the Megaport Portal. For this example, the AWS Hosted Connection will appear in the AWS portal account under Direct Connect - connection. The account holder can accept the Hosted Connection and create one private, one public or one transit VIF, and connect it to a Virtual Private Gateway or a Direct Connect Gateway or Transit Gateway, and then to their VPCs.
Last modified on August 21, 2026