<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

AWS Hosted Connection Setup

IZO™+ Multi Cloud Connect delivers AWS as a Direct Connect Hosted Connection that you accept in your own AWS account. The ordering journey is the standard flow, documented in full under Provisioning & Configuration. This page shows how that flow applies to AWS, and the AWS-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex. 

This page sits alongside the ordering journey rather than repeating it. The TCx Portal steps, that place and provision the connection are common to every IZO™+ Multi Cloud Connect order and live under Provisioning & Configuration. Here we focus on how the flow applies to AWS: retrieving the network configuration and completing the hand-off in your AWS account.

[Prerequisites: AWS side] : Before you begin, have ready: an AWS account with permission to accept Direct Connect Hosted Connections and create Virtual Interfaces; your 12-digit AWS account ID (already supplied at ordering); and the VIF types you intend to create - Private (VPC), Public (AWS public services), or Transit (Transit Gateway). The Hosted Connection must already be provisioned through the TCx Portal.

How AWS setup fits together

The end-to-end flow is the standard IZO™+ Multi Cloud Connect order, with the AWS-side hand-off at the end:

  1. Place your IZO™+ Multi Cloud Connect order for AWS in the TCx Portal (Direct or Flex).

  2. Tata Communications provisions the Hosted Connection towards AWS Direct Connect against your AWS account ID.

  3. Retrieve the network configuration (Get Network Config) from the Portal inventory.

  4. Accept the Hosted Connection in your AWS console.

  5. Create the Virtual Interface and bring up BGP.

Steps 1 and 2 are covered end to end, with screenshots, under Provisioning & Configuration. See the IZO™+ Multi Cloud Connect Direct and IZO™+ Multi Cloud Connect Flex order pages for AWS. This page picks up at step 3.

In the TCx Portal: retrieve the network configuration

Once the order is provisioned, open the connection in your Portal inventory and choose Get Network Config. Note the values you will need on the AWS side: the Connection ID (used to find the connection in AWS), the Cloud IP and Peer IP (the /30 transit subnet), the ASN (4755), and the BGP key. Track provisioning status in the same inventory view.

On the AWS side

Because AWS is delivered as a Hosted Connection in your own AWS account, the AWS-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex. In your AWS console you:

  • Accept the Hosted Connection - Search for your Connection ID in AWS Direct Connect, then accept and confirm it. Its state transitions to Available.

  • Create the Virtual Interface - Choose the type that matches your architecture: Private (VPC), Public (AWS public services), or Transit (Transit Gateway).

  • Bring up BGP - Set the VIF BGP ASN to 4755 (the Tata Communications ASN from Get Network Config), enter the peer IPs from the /30, and enter the BGP key. AWS peers with the Tata Communications Cloud VC and uses a region-dependent ASN on its own side, shown in the VIF details. Once BGP establishes, the VIF state transitions to Up.

The click-by-click walkthrough, with the AWS-console screenshots, is under Provisioning & Configuration. For the AWS-specific detail on this side, see Configuring Virtual Interfaces (VIFs) for AWS for the per-VIF parameters and BGP Configuration for AWS for the routing.

Bandwidth changes

Bandwidth behaviour depends on the delivery path: hot (in place) on the direct interconnect, rebuild-required on the partner-routed path. See AWS Bandwidth Changes and Upgrades.

Related pages