Easily integrate AWS Direct Connect and Telnyx VXC

In this guide, we’ll walk you through how to integrate an Amazon Web Services (AWS) Virtual Private Cloud environment with the Telnyx network backbone. The Virtual Cross Connect will allow you to bypass the internet and gain direct private access to the Telnyx telephony engine, thereby eliminating hops and reducing the risk or packet loss and jitter.

You’ll also benefit from the additional security of direct interconnection. With that being said, to protect against attacks, we always recommend that you encrypt both signaling and media with TLS & Z/SRTP.

1. Provide Telnyx with VXC Preferences

1. In the Networking section of the Mission Control Portal, click on Create a New VXC to input your preferences, including the 12-digit AWS account number associated with your VPC, AWS region, bandwidth speed and network name.
2. Once you submit your preferences, you won’t be able to change them without creating a new VXC. Telnyx will create one or two Direct Connect connections for you to accept in your AWS console within 1-3 days.

2. Create a Virtual Private Gateway (VGW)

1. A VGW is an intermediary between AWS Direct Connect connections and your AWS VPCs. You’ll need to create one VGW to complete this setup.
2. Open the Amazon VPC console.
3. Choose Virtual Private Gateways, Create Virtual Private Gateway.
4. Name the gateway.
5. Use the default ASN.
6. Choose Create Virtual Private Gateway.
7. Next, associate the new VGW with your destination AWS VPC. Select the virtual private gateway that you created, and then choose Actions, Attach to VPC.
8. Select your VPC from the list and choose Yes, Attach. Once completed, you should see the output in the image above.
9. You won’t be able to move on to step 3 before Telnyx completes the initial setup described in step 1. If there are no pending connections as described in step 3 after one business day, please contact [email protected].

3. Accept Pending Direct Connect Connections

1. Now that the VGW is created, the Direct Connect connections need to be accepted. If you requested a backup link, you’ll see two pending connections in this step. Otherwise, there will only be one.
2. To accept Telnyx’s connections, open the AWS Direct Connect console.
3. In the navigation pane, choose Connections.
4. You should see one or two connections pending acceptance (see image above).
5. Expand each connection, select I understand that Direct Connect port charges apply once I click Accept Connection, and then choose Accept Connection.
6. Once the connections are completed, your output should show each connection as available.

4. Create One Virtual Interface Per Circuit

1. Virtual interfaces are where the Layer 3 addressing and BGP details will be completed. Some of the information required below will be provided by Telnyx via email. Those fields are indicated below. If you were able to complete step 3, but haven't received this info yet, please reach out to Telnyx support.
2. Open the AWS Direct Connect console.
3. In the navigation pane, choose Connections, select the first newly accepted connection, and then choose Actions, Create Virtual Interface.
4. Complete the form pictured above.
5. Required Fields:
   Public or Private: Use "Private."
   Virtual Interface Name: use the connection ID for easy identification.
   Your router peer IP: “Telnyx IP” as provided in Telnyx support email.
   Amazon router peer IP: “Customer IP” as provided in Telnyx support email.
   BGP ASN: provided in Telnyx support email.
   BGP Authentication Key: provided in Telnyx support email.
   
6. If you requested a redundant backup link and accepted two connections in step 3, repeat these steps for that second connection.

5. Enable Route Propagation for VPC Route Tables

1. After the virtual interfaces have been created, BGP sessions will form with Telnyx, and routing will be in place over the connections. The final step is to ensure route propagation is enabled for the VGW.
2. Open the Amazon VPC console.
3. On the Route Propagation tab, choose Edit.
4. Select the Propagate check box next to the virtual private gateway, and then choose Save.
5. At this point, the routing table should show Telnyx prefixes routing to the VGW.
6. Navigate to the Routes tab, the output should be similar to the screenshot below.
7. When Telnyx routes are visible in the routing table, full integration is complete, and IP reachability can be tested.

Congrats! You’ve set up a Virtual Cross Connect between Telnyx and AWS. If you have any questions about Telnyx products or pricing, please get in touch with our team of experts or speak with our support team 24/7 via the chat bubble in your Mission Control Portal account.