AWS Interconnect Multicloud with OCI Reaches GA, Replacing DIY Cross-Cloud Networking

What AWS Interconnect – Multicloud Actually Does

With AWS Interconnect, customers no longer need to configure physical or virtual routers, order cross-connects, or manage BGP peering manually. They select a target cloud provider, a destination region, and required bandwidth. AWS and the provider handle provisioning on both sides.

Every Interconnect is provisioned across redundant network devices spanning at least two physically distinct facilities with independent power and networking. The multicloud offering uses a four-connection model with Equal-Cost Multi-Path load balancing, keeping at least one link active during planned maintenance.

All physical connections between AWS routers and partner devices are encrypted using MACsec — IEEE 802.1AE MAC Security. The devices transmit customer traffic only if the encryption session is active. Customers see a single logical object in their AWS account. The underlying redundant infrastructure is abstracted away.

Provisioning follows a two-step create-and-accept flow. One side initiates and generates an activation key. The other side uses that key to accept, triggering automated provisioning on both ends. The documentation states new interconnects are typically provisioned and configured within minutes. Bandwidth can be adjusted afterward without reprovisioning or engaging support.

How This Arrived at GA

AWS published an open specification that other cloud providers such as Google Cloud and Oracle Cloud Infrastructure are adopting. Google Cloud was already supported when the announcement was made. OCI launched support for AWS Interconnect in public preview in May 2026 and is now GA alongside the July 29 announcement. Microsoft Azure will launch later in 2026, but that date is not confirmed in the announcement.

Oracle described the collaboration publicly in April. According to Oracle's announcement, the two companies planned to establish connectivity between Oracle Interconnect and AWS Interconnect – multicloud, targeting the us-east-1 region at that time. Oracle stated the connection would support both full and split-stack multicloud deployments and that customers could avoid managing multiple network providers and installing physical network infrastructure.

The AWS GA announcement confirms OCI support is live. It does not independently characterize the full scope of Oracle's deployment model.

The service connects to AWS VPCs through Virtual Private Gateways, Transit Gateways, and Cloud WAN. When using Cloud WAN, any Core Network Edge can reach any Interconnect globally that is attached to the same Direct Connect Gateway. Virtual Private Gateways and Transit Gateways can only reach an Interconnect local to their Region. That distinction matters for teams planning cross-region architectures.

All Interconnects include a single CloudWatch Network Synthetic Monitor at no extra cost, providing round-trip latency and packet loss data. The announcement does not state pricing for the connection itself. Teams should check the AWS Interconnect pricing page before building cost models.

Why This Matters for Your Architecture

The previous path for AWS-to-OCI connectivity required teams to build and manage global multi-layered networks at scale — provisioning virtual routers, ordering physical cross-connects, and managing BGP peering. That operational overhead adds lead time.

A fully managed path removes that setup overhead, though teams should verify pricing before assuming cost savings. Built-in resiliency spans redundant devices across physically distinct facilities, reducing single points of failure at the device, cross-connect, and facility level. Physical connections between AWS routers and partner devices are secured using MACsec encryption, designed to ensure data confidentiality and integrity on those links.

The announcement does not describe end-to-end encryption beyond the physical link between AWS and OCI routers.

Teams running Oracle AI Database workloads on AWS — a scenario Oracle has highlighted through Oracle AI Database@AWS — are likely candidates for this path if their workloads run in us-east-1. The documentation states the service eliminates the need for complex on-premises routing or intermediate network hops, which AWS describes as a simplified network architecture advantage.

Teams with high call frequency or large data movement volumes should evaluate whether that architectural change fits their workload profile.

The current GA scope is limited to us-east-1. Teams with workloads in other AWS Regions cannot use the OCI connection today. The announcement does not state when additional regions will become available.

What to Do Before You Commit

Cloud platform owners should take three concrete steps now.

Inventory your existing OCI-to-AWS connectivity. If your team built a DIY path — virtual routers, physical cross-connects, or transit through on-premises equipment — assess whether that path carries production workloads and what SLA it currently delivers. That baseline determines whether a migration is worth the effort.

Confirm your workload regions. The OCI connection is available only in us-east-1 today. If your primary AWS workloads run in us-east-2, eu-west-1, or anywhere else, GA availability does not translate to immediate usability. Watch for additional region announcements before adjusting your roadmap.

Review your security and governance controls for cross-cloud traffic. MACsec encrypts physical links between AWS and OCI routers. Security leaders should confirm whether current policies cover private cloud-to-cloud paths and whether new monitoring, access controls, or logging requirements apply. The announcement does not describe cross-cloud IAM integration or data residency enforcement. Confirm those details in the AWS Interconnect documentation before production deployment.

Microsoft Azure support is planned for later in 2026. Teams running three-cloud architectures should treat Azure connectivity as conditional until AWS confirms a GA date.