Bandwidth
Per-pair speeds, changed without downtime
Choose from the list each partner/Region pair supports, and scale up or down by changing an attribute instead of recreating the connection.
AWS Interconnect · Managed private connectivity family
One name, two services
AWS Interconnect is the umbrella name for two independent services. multicloud connects AWS VPCs to VPCs in other public clouds, and last mile connects branches and data centers to AWS over a carrier's existing network. Each service has its own partners, supported Regions, pricing and quotas.
What they share is the operating model. You pick a Region, bandwidth and partner; AWS builds the connection on capacity it has pre-provisioned with that partner and presents it as a single interconnect object attached to a DX gateway.
AWS Interconnect2 offerings
Service 01
Interconnect – multicloud
AWS VPC ↔ other-cloud VPC
AWSCSP
- Partner
- Cloud service provider (CSP)
- attach
- DX gateway ↔ CSP router
- Bandwidth
- Per partner/Region pair (e.g. 10 Gbps)
Google Cloud GAOCI GAAzure Preview
Service 02
Interconnect – last mile
Branch / data center ↔ AWS
SiteAWS
- Partner
- Carrier (delivery partner)
- attach
- DX gateway ↔ partner network ID
- Bandwidth
- 1–100 Gbps, 7 steps
Lumen GAAT&T Gated preview
Both services use four connections (ECMP) across at least two facilities and encrypt the AWS-to-partner device segment with MACsec.
2
Independent services: multicloud · last mile
4
Connections across 2+ facilities (both, ECMP)
1–100
last mile bandwidth steps (Gbps)
500 Mbps
multicloud Free Tier (one per Region per CSP)
Two offerings
multicloud and last mile are separate services
The service depends on whether your partner is a cloud provider or a carrier. Console menus, supported Regions, pricing pages and per-partner quotas are all separate, so use only the one you need.
| Item | multicloud | last mile |
|---|---|---|
| Connects | AWS VPC ↔ VPC in another public cloud | Branches, data centers, remote sites ↔ AWS (over the partner's existing network) |
| Partners | Google Cloud GA · OCI GA · Azure Preview | Lumen GA · AT&T Gated preview |
| Location choice | AWS local Region + paired CSP Region (8 Regions for Google Cloud, 1 for OCI, 4 for Azure) | Choosing an Interconnect metro determines the Region (NY/NJ → us-east-1) |
| Create · accept | DX console › AWS Interconnect › multicloud. Enter the partner ID (Google Cloud project ID, OCI tenancy OCID) → accept with the activation key in the CSP console | DX console › Last mile Interconnect. Enter the partner account ID (email for Lumen) → accept with the activation key in the partner portal |
| Partner-side attach point | CSP router | Partner-side network identifier, with customer CPE beyond it |
| Bandwidth | Supported list per partner/Region pair (e.g. Google Cloud 10 Gbps). 1 Gbps for preview partners | 1 · 2 · 5 · 10 · 25 · 50 · 100 Gbps |
| Extras | 500 Mbps Free Tier for GA partners (one per Region per CSP) | 99.99% availability SLA (to the DX port), MTU 8500, IPv4 · IPv6 |
| Pricing tier basis | Distance from the VPC traffic source Region ↔ Interconnect local Region | Interconnect metro ↔ farthest Region attached to the DX gateway |
| Quota | 2 per partner CSP (per account) | 2 per partner (per account) |
| Typical uses | Cross-cloud data pipelines, distributed analytics and AI workloads, cross-cloud DR | Onboarding branches and data centers, replacing hosted connections or self-procured circuits |
In common · Both are managed in the Direct Connect console, CLI, API and CloudFormation (AWS::Interconnect::Connection, with the CSP or last mile provider set in Provider). The AWS-side attach point is a DX gateway; four connections, ECMP and MACsec are the default; and you pay an hourly rate with no per-GB transfer charge. The two services share a quota of 10 Interconnects per account (4 in requested state).
Service 01 · multicloud
Interconnect – multicloud: connect directly to other clouds
Create private connections with dedicated bandwidth on a capacity pool that AWS and the partner CSP have pre-provisioned. Traffic rides the AWS global backbone and is handed straight to the partner CSP, with no on-premises equipment or virtual routers in the path.
| Partner CSP | Status | AWS Region – partner Region | Notes |
|---|---|---|---|
| Google Cloud | GA | us-east-1, us-west-1, us-west-2, eu-west-2, eu-central-1, eu-north-1, ap-southeast-1, ap-southeast-2 (e.g. us-east-1 – us-east4) | Launch partner, GA April 2026. Enter the project ID at creation |
| Oracle Cloud Infrastructure | GA | us-east-1 – us-ashburn-1 | GA July 2026. Enter the tenancy OCID at creation |
| Microsoft Azure | Preview | us-east-1, us-west-1, eu-central-1, ap-southeast-2 | Public preview since August 2026. One per Region, 1 Gbps, free; preview connections are removed at GA |
Resiliency
4-way redundancy + MACsec
ECMP across four connections in at least two facilities. The physical segment between AWS and CSP routers is encrypted with MACsec.
Limits
2 per CSP
Up to two per partner CSP per account. Preview partners allow one per Region, and activation during preview may require the CLI.
multicloud · architecture
Local Region through TGW or VGW, other Regions through Cloud WAN
This example connects us-east-1, as the local Region, to Google Cloud (us-east4). A VGW or TGW reaches only an Interconnect in the same Region, while a Cloud WAN CNE reaches any Interconnect on the same DX gateway, from any Region.
On narrow screens, swipe the diagram sideways.
When to use
Cross-cloud data movement
Connect AWS workloads to data and analytics services in another cloud without the internet or your own colocation.
When to use
Multi-Region hub integration
With Cloud WAN, workloads in other Regions use the same Interconnect. The pricing tier rises to match the farthest CNE.
When to use
Validate for free first
GA partners include a Tier 1 500 Mbps Free Tier, so you can verify paths and routing first (it cannot be converted to paid).
Service 02 · last mile
Interconnect – last mile: reach AWS through the carrier you already use
Come into AWS directly from the Ethernet or MPLS network of a carrier you already have a contract with. The service automates partner discovery, cross-connects and VLAN, ASN and BGP configuration, and enforces the AWS recommended configuration. On your side, all you need is CPE connected to the partner's network.
| Partner | Status | Interconnect metro → AWS Region | Notes |
|---|---|---|---|
| Lumen | GA | New York/New Jersey → us-east-1 | GA April 2026. Connect from anywhere in the contiguous US over the Lumen network. The partner account ID is an email address |
| AT&T | Gated preview | United States | Gated preview since June 30, 2026 |
Bandwidth
1–100 Gbps, 7 steps
Choose 1 · 2 · 5 · 10 · 25 · 50 · 100 Gbps and scale up or down in the console or CLI without recreating the connection.
Resiliency
99.99% SLA (to the DX port)
Four connections on four router pairs at two separate sites, load-shared with ECMP. At least one link stays up during planned maintenance.
Network
MTU 8500 · IPv4/IPv6
Jumbo frames by default and BGP configured automatically. 256-bit MACsec is applied to every connection by default.
last mile · architecture
Enter AWS at the metro, fan out through the DX gateway
In this example, traffic leaves the site's CPE, crosses the Lumen network (first mile) and enters AWS at the NY/NJ metro. Workloads need not be in us-east-1; with Cloud WAN they can be in other Regions too.
On narrow screens, swipe the diagram sideways.
vs hosted connection
Procurement, setup and redundancy automated
With a hosted connection, finding a partner, procuring the circuit and configuring VIFs and BGP are up to you; it isn't redundant by default and isn't covered by the DX SLA. last mile automates all of this and enforces redundancy.
When to use
Onboard branches and data centers
Request directly in the console with the carrier account you already have. You can also attach to a DX gateway that already has private or transit VIFs.
Operations
Two support channels
AWS Support covers the AWS side, and the partner supports its network. You can create up to two per partner (per account).
Comparison
How it differs from Direct Connect and VPN
Both Interconnect services are managed layers that run on Direct Connect infrastructure and the DX gateway. Instead of handling ports, VIFs and BGP yourself, you consume capacity pre-arranged with the partner as an object.
| Item | multicloud | last mile | Direct Connect | S2S VPN (internet) |
|---|---|---|---|---|
| Connects | VPCs in another CSP | Branches and data centers on the partner network | Customer or partner circuits brought to a DX location | Customer gateway reachable over the internet |
| Setup work | Create + accept the key in the CSP console | Create + accept the key in the partner portal | Port request, LOA-CFA, cross-connect, VIF creation | Create the VPN connection, configure IPsec on customer device |
| Routing | BGP, VLAN, ASN automatic | BGP, VLAN, ASN automatic | Configure eBGP yourself per VIF | Configure static routes or BGP yourself |
| Redundancy | Default: 2+ facilities, 4 connections, ECMP | Default: 2 sites, 4 connections, ECMP, 99.99% SLA | You design it (Resiliency Toolkit) | 2 tunnels per connection; device redundancy is up to you |
| Encryption | MACsec on AWS–CSP segment by default | MACsec on AWS–partner segment by default | Optional MACsec on supported dedicated connections | IPsec end to end |
| Bandwidth | List per pair, changed without downtime | 1–100 Gbps in 7 steps, changed without downtime | Dedicated 1–400 Gbps, hosted 50 Mbps–25 Gbps | Per-tunnel limit, depends on internet quality |
| Pricing model | Hourly rate by bandwidth × tier, no per-GB charge | Hourly rate by bandwidth × tier, no per-GB charge | Port hours + per-GB DTO | Connection hours + internet DTO |
MACsec protects the L2 segment between AWS devices and the partner's devices. If you need end-to-end confidentiality from the VPC to the partner subnet, add IPsec or application-layer encryption.
Getting started
Creation steps for each service
Both start in the Direct Connect console, under different menus. Whichever side creates the connection first, provisioning completes automatically once the other side accepts with the activation key.
multicloud
DX console › AWS Interconnect
- Design · Choose between VGW/TGW (local Region) and Cloud WAN (global), and check for IP range overlaps.
- Create new multicloud Interconnect · Choose the partner CSP card (previews are marked Preview).
- Location · speed · Enter the AWS local Region, partner Region, bandwidth, DX gateway and partner ID.
- Accept · Enter the issued activation key on the CSP side. If the CSP created it first, enter the key in Accept multicloud Interconnect.
- Start for free · “AWS Interconnect - multicloud - Free Tier” in the DX console preselects 500 Mbps. Check the partner CSP's quota first.
last mile
DX console › Last mile Interconnect
- Prepare · Partner sign-up, site CPE connected to the partner network, and a DX gateway (you can also create it during setup).
- Create new last mile Interconnect · Choose the partner (e.g. Lumen) and the nearest Interconnect metro; the connected Region is shown.
- Speed · ID · Enter the bandwidth (1–100 Gbps), DX gateway and partner account ID.
- Accept · Enter the activation key in the partner portal. If the partner created it first, enter the key in Accept last mile Interconnect.
- Automatic setup · Four connections, BGP, VLAN, ASN and MACsec are configured and attached to the DX gateway.
Both: each Interconnect gets one CloudWatch Network Synthetic Monitor at no extra cost to measure latency and packet loss, and you can alarm on the bandwidth utilization (%) metric.
Pricing
What you pay for
Each service has its own price list. The structure is the same: a single hourly rate set by bandwidth and an automatically assigned tier (1–5), with no per-GB transfer charge. Billing runs from creation to deletion in one-hour increments (rounded up).
| Item | multicloud | last mile |
|---|---|---|
| Tier assignment | VPC traffic source Region ↔ Interconnect local Region. The highest tier among the paths in use applies | Interconnect metro ↔ farthest AWS Region attached to the DX gateway |
| Cloud WAN caveat | If CNEs are in multiple Regions, the highest-tier CNE sets the tier. Example: an ap-southeast-1 CNE attached to a us-east-1 (or NY metro) Interconnect makes it Tier 4, not Tier 1 | |
| Free Tier | One Tier 1 500 Mbps connection (per Region, per GA CSP). Cannot be converted to paid | None |
| Preview | Azure preview: free, one per Region, 1 Gbps | AT&T gated preview: not listed separately on the pricing page |
| Partner-side charges | Billed separately by the partner CSP | Circuit charges billed separately by the carrier |
| Pricing page | Interconnect - multicloud pricing | Interconnect - last mile pricing |
Transit Gateway and Cloud WAN attachment and data processing charges are billed separately by each service. If a remote-Region TGW comes in by peering with the local-Region TGW, inter-Region transfer charges also apply.
Next step
Partner is a cloud? multicloud. A carrier? last mile.
With multicloud, validate the path first on the 500 Mbps Free Tier; with last mile, request a connection right away with your existing carrier account. For dedicated on-premises circuits see Direct Connect, for hub design see Transit Gateway and Cloud WAN, and for quick temporary connectivity see Site-to-Site VPN.