Integrating Megaport with SAP on AWS

You can use Megaport to create an AWS Direct Connect Layer 2 connection between your on-premises or colocation-based infrastructure and your SAP environment on AWS. You can also use Direct Connect to connect to a cloud-only instance of SAP on AWS.

Before you begin, ensure that you have created a Megaport connection, or Port. After you create the Port, you can connect a Virtual Cross Connect (VXC) from the Port to the virtual gateway associated with the AWS VPC infrastructure. A VXC is a point-to-point Ethernet connection between an A-End (your Port) and a B-End (in this case, your SAP on AWS instance).

If you aren’t a Megaport customer, you can create a 1 Gbps, 10 Gbps, or 100 Gbps Port in one of our global data centers/Points of Presence. If your company isn’t located in one of our PoPs, you can procure a last mile circuit to one of the sites to connect to Megaport. Contact Megaport for more information.


If you require a Port in a different location to physically separate this solution from other existing traffic traversing your Ports, we recommend that you create a new one before proceeding.

To integrate Megaport with SAP on AWS

  1. In the Megaport Portal, go to the Services page and select the Port you want to use.

    If you haven’t already created a Port, see Creating a Port.

  2. Add an AWS connection for the Port.

    If this is the first connection for the Port, click the AWS tile. The tile is a shortcut to the configuration page. Alternatively, click +Connection, click Cloud, and click AWS.

  3. For AWS Connection Type, click Hosted VIF or Hosted Connection and click Next.

    For this example, you will click Hosted VIF.
    Hosted VIF
    Next, you’ll create a new VXC.
    Destination Port List

  4. In the Select Destination Port list, select the AWS region and the interconnection point for your connection and click Next. You can use the Country filter to narrow the selection.

  5. Specify the connection details:

    • Connection Name – The name of your VXC to be shown in the Megaport Portal.


      Match this to the VXC name on the next screen for easy mapping.

    • Service Level Reference (optional) – Specify a unique identifying number for the VXC to be used for billing purposes, such as a cost center number or a unique customer ID. 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.


      Partner-managed accounts can apply a Partner Deal to a service. For more information, see Associating a Deal With a Service.

    • Rate Limit – The speed of your connection in Mbps. Accepted values range from 1 Mbps to 5 Gbps in 1 Mbps increments. Note the sum of all hosted virtual VXCs to a service can exceed the Port capacity (1 or 10 Gpbs) but the total aggregate will never burst beyond the Port 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.


      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.

    • Preferred A-End VLAN (optional) – Specify an unused VLAN ID for this connection.
      This must be a unique VLAN ID on this Port 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, or 36 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). See VXC Pricing and Contract Terms and VXC, Megaport Internet, and IX Billing for more information.

    Connection details

  6. Click Next.

  7. Specify the cloud details.

    • Type – This refers to your destination within the AWS cloud infrastructure, either Public or Private resources. For this example, choose Private.

    • AWS Connection Name – This is a text field and will be the name of your virtual interface that appears in the AWS console. For easy mapping, use the same name for this field as you did for the VXC name on the previous screen.

    • AWS Account ID – This is the ID of the account you want to connect. You can find this value in the Account Details section of your AWS console.

    • Customer ASN – Your network’s Autonomous System Number. For Private Direct Connects, this must be a private ASN and the supported private ASN range is 64512 - 65535.

    • BGP Auth Key (optional) – Specify the BGP 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.)

    • Customer IP Address – The IP Address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address.

    • Amazon IP Address – The IP address space in CIDR format assigned in the AWS VPC network for peering. For private connections, this field is optional and if left blank, Megaport automatically assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
      Cloud Details

  8. Click Next.

  9. Click Add VXC.
    AWS Summary
  10. Click Order.
    Configured Services

  11. Click Order Now.

  12. Connect the new VXC to the SAP on AWS instance.

In approximately 2 minutes, log in to your AWS account. The VIF will appear in your Direct Connect under Virtual Interfaces. Accept the VIF and attach it to either a Virtual Gateway (VGW) or a Direct Connect Gateway (DGW), depending on your particular solution’s design.


To achieve redundancy for the connectivity portion of this solution, you can establish additional VXCs to the AWS environment. For additional physical redundancy, you can implement the VXCs on separate Ports.

Background information

Planning for deployment of SAP on AWS

SAP on AWS can be operated as a hybrid model with on-premises (global) and cloud resources working in tandem or entirely as a cloud-based solution.

This image shows a hybrid solution showing the QAS, DEV, and SAP test, training and Sandbox environment in the AWS cloud. As shown here, the VPC can connect to a wide array of AWS resources. The on-premise infrastructure is connected to the AWS cloud via a Direct Connect Layer 2 connection, enabled through Megaport.

SAP AWS Architecture

For more information on how to migrate, implement, configure, and operate SAP solutions on AWS: