Yellow Ethernet network cable on a blue background

Amazon.com, Inc. (NASDAQ: AMZN)’s AWS has made AWS Interconnect – multicloud generally available for Microsoft Corp. (NASDAQ: MSFT)’s Azure, giving organizations a managed way to establish private connections between workloads running in the two clouds. The service is meant to reduce the network-design and provisioning work that can accompany multicloud application deployments.

AWS Interconnect – multicloud lets customers provision private, scalable connections to other cloud providers. AWS said customers can use the AWS Management Console, command-line interface or API to create the connections, rather than assembling and managing a multicloud network through separate infrastructure and processes.

The company’s documentation describes the service as managed private connectivity between AWS and other cloud environments. Customers choose a region, capacity and provider, while AWS and the provider provision the requested capacity on redundant network devices. AWS presents the result as one interconnect object in the customer account, rather than exposing the underlying infrastructure as separate connection components.

The Azure availability adds another supported cloud environment to the service. AWS said customers can now use the same service for workloads on Azure, Google Cloud and Oracle Cloud Infrastructure. For IT teams that distribute applications or data services across providers, that common connection model could make it easier to standardize how teams request and operate cross-cloud network links.

Microsoft launched support for AWS Interconnect in public preview in August, according to AWS. The general-availability release covers Azure connections in AWS’s us-east-1 region in Northern Virginia, ap-southeast-2 in Sydney and eu-central-1 in Frankfurt. AWS did not state when it plans to add other regions.

The change addresses a practical issue in multicloud operations. Organizations often keep workloads in more than one provider because of application requirements, regional needs or technology choices, but linking those environments can leave network teams responsible for coordinating connectivity layers and operating procedures across providers. AWS said its service is designed to provide resilient, scalable private connections without that do-it-yourself approach.

Availability through the console, CLI and API also gives platform and network teams multiple ways to incorporate provisioning into their existing operating model. A team that manages infrastructure through automation can use the API, while an operator can use the console for an individual connection. AWS did not describe pricing, service-level commitments or bandwidth options in its update.

For enterprises, the immediate value is a managed path for connecting AWS and Azure environments without building a separate cross-cloud connectivity design for each deployment. It does not remove the need to plan application architecture, identity controls, routing policies or data handling across clouds. It does, however, give AWS customers a supported service for a piece of multicloud infrastructure that previously required more customer-managed coordination.

The broader test will be whether the limited initial regional footprint meets the needs of organizations with distributed workloads. As more applications span providers, managed private connectivity can reduce an operational constraint that often falls to network and cloud-operations teams: turning a multicloud design into a connection that is repeatable to provision and maintain. The initial rollout remains limited to the three listed AWS regions.

Leave a Reply

Your email address will not be published. Required fields are marked *

Latest News