Tata Communications-Managed Direct Interconnect to AWS

The Tata Communications-managed direct interconnect is the primary delivery path for IZO™+ Multi Cloud Connect AWS Hosted Connections. Tata Communications owns the physical interconnect to AWS Direct Connect, multiplexes customer circuits onto it as Dot1Q-tagged Cloud VCs, and applies per-customer bandwidth shaping. This path supports hot bandwidth changes.

When this route is used

Every AWS Hosted Connection ordered through IZO™+ Multi Cloud Connect is the same product: an AWS Direct Connect Hosted Connection that you accept in your own AWS account. What differs is how Tata Communications reaches the AWS Direct Connect location, and that follows interconnect availability rather than a selection you make – the route is confirmed to you during ordering.

This page covers connections carried on a Tata Communications direct interconnect, which is used wherever Tata Communications operates one at the location serving your target AWS region. Where it does not, an interconnection partner carries the connection instead. Confirm the position for your region with your account team.

Because Tata Communications owns the interconnect on this route, bandwidth can be changed in place without rebuilding the connection.

Where your AWS region is reachable only through a partner network, the partner-routed path is the right choice.

Physical interconnect layout

The direct interconnect is built on AWS Direct Connect ports terminated in the Tata Communications MPLS PE. Customer Hosted Connections are multiplexed onto it as virtual circuits. The per-Hosted-Connection bandwidth ceiling is governed by the underlying interconnect:

Underlying interconnect	Maximum per Hosted Connection
1 Gbps	Up to 1 Gbps
10 Gbps	Up to 5 Gbps (AWS limit)
20 Gbps	Up to 10 Gbps
100 Gbps	Up to 25 Gbps (where 100 Gbps locations exist)

This per-connection cap is an AWS rule and applies to both delivery paths.

VLAN encapsulation

The direct interconnect uses Dot1Q (single C-tag). The C-tag is assigned by Tata Communications at provisioning; customers do not choose their own VLAN ID.

IP addressing and BGP

For each AWS Hosted Connection (Cloud VC), Tata Communications allocates addressing by service category:

Private peering (VPC): a /30 on the Hosted Connection.
Public peering (S3, DynamoDB, etc.): a /30 non-routable public on the Hosted Connection, plus a /32 non-routable public for the customer CPE.

BGP runs over the Hosted Connection as a single EBGP session per virtual circuit. Tata Communications uses ASN 4755; AWS provides its ASN based on the region of the connection. BFD is enabled on every session at 300 ms × 3, giving sub-second failure detection. The full parameter set and routing guidance is on BGP Configuration for AWS.

Bandwidth shaping

Each customer Cloud VC is associated with a dedicated logical interface on which Tata Communications applies bandwidth shaping, so a customer is held to their contracted rate on the shared cloud-facing port. A single class of service is used towards the cloud, because AWS does not honour QoS markings on Direct Connect.

AWS service categories carried

The direct path delivers two AWS Hosted Connection categories; the category is selected in your AWS account when the connection is configured:

Category	What it carries
Private	Traffic into a VPC, via a Private VIF or a Transit VIF
Public	Traffic to AWS public-service endpoints (S3, DynamoDB, …) via a Public VIF

For Public Hosted Connections, the customer CPE IP allocation (the /30 and the /32) is registered with AWS during provisioning and need to be whitelisted

Bandwidth changes

Bandwidth changes on the direct interconnect are made in place, without teardown – see AWS Bandwidth Changes and Upgrades.

AWS regions and Direct Connect locations

The current list of AWS regions and Direct Connect locations where Tata Communications has a direct interconnect is maintained by Tata Communications – confirm coverage for your target region with your account team.

View the full coverage map here: IZO™+ Multi Cloud Connect - Interactive Network Map

What’s on the cloud side

The cloud connection at the far end is created in your AWS console. This page covers how the direct interconnect is delivered on the Tata Communications side; for the cloud-side connection acceptance, VIF creation, and routing, see AWS Hosted Connection Setup and Configuring Virtual Interfaces (VIFs) for AWS.