AWS Direct Connect FAQs

Quick answers to the most common AWS Direct Connect questions on IZO™+ Multi Cloud Connect. For detail, follow the linked pages.

1. Which AWS regions does IZO™+ Multi Cloud Connect support?

Tata Communications has direct AWS Direct Connect interconnects in major AWS regions, with reach to all AWS regions over AWS’s global backbone. Where there is no direct interconnect in a target metro, the partner-routed path is used. Confirm coverage for your region with your account team.

2. What bandwidth options are available?

Both delivery paths offer the AWS Hosted Connection catalogue: 50–500 Mbps (standard) and 1–25 Gbps (high capacity). The per-connection maximum is governed by the underlying interconnect — up to 5 Gbps on a 10 Gbps interconnect, 10 Gbps on a 20 Gbps interconnect, and 25 Gbps only where 100 Gbps Direct Connect ports exist.

3. Can I change bandwidth after provisioning?

Yes, on both paths, but the mechanics differ. On the direct interconnect, AWS supports a hot change with no teardown. On the partner-routed path, the connection is deleted and recreated. See AWS Bandwidth Changes and Upgrades.

4. Is MACsec encryption supported?

No. AWS supports MACsec only on Dedicated Direct Connect; it is not supported on Hosted Connections, which is the delivery model IZO™+ Multi Cloud Connect uses. For Layer 3 encryption, an IPsec overlay to a Transit Gateway, Virtual Private Gateway, or a customer-managed appliance is the supported pattern. See MACsec Encryption on AWS.

5. What MTU is supported?

Jumbo MTU on Private VIFs (up to 9001 bytes) and Transit VIFs (up to 8500 bytes); Public VIFs are 1500 only. The Tata Communications interconnect supports jumbo below 9000, so a 9001 Private VIF is effectively capped just under 9000 end to end. See MTU and Jumbo Frames on AWS.

6. What BGP parameters are used?

Tata Communications uses ASN 4755; AWS provides its ASN based on the connection region. MD5 authentication is mandatory, and BFD runs at 300 ms × 3. See BGP Configuration for AWS.

7. Can a single Hosted Connection reach multiple AWS regions?

Not directly — a single Hosted Connection terminates at one Direct Connect location and serves its associated region. To reach several regions over one connection, use a Transit Gateway with a Transit VIF in your AWS account; Tata Communications delivers the Hosted Connection underneath, and the multi-region routing is configured in AWS.

8. How do I add resiliency between two Direct Connect locations?

Provision two Hosted Connections at two Direct Connect locations and steer traffic with BGP (local preference and AS-PATH prepending). See the path-control guidance on BGP Configuration for AWS.

9. Does AWS Direct Connect support multicast?

No. AWS does not support multicast on Direct Connect Hosted Connections; multicast between on-premises and AWS must be handled with an overlay.

10. Can I use IPv6?

IPv6 support on AWS Hosted Connections is currently under testing and is not yet offered as standard. Confirm the position for your connection with your account team.

11. What happens if my BGP session goes down?

The Hosted Connection stays up — BGP runs over the connection, not under it. When BGP drops, routes are withdrawn and traffic fails over to any redundant path until the session re-establishes.

12. Who do I contact for support?

Raise a ticket on the TC^x Portal against the affected Hosted Connection. For issues clearly on the Tata Communications side (connection state, BGP over the Cloud VC, IP allocation), Tata Communications handles them directly; for ambiguous issues, Tata Communications triages and engages AWS where needed. See AWS Troubleshooting.