AWS Interconnect Last Mile Preview With Equinix Skips Cross-Connect Orders
November 3, 2026
AWS announced a preview of AWS Interconnect - last mile with Equinix on November 4, 2026, promising managed private connections from Equinix's global network of 282 data centers into AWS, backed by a 99.99% availability SLA (service level agreement, the uptime AWS commits to).

AWS announced a preview of AWS Interconnect - last mile with Equinix on November 4, 2026, promising managed private connections from Equinix's global network of 282 data centers into AWS, backed by a 99.99% availability SLA (service level agreement, the uptime AWS commits to). The detail that matters more than the reach is what disappears from the project plan: no cross-connect orders and no router configuration, two steps that typically fall to the customer.
For enterprise network teams, that is the real story. This preview, offered through AWS, is free at 1 Gbps and limited to two Regions. It is a chance to test whether activation-key provisioning actually replaces the physical work, before any pricing is attached.
What's new
AWS Interconnect - last mile (preview, with Equinix) provides managed, private, resilient connections to AWS. Equinix is the launch partner, and the connection runs over its network, Equinix Fabric, with setup tied to the Equinix Fabric One portal. According to AWS, customers do not order cross-connects (physical cables joining two networks inside a data center) or configure routers.
Setup in the AWS console takes four inputs: an AWS Region, a bandwidth speed, a Direct Connect gateway (an AWS component that links private connectivity to your cloud networks), and your Equinix Fabric One project ID. AWS then generates an activation key. The customer enters that key in the Equinix Fabric One portal to finish the connection. A connection can also be started from the Fabric One portal instead.

The two companies pre-provision the capacity. AWS and Equinix set up quad-redundant capacity in advance, meaning four separate links across two locations, and they configure BGP peering (the routing handshake between networks), VLANs and ASNs for the customer. Every connection carries a 99.99% availability SLA. Traffic between AWS and Equinix edge devices is encrypted by default with MACsec (a link-layer encryption standard that protects Ethernet frames between directly connected devices).
Connections can be created through the console, the AWS CLI, or the API. Partners can integrate using an open API package that AWS hosts on GitHub.
- Announced: November 4, 2026, as a preview
- Reach: Equinix's network of 282 data centers
- Redundancy: 4 separate links across 2 locations
- SLA: 99.99% availability on every connection
- Preview speed: 1 Gbps only, at no charge
- Preview Regions: US West (N. California) via the San Jose metro, and US East (N. Virginia) via the Northern Virginia metro
Why it matters
Reaching a cloud from colocation has traditionally meant coordinating physical work: ordering a cross-connect, building or configuring routers, and standing up redundancy by hand. AWS says this service removes that work. Redundancy arrives built in, with the four-link, two-location layout already provisioned, and the 99.99% SLA and default MACsec come with it rather than as separate projects.
The reach is the other half. With 282 Equinix data centers able to connect, a team whose servers already sit in an Equinix facility has a managed path to AWS without negotiating the physical layer facility by facility.
The activation-key design is also worth noticing. Setup spans two companies' portals: AWS generates the key in its console, and the customer finishes in Equinix Fabric One. Because a connection can alternatively begin in Fabric One, teams can start from whichever tool they already use.

The value of the preview is therefore procedural: how long setup takes, and how many hands it passes through.
The preview is deliberately narrow. It offers 1 Gbps at no charge in two Regions: US West (N. California) via the San Jose metro and US East (N. Virginia) via the Northern Virginia metro. Once the service is generally available, the console will let customers select from 1 Gbps to 100 Gbps.
Competitive Landscape
One distinction is worth keeping straight: AWS Interconnect (multicloud), which reached general availability on April 13, 2026, is a separate product from this last-mile preview.

Without a named peer, the most useful benchmark is your own current process: the cross-connect order, router configuration and redundancy build that AWS says this service removes.
What's next
The preview is limited to 1 Gbps connections in two Regions.
Practical steps are modest. Teams with Equinix presence in San Jose or Northern Virginia can try the free 1 Gbps preview and time the activation-key handshake against their current cross-connect lead times. Watch for the 1 Gbps to 100 Gbps range and its pricing at general availability, and for partner integrations built on the open API package on GitHub.
A free link that eliminates a ticket queue is a good way to learn how much of your network project was waiting rather than engineering. The harder question arrives at general availability: whether the price of convenience still beats the cost of the cable.
For a network architect at a company with racks in an Equinix facility, two figures decide this: how long the activation-key flow takes compared with your last cross-connect order, and the cost per Gbps once the free tier ends.
-- Aria Lin, Enterprise Technology Analyst
Sources: AWS · AWS · Equinix Fabric