This is a cache of https://docs.openshift.com/rosa/rosa_cluster_admin/cloud_infrastructure_access/dedicated-aws-dc.html. It is a snapshot of the page at 2024-11-25T03:10:38.046+0000.
Configuring AWS Direct Connect - Configuring private connections | Cluster administration | Red Hat OpenShift <strong>service</strong> on AWS
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Configuring AWS Direct Connect

edit

This process describes accepting an AWS Direct Connect virtual interface with Red Hat OpenShift service on AWS. For more information about AWS Direct Connect types and configuration, see the AWS Direct Connect components documentation.

edit

AWS Direct Connect methods

A Direct Connect connection 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 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 the Red Hat OpenShift service on AWS AWS Account.

If you have an existing DXGateway connected to one or more existing VGWs, the process involves the Red Hat OpenShift service on AWS 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.

See the following AWS documentation for more details:

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

There are two configuration options available:

Method 1

Create the hosted VIF and then the DXGateway and VGW.
Method 2

Request a connection via an existing Direct Connect Gateway that you own.

Creating the hosted Virtual Interface

Prerequisites

  • Gather Red Hat OpenShift service on AWS AWS Account ID.

edit

Determining the type of Direct Connect connection

View the Direct Connect Virtual Interface details to determine the type of connection.

Procedure

  1. Log in to the Red Hat OpenShift service on AWS AWS Account Dashboard and select the correct region.

  2. Select Direct Connect from the services menu.

  3. There will be one or more Virtual Interfaces waiting to be accepted, select one of them to view the Summary.

  4. View the Virtual Interface type: private or public.

  5. Record the Amazon side ASN value.

If the Direct Connect Virtual Interface type is Private, a Virtual Private Gateway is created. If the Direct Connect Virtual Interface is Public, a Direct Connect Gateway is created.

Creating a Private Direct Connect

A Private Direct Connect is created if the Direct Connect Virtual Interface type is Private.

Procedure

  1. Log in to the Red Hat OpenShift service on AWS AWS Account Dashboard and select the correct region.

  2. From the AWS region, select VPC from the services menu.

  3. Select Virtual Private Gateways from VPN Connections.

  4. Click Create Virtual Private Gateway.

  5. Give the Virtual Private Gateway a suitable name.

  6. Select Custom ASN and enter the Amazon side ASN value gathered previously.

  7. Create the Virtual Private Gateway.

  8. Click the newly created Virtual Private Gateway and choose Attach to VPC from the Actions tab.

  9. Select the Red Hat OpenShift service on AWS Cluster VPC from the list, and attach the Virtual Private Gateway to the VPC.

  10. From the services menu, click Direct Connect. Choose one of the Direct Connect Virtual Interfaces from the list.

  11. Acknowledge the I understand that Direct Connect port charges apply once I click Accept Connection message, then choose Accept Connection.

  12. Choose to Accept the Virtual Private Gateway Connection and select the Virtual Private Gateway that was created in the previous steps.

  13. Select Accept to accept the connection.

  14. Repeat the previous steps if there is more than one Virtual Interface.

Creating a Public Direct Connect

A Public Direct Connect is created if the Direct Connect Virtual Interface type is Public.

Procedure

  1. Log in to the Red Hat OpenShift service on AWS AWS Account Dashboard and select the correct region.

  2. From the Red Hat OpenShift service on AWS AWS Account region, select Direct Connect from the services menu.

  3. Select Direct Connect Gateways and Create Direct Connect Gateway.

  4. Give the Direct Connect Gateway a suitable name.

  5. In the Amazon side ASN, enter the Amazon side ASN value gathered previously.

  6. Create the Direct Connect Gateway.

  7. Select Direct Connect from the services menu.

  8. Select one of the Direct Connect Virtual Interfaces from the list.

  9. Acknowledge the I understand that Direct Connect port charges apply once I click Accept Connection message, then choose Accept Connection.

  10. Choose to Accept the Direct Connect Gateway Connection and select the Direct Connect Gateway that was created in the previous steps.

  11. Click Accept to accept the connection.

  12. Repeat the previous steps if there is more than one Virtual Interface.

Verifying the Virtual Interfaces

After the Direct Connect Virtual Interfaces have been accepted, wait a short period and view the status of the Interfaces.

Procedure

  1. Log in to the Red Hat OpenShift service on AWS AWS Account Dashboard and select the correct region.

  2. From the Red Hat OpenShift service on AWS AWS Account region, select Direct Connect from the services menu.

  3. Select one of the Direct Connect Virtual Interfaces from the list.

  4. Check the Interface State has become Available

  5. Check the Interface BGP Status has become Up.

  6. Repeat this verification for any remaining Direct Connect Interfaces.

After the Direct Connect Virtual Interfaces are available, you can log in to the Red Hat OpenShift service on AWS AWS Account Dashboard and download the Direct Connect configuration file for configuration on your side.

edit

Connecting to an existing Direct Connect Gateway

Prerequisites

  • Confirm the CIDR range of the Red Hat OpenShift service on AWS 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. Log in to the Red Hat OpenShift service on AWS AWS Account Dashboard and select the correct region.

  2. From the Red Hat OpenShift service on AWS AWS Account region, select VPC from the services menu.

  3. From VPN Connections, select Virtual Private Gateways.

  4. Select Create Virtual Private Gateway.

  5. Give the Virtual Private Gateway a suitable name.

  6. Click Custom ASN and enter the Amazon side ASN value gathered previously or use the Amazon Provided ASN.

  7. Create the Virtual Private Gateway.

  8. In the Navigation pane of the Red Hat OpenShift service on AWS AWS Account Dashboard, choose Virtual private gateways and select the virtual private gateway. Choose View details.

  9. Choose Direct Connect gateway associations and click Associate Direct Connect gateway.

  10. Under Association account type, for Account owner, choose Another account.

  11. For Direct Connect gateway owner, enter the ID of the AWS account that owns the Direct Connect gateway.

  12. Under Association settings, for Direct Connect gateway ID, enter the ID of the Direct Connect gateway.

  13. Under Association settings, for Virtual interface owner, enter the ID of the AWS account that owns the virtual interface for the association.

  14. Optional: Add prefixes to Allowed prefixes, separating them using commas.

  15. Choose Associate Direct Connect gateway.

  16. After the Association Proposal has been sent, it will be waiting for your acceptance. The final steps you must perform are available in the AWS Documentation.

edit

Troubleshooting Direct Connect

Further troubleshooting can be found in the Troubleshooting AWS Direct Connect documentation.