Interconnection Partner-Routed Hosted Connection

The Interconnection partner-routed path delivers an AWS Hosted Connection through a partner network where Tata Communications does not have a direct interconnect at the target metro. It supports the full AWS bandwidth catalogue (50 Mbps – 25 Gbps) and jumbo MTU (< 9000). Bandwidth changes on this path require a rebuild rather than a hot change.

IZO™+ Multi Cloud Connect offers a partner-routed path for AWS Hosted Connections in addition to the Tata Communications-managed direct interconnect. Both present an identical Hosted Connection to AWS, the difference is how Tata Communications reaches the AWS Direct Connect location.

How the two paths compare

Capability	Tata Communications-managed direct	Interconnection Partner-routed
Bandwidth range	50 Mbps – 25 Gbps	50 Mbps – 25 Gbps
In-place bandwidth changes	Yes (hot)	No – delete + recreate
MTU	Jumbo (< 9000)	Jumbo (< 9000)
VLAN encapsulation	Dot1Q	QinQ (S-tag + C-tag)
MACsec	Not supported	Not supported

When this route is used

The target AWS metro is better served through a partner network than by a Tata Communications direct interconnect.
A direct interconnect is not available in your target region (confirm with your account team).

Tata Communications-side delivery parameters

On the partner-routed path, Tata Communications allocates the outer S-tag and inner C-tag at provisioning. Bandwidth slabs follow the AWS Hosted Connection catalogue.

Parameter	Value
S-tag (outer)	Reserved range 1300–1399, unique per customer circuit
C-tag (inner)	Range 2–4094
Encapsulation	QinQ (TPID 0x8100)
Bandwidth slabs	50–500 Mbps (standard); 1–25 Gbps (high capacity)
Jumbo MTU	Less than 9000

The 25 Gbps slab is available only where 100 Gbps AWS Direct Connect ports exist; the per-Hosted-Connection ceiling otherwise follows the AWS interconnect rule (5 Gbps on a 10 Gbps interconnect, 10 Gbps on a 20 Gbps interconnect).

Provisioning flow

The TC^x Portal ordering flow is the same as the direct path; you select the partner-routed option during ordering. After Tata Communications provisions the Hosted Connection through the partner network, you accept it and create VIFs in your AWS account exactly as on the direct path – see Provisioning an IZO™+ Multi Cloud Connect order.

Bandwidth changes on the partner-routed path

This path does not support hot bandwidth changes; a change requires deleting the current Hosted Connection and creating a new one at the target bandwidth. The full procedure and the continuous-availability pattern are on AWS Bandwidth Changes and Upgrades.

What’s on the cloud side

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