Amazon Web Services (AWS) today announced the general availability of AWS Interconnect, a managed private connectivity service designed to dramatically simplify and enhance network connections across multicloud environments and between AWS and on-premises infrastructure. This significant launch introduces two core capabilities: AWS Interconnect – multicloud, enabling direct, private connections between Amazon Virtual Private Clouds (Amazon VPCs) and VPCs on other cloud providers, and AWS Interconnect – last mile, a new feature that streamlines the establishment of high-speed, private connections from enterprise branch offices, data centers, and remote locations to AWS through existing network providers. This strategic move by AWS addresses the escalating complexity faced by large enterprises operating diverse IT landscapes, aiming to transform network management from a labor-intensive, undifferentiated task into a streamlined, policy-driven operation.
The Evolving Landscape of Enterprise Connectivity Challenges
The modern enterprise IT landscape is increasingly characterized by complexity. Driven by strategic imperatives such as leveraging specialized services from different vendors, adhering to stringent data residency regulations, or accommodating disparate teams standardized on varying cloud platforms, a significant number of organizations have adopted multicloud strategies. Industry analysts, such as Gartner and IDC, consistently report that a substantial majority of enterprises—often exceeding 80%—are either actively implementing or planning multicloud architectures. While multicloud offers undeniable benefits in flexibility, innovation, and risk mitigation, it simultaneously introduces formidable networking challenges.
Historically, connecting these disparate cloud environments, or integrating on-premises infrastructure with cloud resources, has been a monumental undertaking. IT and networking teams have traditionally grappled with a convoluted array of tasks: meticulously managing complex Virtual Private Network (VPN) tunnels over the public internet, coordinating with multiple colocation facilities, and configuring intricate third-party network fabrics. These methods often lead to unpredictable performance, inconsistent security postures, and significant operational overhead, consuming valuable resources that could otherwise be dedicated to innovating and developing business-critical applications. The public internet, while ubiquitous, inherently lacks the guarantees of latency, throughput, and security that enterprise workloads demand, making direct, private connectivity a critical requirement. Furthermore, the "last mile" problem—connecting an organization’s physical locations to cloud infrastructure—has long been a bottleneck, often requiring bespoke solutions and extensive hardware deployments.
AWS Interconnect: A Unified Solution for Hybrid and Multicloud Networks
AWS Interconnect emerges as a direct response to these pervasive challenges, offering a fully managed connectivity service that abstracts away much of the underlying infrastructure complexity. By providing the capability to establish private, high-speed network connections with dedicated bandwidth, Interconnect facilitates seamless data exchange across hybrid and multicloud environments. The service’s design philosophy centers on ease of use, allowing organizations to configure resilient, end-to-end connectivity with just a few clicks through the AWS Console. Users can simply select their desired location, partner, or cloud provider, preferred AWS Region, and bandwidth requirements, thereby eliminating the friction of partner discovery and the intricacies of manual network configurations.
The service’s dual capabilities—multicloud connectivity and last-mile connectivity—are built upon a common principle: delivering a fully managed, turnkey experience that significantly reduces the operational burden on IT teams. This approach allows enterprises to shift their focus from infrastructure management to strategic business objectives and application development.
Deep Dive: AWS Interconnect – Multicloud
AWS Interconnect – multicloud offers a private, managed Layer 3 connection, creating a secure and high-performance bridge between AWS environments and other participating cloud providers. Initially, this service supports connectivity with Google Cloud, with plans to extend support to Microsoft Azure later in 2026 and Oracle Cloud Infrastructure (OCI) in 2026. A key differentiator of this service is that traffic flows entirely over the AWS global backbone and the partner cloud’s private network, ensuring that data never traverses the public internet. This fundamental design choice provides several critical advantages for enterprises: predictable latency, consistent throughput, and inherent isolation from the congestion and security vulnerabilities associated with the public internet. Crucially, customers are relieved from the burden of managing any physical infrastructure themselves.
Security is a paramount concern for multicloud deployments, and AWS Interconnect – multicloud addresses this by embedding robust security measures by default. Every connection utilizes IEEE 802.1AE MACsec encryption on the physical links between AWS routers and the partner cloud provider’s routers at the interconnection facilities. This hardware-level encryption provides robust data protection without requiring separate configuration by the customer. It’s important to note that while MACsec secures the inter-cloud link, each cloud provider manages encryption independently on its own backbone. Customers are advised to review the specific encryption documentation for their respective cloud deployments to ensure compliance with their internal security and regulatory requirements.
Resilience is also a cornerstone of the service’s architecture. Each connection is designed to span multiple logical links, distributed across at least two geographically distinct physical facilities. This redundancy ensures that a single device or building failure will not disrupt connectivity, providing enterprises with the high availability necessary for mission-critical workloads.
For comprehensive network visibility and operational efficiency, AWS Interconnect – multicloud seamlessly integrates with Amazon CloudWatch. This integration provides customers with a Network Synthetic Monitor included with each connection, enabling real-time tracking of critical metrics such as round-trip latency and packet loss. Furthermore, bandwidth utilization metrics are readily available to support proactive capacity planning and ensure optimal network performance.
In a move demonstrating commitment to industry collaboration and interoperability, AWS has published the underlying technical specification for Interconnect on GitHub under the Apache 2.0 license. This open-source approach invites any cloud service provider to collaborate with AWS Interconnect – multicloud, fostering a broader ecosystem of interconnected cloud platforms. To become an AWS Interconnect partner, cloud providers must adhere to the technical specification and meet stringent AWS operational requirements, encompassing resiliency standards, support commitments, and robust service level agreements. This open model is expected to accelerate multicloud adoption by standardizing connectivity and reducing proprietary barriers.
Simplified Provisioning: A Walkthrough
The provisioning process for an AWS Interconnect – multicloud connection is designed for speed and simplicity, often taking mere minutes. The user initiates the connection from the familiar AWS Direct Connect console, navigating to the AWS Interconnect section. The process involves selecting the desired cloud provider (e.g., Google Cloud), specifying source and destination regions, defining bandwidth requirements, and providing the relevant project ID for the partner cloud. AWS then generates an activation key, which is subsequently used on the partner cloud’s side to complete the connection setup. A key benefit is the automatic propagation of routes in both directions, allowing workloads to begin exchanging data shortly after activation.
For a practical illustration, consider connecting an Amazon VPC to a Google Cloud VPC. The process typically involves three main steps:
-
Requesting an Interconnect in the AWS Management Console:
- Navigate to "AWS Direct Connect," then "AWS Interconnect," and select "Create."
- Choose the target cloud provider (e.g., Google Cloud).
- Specify the AWS Region (e.g.,
eu-central-1) and the corresponding Google Cloud Region (e.g.,europe-west3). - Provide a description, select the desired bandwidth, choose the Direct Connect gateway for attachment, and enter the Google Cloud project ID.
- After review and confirmation, an activation key is generated, which is crucial for validating the request on the Google Cloud side.
-
Creating Transport and VPC Peering Resources on Google Cloud Platform (GCP):
- Using the activation key obtained from AWS, the user proceeds to the GCP environment. While a web-based console may be available in the future, current implementation might involve using the GCP command-line interface (CLI).
- The
gcloud network-connectivity transports createcommand is executed with the activation key, specifying the region, network, and advertised routes (e.g., the CIDR range of the GCP VPC subnet). - Upon completion, a peering connection is established between the GCP VPC and the newly created transport using the
gcloud compute networks peerings createcommand, ensuring custom routes are imported and exported. - Verification in the GCP console confirms the peering status. Concurrently, the AWS Interconnect console confirms the connection status as "available," and the AWS Direct Connect console displays the attachment to the new interconnect under "Direct Connect gateways."
-
Associating the New Gateway on the AWS Side and Configuring Routing:
- In the AWS Direct Connect console, under "Gateway associations," the user associates a Virtual Private Gateway (VGW) with the Direct Connect Gateway. It’s imperative to use a VGW located in the same AWS Region as the interconnect.
- The final step on the AWS side involves adding a route entry in the relevant Amazon VPC Route tables. This entry directs all traffic destined for the GCP IP address range through the Virtual Gateway, completing the network setup.
Once these steps are completed, a private network route is established, enabling secure and efficient communication between compute instances residing in the respective cloud environments. A simple test, such as running a web server on an AWS EC2 instance and accessing it from a GCP VM via its private IP address, demonstrates the successful establishment of this managed private connection. This end-to-end connectivity is entirely managed by the two participating Cloud Service Providers, significantly reducing the customer’s operational burden.
Reference Architectures for Scalability and Global Reach
As enterprise deployments evolve and grow in complexity, AWS Interconnect integrates seamlessly with existing AWS networking services to provide scalable and globally resilient architectures.
For organizations with multiple VPCs within a single AWS Region, AWS Transit Gateway serves as a centralized routing hub. This allows all VPCs to connect through a single Interconnect attachment, simplifying network topology. Transit Gateway also facilitates traffic segmentation between different environments, enables the application of consistent routing policies, and can integrate with AWS Network Firewall for deep packet inspection at the cloud boundary, enhancing security.
For enterprises operating at a global scale, with workloads distributed across multiple AWS Regions and various Google Cloud environments, AWS Cloud WAN extends this model worldwide. Cloud WAN enables any region in an organization’s network to reach any Interconnect attachment globally, providing centralized policy management and segment-based routing that applies consistently across all operational footprints. This global fabric is critical for multinational corporations requiring low-latency, secure connectivity across continents. The detailed reference architectures for building resilient and scalable multicloud connectivity using AWS Interconnect with Transit Gateway and Cloud WAN are further documented by AWS networking specialists, providing comprehensive guidance for complex deployments.
AWS Interconnect – Last Mile: Bridging the On-Premises Gap
Built on the same architectural principles and design as AWS Interconnect – multicloud, AWS Interconnect – last mile addresses the critical need for simplified, high-speed connectivity between on-premises locations and AWS. This capability allows enterprises to connect their physical data centers, branch offices, and remote sites to AWS through a participating network provider’s last-mile infrastructure, directly manageable from the AWS Management Console.
The onboarding process for AWS Interconnect – last mile mirrors its multicloud counterpart. Users select a network provider, authenticate, and specify their connection endpoints and bandwidth requirements. AWS generates an activation key, which the customer then provides to the network provider to complete the configuration. The service automates the provisioning of four redundant connections across two physical locations, configures Border Gateway Protocol (BGP) routing, and activates MACsec encryption and Jumbo Frames by default. This comprehensive automation delivers a highly resilient private connection to AWS, adhering to best practices without requiring customers to manually configure complex networking components.
AWS Interconnect – last mile supports a wide range of bandwidths, from 1 Gbps up to 100 Gbps, with the flexibility to adjust bandwidth directly from the console without needing to reprovision the entire connection. The service includes a robust 99.99% availability SLA up to the Direct Connect port and bundles CloudWatch Network Synthetic Monitor for continuous connection health monitoring. Like AWS Interconnect – multicloud, the last-mile solution attaches to a Direct Connect Gateway, which can then connect to Virtual Private Gateways, Transit Gateways, or AWS Cloud WAN deployments, ensuring seamless integration into existing AWS network architectures.
Industry Reactions and Market Impact
The introduction of AWS Interconnect has been met with positive reception from industry partners, highlighting its potential to significantly streamline enterprise cloud adoption and hybrid IT strategies. Scott Yow, SVP Product at Lumen Technologies, an initial partner for AWS Interconnect – last mile, remarked, "By combining AWS Interconnect – last mile with Lumen fiber network and Cloud Interconnect, we simplify the last-mile complexity that often slows cloud adoption and enable a faster, and more resilient path to AWS for customers." This statement underscores the collaborative effort to remove common impediments to hybrid cloud integration.
The strategic decision by AWS to partner with other major cloud providers like Google Cloud, Microsoft Azure, and Oracle Cloud for multicloud connectivity represents a significant shift towards greater interoperability in the cloud ecosystem. For enterprises, this means reduced vendor lock-in concerns and the ability to truly leverage best-of-breed services from different providers without incurring prohibitive networking overheads. For the partner cloud providers, it signifies an opportunity to attract customers who prioritize seamless multicloud operations and leverage AWS’s extensive global backbone.
The publication of the AWS Interconnect specification on GitHub under an Apache 2.0 license is a particularly impactful move. It not only promotes transparency and collaboration but also lays the groundwork for a standardized approach to inter-cloud connectivity, potentially fostering an even broader ecosystem of interconnected cloud services in the future. This open-source strategy could accelerate innovation in cloud networking and further commoditize the underlying connectivity infrastructure, allowing enterprises to focus more on application logic.
For enterprise IT teams, AWS Interconnect translates directly into reduced operational expenditure and improved agility. The automation of complex networking tasks frees up skilled personnel to focus on higher-value activities. The enhanced security and predictable performance offered by private connections over the AWS global backbone also contribute to a more robust and reliable IT infrastructure, mitigating risks associated with data transfer over the public internet. This service positions AWS as a central orchestrator of enterprise multicloud and hybrid cloud networks, solidifying its role as a foundational platform for complex digital transformations.
Pricing and Availability
AWS Interconnect – multicloud and AWS Interconnect – last mile are priced based on a flat hourly rate for the requested capacity, billed pro-rata by the hour. Customers select the bandwidth tier that best fits their workload needs.
Pricing for AWS Interconnect – multicloud is dynamic and varies by region pair. For instance, a connection between US East (N. Virginia) and Google Cloud N. Virginia will have a different cost structure than a connection between US East (N. Virginia) and a more geographically distant region. When leveraging AWS Cloud WAN, the global any-to-any routing model means traffic might traverse multiple regions, which can influence the overall cost of a distributed deployment. Customers are strongly encouraged to review the dedicated AWS Interconnect – multicloud pricing page and AWS Interconnect – last mile pricing page for comprehensive rate cards, detailing costs by region pair and capacity tier, before making provisioning decisions.
Currently, AWS Interconnect – multicloud is available in five initial region pairs:
- US East (N. Virginia) to Google Cloud N. Virginia
- US West (N. California) to Google Cloud Los Angeles
- US West (Oregon) to Google Cloud Oregon
- Europe (London) to Google Cloud London
- Europe (Frankfurt) to Google Cloud Frankfurt
Future expansion plans include support for Microsoft Azure later in 2026 and Oracle Cloud Infrastructure (OCI) in 2026, significantly broadening the multicloud ecosystem.
AWS Interconnect – last mile has launched in US East (N. Virginia) with Lumen Technologies as the initial network provider partner. AWS has announced that additional partners, including AT&T and Megaport, are in progress, and further regional expansions are planned to extend the reach of this service globally.
To begin utilizing AWS Interconnect, customers can visit the AWS Direct Connect console and select AWS Interconnect from the navigation menu. This unified portal simplifies the discovery and configuration of these new, powerful connectivity services, marking a significant step forward in simplifying the complexities of modern enterprise networking.
