Skip to content

Latest commit

 

History

History
42 lines (29 loc) · 2.53 KB

aws-direct-connect.adoc

File metadata and controls

42 lines (29 loc) · 2.53 KB

Configuring AWS Direct Connect

{AWS} Direct Connect requires a hosted Virtual Interface (VIF) connected to a Direct Connect Gateway (DXGateway), which is in turn associated to a Virtual Gateway (VGW) or a Transit Gateway in order to access a remote Virtual Private Cloud (VPC) in the same or another account.

If you do not have an existing DXGateway, the typical process involves creating the hosted VIF, with the DXGateway and VGW being created in your AWS account.

If you have an existing DXGateway connected to one or more existing VGWs, the process involves your AWS account sending an Association Proposal to the DXGateway owner. The DXGateway owner must ensure that the proposed CIDR will not conflict with any other VGWs they have associated.

Prerequisites

  • Confirm the CIDR range of the {product-title} VPC will not conflict with any other VGWs you have associated.

  • Gather the following information:

    • The Direct Connect Gateway ID.

    • The AWS Account ID associated with the virtual interface.

    • The BGP ASN assigned for the DXGateway. Optional: the Amazon default ASN may also be used.

Procedure

  1. Create a VIF or view your existing VIFs to determine the type of direct connection you need to create.

  2. Create your gateway.

    1. If the Direct Connect VIF type is Private, create a virtual private gateway.

    2. If the Direct Connect VIF is Public, create a Direct Connect gateway.

  3. If you have an existing gateway you want to use, create an association proposal and send the proposal to the DXGateway owner for approval.

    Warning

    When connecting to an existing DXGateway, you are responsible for the costs.
Additional resources