On AWS, Multi Cloud Connect Flex terminates the internet + IPsec first mile at your VNF and hands off to AWS over a Direct Connect hosted connection. You supply your AWS Account ID and your own BGP addressing (interface IP, neighbour IP, /30, ASN) in the Virtual Cloud Connection.
Complete the order, retrieve the connection details from inventory, then accept the connection and create the virtual interface in the AWS console. End state: BGP is up end to end.
This continues Placing a Multi Cloud Connect Flex Order at the Virtual Cloud Connection step for AWS. The order-completion and Get Network Config steps are repeated here so you can finish without hopping back. For Azure or Google Cloud, use their pages.
Prerequisite — before you start
Have your AWS Account ID (12-digit) ready — you need to enter it in the Virtual Cloud Connection.
Unlike Azure and Google Cloud, AWS needs no upfront cloud-side artifact: the Direct Connect hosted connection is created from the Tata Communications side, and you have to accept it in the AWS console.
Virtual Cloud Connection — AWS
Double-click the Virtual Cloud Connection icon, enter the fields in portal order, then Save and Validate.
|
Field |
Information |
Mandatory |
What it is / Sample Value |
|
MCC Flavor |
Virtual Cloud Connect supports MCC Flavors: 1. Direct: Direct connection from Tata Communications PoP to the Cloud Service Provider (CSP). 2. Flex: Includes a Virtual Network Function (VNF) between the PoP and CSP for advanced networking (e.g., firewall, SD-WAN). |
Yes |
Flex |
|
CSP |
Select the Cloud Service Provider (CSP) with which you intend to establish Direct Connectivity. |
Yes |
Amazon Web Services |
|
Alias Name |
Alias Name acts as a unique identifier to link components, enabling easy reference throughout the solution. |
Yes |
AWS_Delhi_VC |
|
Location |
Select the desired CSP Direct Connect location based on your deployment requirements. |
Yes |
Delhi |
|
Data Center |
Select the data center corresponding to the CSP Direct Connect location where you want to establish connectivity. |
No |
STT Delhi DC1 -TF, VSB, India |
|
Link Type |
Specifies the connection setup between the VNF and the CSP:
|
Yes |
Single |
|
Select or Add VNF |
Select the A-End VNF for the Virtual Cloud Connect or create a new VNF if one is not already available. |
Yes |
N/A |
|
Bandwidth |
Specify the bandwidth for the Virtual Cloud Connect link between the Fabric Port/VNF and the CSP. |
Yes |
50 Mbps |
|
Redundancy Type |
Choose Primary or Secondary in case of Dual Connectivity. |
No |
Primary |
|
Account ID |
Enter the customer's Cloud Service Provider (CSP) account ID for identification and integration. |
Yes |
your AWS Account ID |
|
AS Number (Local) |
Specify the Autonomous System (AS) number assigned to your local network for BGP configuration. |
Yes |
|
|
AS Number (Global) |
Provide the global AS number if a unified AS is used across multiple regions or locations. |
Yes |
64566 |
|
Peer Type |
Select the desired CSP Peer Type:
|
No |
Private |
|
Enable BFD |
Enable Bidirectional Forwarding Detection (BFD) to quickly detect link failures in the BGP session. |
No |
Yes |
|
BFD Multiplier |
Set the BFD detection multiplier, which defines how many missed messages indicate a failure. |
No |
3 |
|
BFD Transmit Interval |
Specify the time interval (in milliseconds) between sending BFD packets to the peer. |
Yes |
300 |
|
BFD Receive Interval |
Specify the minimum time (in milliseconds) the system expects between receiving BFD packets from the peer. |
Yes |
300 |
|
IP address for Interface |
Provide the IP address to be configured on your interface for BGP peering. |
Yes |
192.168.1.1 |
|
Neighbor IP |
Enter the IP address of the BGP peer (CSP interface) to establish the connection. |
Yes |
192.168.1.2 |
|
Subnet |
Specify the subnet mask for the IP address used in the BGP interface configuration. |
Yes |
30 |
|
BGP Key |
Enter the shared password (authentication key) used for securing the BGP session. |
Yes |
A customer-chosen secret (must match on both ends) |
Note:
Flex addressing: you define the BGP addressing yourself — interface IP, neighbour IP, /30 subnet and your ASN — because your VNF terminates BGP. The BGP Key is a shared secret that must match on both ends; choose your own. AWS Flex has no VLAN field (AWS allocates the VLAN on the hosted connection).
Complete the order
-
Set the Contract Term; the Total Contract Value refreshes automatically. Click Price Breakup for component-wise charges.
-
On Price Breakup, download the draft quote and click Get Ask Price for specific pricing.
-
Enter the expected ARC (Annual Recurring Charges) and NRC (Non-Recurring Charges), then Submit.
-
Click Checkout.
-
Enter the Customer Contracting Entity details, then Generate Order Form.
-
Review the Order Form (Terms and Conditions, Total Charges, Billing and Payments, Contracting Information, Order Summary).
-
Click Order as You Click to submit directly, or DocuSign / Delegate Signature to route the order form for signature.
-
Click Preview eCOF to view or download the draft Customer Order Form.
Get Network Config
-
Open Inventory → IZO™+ Multi Cloud Connect to view Fabric Port, Fabric Edge, Connections and the full Solution Inventory.
-
Open Connection Inventory and copy the Connection ID of the required Virtual Cloud Connection — you use it to find the hosted connection in the AWS console.
AWS side — accept the connection, create the VIF and bring up BGP
These steps are completed in your AWS Management Console. Have the Connection ID and the Cloud IP / Peer IP from Get Network Config to hand.
1. Accept the Hosted Connection
In the AWS console, go to AWS Direct Connect → Connections, search for your Connection ID, then Accept and Confirm the connection. Its state moves to Available.
2. Create the Virtual Interface
Create a Virtual Interface on the connection and choose the type that matches the Peer Type you set on the Virtual Cloud Connection — Private (VPC), Public (AWS public services) or Transit (Transit Gateway).
3. Set the gateway, VLAN and BGP ASN
Attach the Direct Connect gateway, set the VLAN, and enter the BGP ASN as 4755 — the Tata Communications ASN shown in your inventory (My Inventory connection).
|
Field |
Information |
What it is / Demo Value |
Mandatory |
|
Direct Connect gateway |
The Direct Connect gateway the new Virtual Interface will be attached to. |
your DX gateway |
Yes |
|
Virtual Local Area Network (VLAN) |
The VLAN number for the new Virtual Interface (valid range 1–4094). |
e.g. 100 |
Yes |
|
BGP ASN |
The BGP ASN of the router on the Tata Communications side, as shown in inventory. |
4755 |
Yes |
4. Enter the peer IPs and BGP key
Under Additional settings, enter the addresses from the My Inventory (Get Network Config) section:
-
Amazon router peer IP — the Primary Cloud IP address.
-
Your router peer IP — the Primary Peer IP address.
-
BGP authentication key — the same MD5 key you set on the Virtual Cloud Connection, so both ends match.
|
Field |
Information |
What it is / Demo Value |
Mandatory |
|
Address family |
Whether the Virtual Interface is created with IPv4 or IPv6 peering. |
IPv4 |
Yes |
|
Your router peer ip |
The BGP peer IP configured on your endpoint — the Primary Peer IP from Get Network Config. |
e.g. 192.170.1.1/30 |
Yes |
|
Amazon router peer IP |
The BGP peer IP configured on the AWS endpoint — the Primary Cloud IP from Get Network Config. |
e.g. 192.170.1.2/30 |
Yes |
|
BGP authentication key |
The password used to authenticate the BGP session — the same key set on the Virtual Cloud Connection. |
your BGP key |
Yes |
|
Jumbo MTU (MTU size 9001) |
Optionally allow an MTU of 9001 on the Virtual Interface. |
Enabled / off |
No |
5. Confirm BGP is up
Once the Virtual Interface is created and the session establishes, BGP is up — the end-to-end connection is complete.
Related pages
- Placing a Multi Cloud Connect Flex Order
- Placing a Multi Cloud Connect Direct Order
- AWS — Troubleshooting
- AWS — FAQs