Explore

Build

Join the Megaport Community
Join the Megaport Community
The community for network engineers, IT leaders, and partners to swap ideas and build what’s next.
Join Community

Get in touch

Corporate Info

Partners

It's official: Megaport x Latitude.sh
It's official: Megaport x Latitude.sh
Latitude.sh dedicated compute meets Megaport private connectivity so you can launch fast and run anywhere.
Press Start
AWS Interconnect Is Coming to Megaport

AWS Interconnect Is Coming to Megaport

By Chris Cabel, Senior Director, Global Cloud Solutions

AWS Interconnect is coming to Megaport, giving enterprises and AI infrastructure providers another way to scale private AWS connectivity with automation, encryption, and built-in resilience.

Megaport customers just got a new AWS connectivity option, and it fits perfectly with how we’ve always believed infrastructure should work: direct, automated, resilient, and easier to operate.

We’re excited to share that Megaport has been chosen to support AWS Interconnect - last mile, AWS’s managed connectivity service that simplifies connectivity into AWS. This launch keeps every AWS connectivity option available via Megaport, and reflects how cloud connectivity itself is changing.

Read the press release

According to Robert Kennedy, VP, Networking Services at AWS, AWS Interconnect - last mile makes AWS’s high-capacity cloud connectivity even simpler to deploy and operate, and partners like Megaport give customers more choice in how they connect — with automation, encryption, and resilience built into the service.

AWS has been moving more of the network experience into the same operating model customers already expect from cloud, where they can easily choose what they need, provision it through software, and remove as much manual coordination as possible. AWS Interconnect - last mile brings that approach to private connectivity, and we’re proud to be part of how it reaches customers.

A different way to scale into AWS

For many customers, AWS Hosted Connection is a perfect fit. It’s automated, straightforward, and supports a wide range of cloud connectivity requirements. But network requirements don’t stand still.

AI infrastructure, large data sets, cloud migrations, replication, and other bandwidth-heavy workloads can push customers beyond the limits of a hosted connection. Traditionally, the next step has been a dedicated AWS Direct Connect connection, which gives customers more capacity but can introduce more infrastructure and configuration than some teams want to manage.

AWS Interconnect creates another path. At general availability, MACsec encryption and four redundant links across two sites will be included as part of the service, with customers able to select connection speeds from 1 Gbps to 100 Gbps.

AWS Interconnect is a managed service where AWS and the customer’s selected connectivity provider configure the underlying connectivity and present it to the customer as a single interconnect.

Customers can start an order in either the Megaport Portal or the AWS Management Console and complete it in the other. Behind the scenes, AWS and Megaport automate network configuration that would otherwise involve tasks like setting up VLANs, IP subnets, MTU, and BGP.

Bringing AWS Interconnect to Megaport makes deploying this service as consolidated as everything else in our compute, network, and storage offering.

Where Megaport fits

AWS Interconnect can be deployed only through qualified connectivity providers, including Megaport, when the AWS connection becomes part of the same infrastructure platform you already use across cloud, data center, internet, routing, and other services.

This means instead of AWS connectivity running as an isolated circuit, it can sit inside a broader software-defined infrastructure environment. Existing Megaport customers can attach AWS Interconnect through services they already run with us, including a Port, Megaport Cloud Router, Megaport Virtual Edge, or NAT Gateway.

More ways to connect to AWS

This launch gives customers a more complete path for how their AWS connectivity can evolve. As their needs change, they can move between hosted, dedicated, and managed models without having to step outside of Megaport.

Customers can also continue using AWS Hosted Connection where that model fits, use dedicated AWS Direct Connect when they want to operate that infrastructure themselves, or use AWS Interconnect when they want higher-capacity managed connectivity with more of the underlying setup handled for them.

That means the architecture can follow the workload instead of forcing every AWS connection into the same model.

AWS Interconnect Preview from Megaport will initially be available in Ashburn and San Jose at the end of 2026.

We’ve worked closely with AWS for years on making cloud networking easier to consume. Bringing AWS Interconnect onto the Megaport platform is another step in that direction, and a significant one.

Go to the Docs page

Related Posts

API Highlight: Introduction

API Highlight: Introduction

One of the key features of the Megaport service is our flexible network model. The core of the system is the Megaport API and over the coming months we’ll be doing a series of posts around the API with some usage information and examples.

Read More
When to Use ExpressRoute Local for Microsoft Azure Private Peering

When to Use ExpressRoute Local for Microsoft Azure Private Peering

A checklist for knowing how to make ExpressRoute Local on Microsoft Azure right for you.

Read More
What to Expect When Attending Your First Network Operator Group (NOG)

What to Expect When Attending Your First Network Operator Group (NOG)

Your first NOG meeting doesn’t have to be daunting. Here’s what to expect, how to prepare, and how to make the most of every session and conversation.

Read More