AWS Interconnect - multicloud now supports OCI, so I tried checking it with the AWS CLI

AWS Interconnect - multicloud now supports OCI, so I tried checking it with the AWS CLI

AWS Interconnect - OCI has been added as a supported CSP destination for multi-cloud connectivity, following Google Cloud which was supported in April 2026. We will organize the two Environment states that can be confirmed with the AWS CLI, the input items required before creating a connection, and the AWS-side billing conditions that can be read from the pricing page.
2026.07.31

This page has been translated by machine translation. View original

Introduction

On July 29, 2026, AWS Interconnect - multicloud connectivity with Oracle Cloud Infrastructure (OCI) became generally available (GA). The AWS What's New announcement lists us-east-1 (N. Virginia) as the supported AWS Region.

https://aws.amazon.com/jp/about-aws/whats-new/2026/07/aws-announces-AWS-interconnect-multicloud-OCI-GA/

AWS Interconnect - multicloud itself went GA on April 14, 2026, with Google Cloud as the only supported CSP at that time. The April announcement named Google Cloud as the first launch partner, with Microsoft Azure and OCI slated for support later in 2026. This GA represents OCI being the first of those two to become available.

The details of the April GA and the steps to connect with Google Cloud have been thoroughly explained by my colleague Hajime Oguri.

https://dev.classmethod.jp/articles/aws-and-google-cloud-aws-interconnect-multicloud-ga/

This article covers only what can be confirmed via the AWS CLI, without operating the OCI portal. All CLI output shown below was obtained from actual measurements in us-east-1, the OCI-supported region.

Validation Details

The execution conditions are as follows.

Item Value
AWS CLI aws-cli/2.36.11
Target AWS Region us-east-1

Checking the Destination Environments

A list of destination Environments was retrieved.

aws interconnect list-environments --region us-east-1

Two Multicloud-type Environments were returned. Only the array elements are excerpted below. Each element also includes an Environment ID field, but the value is not shown here.

{
  "provider": { "cloudServiceProvider": "oci" },
  "location": "us-ashburn-1",
  "state": "available",
  "bandwidths": {
    "available": ["500Mbps", "1Gbps", "2Gbps", "5Gbps", "10Gbps", "20Gbps", "50Gbps", "100Gbps"],
    "supported": ["500Mbps", "1Gbps", "2Gbps", "5Gbps", "10Gbps", "20Gbps", "50Gbps", "100Gbps"]
  },
  "type": "Multicloud",
  "remoteIdentifierType": "account"
}
{
  "provider": { "cloudServiceProvider": "gcp" },
  "location": "us-east4",
  "state": "limited",
  "bandwidths": {
    "available": ["1Gbps", "2Gbps", "5Gbps", "10Gbps", "500Mbps"],
    "supported": ["1Gbps", "2Gbps", "5Gbps", "10Gbps", "20Gbps", "50Gbps", "100Gbps", "500Mbps"]
  },
  "type": "Multicloud",
  "remoteIdentifierType": "account"
}

According to the CLI reference, state has three possible values. available means new Connections can be requested for that Environment. limited means it is usable but overall capacity is constrained, and unavailable means it is currently not usable.

Bandwidth is also defined in the same CLI reference. bandwidths.available refers to currently available bandwidths, and bandwidths.supported refers to bandwidths the Environment plans to support.

The newly added OCI side had a state of available. Both bandwidths.available and bandwidths.supported offered the same 8 tiers ranging from 500Mbps to 100Gbps. The previously available Google Cloud side had a state of limited. bandwidths.available offered 5 tiers from 500Mbps to 10Gbps, while bandwidths.supported offered 8 tiers.

The location field contained the region name of the destination CSP rather than an AWS Region name. Both OCI's us-ashburn-1 and Google Cloud's us-east4 are Northern Virginia regions, the same as us-east-1.

Checking the AWS-Side Attach Points

Attach Points on the AWS side were checked by specifying the OCI-targeted Environment. list-attach-points returns only valid Attach Points accessible to the caller.

The actual Environment ID is not shown and is represented as <environment-id>.

aws interconnect list-attach-points --environment-id <environment-id> --region us-east-1
{
  "attachPoints": []
}

In the test account used this time, no Attach Points eligible for enumeration existed, so an empty array was returned.

Input Fields Verifiable Before Creation

No Connection was created; only the shape of the request was checked. --generate-cli-skeleton input does not send an API request and outputs only the input JSON.

aws interconnect create-connection --generate-cli-skeleton input

With AWS CLI 2.36.11, the following JSON was output.

{
  "description": "",
  "bandwidth": "",
  "attachPoint": {
    "directConnectGateway": "",
    "arn": ""
  },
  "environmentId": "",
  "remoteAccount": { "identifier": "" },
  "tags": { "KeyName": "" },
  "clientToken": ""
}

Of the 7 fields, the one whose specification method cannot be determined from this JSON alone is attachPoint. In the expanded JSON, two keys appear side by side, but the CLI reference defines it as a tagged union, meaning either directConnectGateway or arn is specified, not both.

The description of --generate-cli-skeleton explicitly states that the generated JSON is not stable across AWS CLI versions and that backward compatibility is not guaranteed. Please refer to the latest CLI reference for the presence and meaning of fields. The JSON above is the output from the version at the time this article was written.

AWS-Side Pricing

The billing conditions on the AWS side were read from the pricing page and summarized in a table. This is a summary based on the content at the time this article was written.

Item Details
Billing unit Hourly billing based on bandwidth and automatically determined Tier
Data transfer fee No per-GB data transfer fee for Interconnect
Billing start/end From creation until deletion
Rounding Per hour, rounded up
Tier 5 levels. The highest Tier among the paths used by a connection is assigned to the entire connection
Free tier One 500Mbps connection can be created for free per CSP per region
CSP-side pricing CSP-side pricing must be confirmed separately from the AWS side

Summary

The supported CSPs for AWS Interconnect - multicloud have grown to two, with OCI joining Google Cloud. It was possible to compare the state of both Environments using only the AWS CLI, before operating the OCI portal.

The AWS Region supporting connectivity with OCI is currently limited to us-east-1 only. There is much to look forward to regarding the future evolution of AWS Interconnect - multicloud, including the expansion of supported regions to include the Tokyo Region and the addition of Microsoft Azure as a destination CSP.

Share this article

AWSのお困り事はクラスメソッドへ