AWS Interconnect - multicloud Now Supports OCI, So I Checked It Out Using the AWS CLI
This page has been translated by machine translation. View original
Introduction
On July 29, 2026, the connection between AWS Interconnect - multicloud and Oracle Cloud Infrastructure (OCI) became generally available (GA). AWS What's New lists us-east-1 (N. Virginia) as the supported AWS Region.
AWS Interconnect - multicloud itself reached GA on April 14, 2026, and at that time the only destination CSP was Google Cloud. In the April announcement, Google Cloud was named as the first launch partner, and Microsoft Azure and OCI were indicated as planned to be supported within 2026. This GA means that, of those plans, OCI has been realized first.
My colleague Hajime Oguri has written a detailed explanation of the April GA and the steps for connecting with Google Cloud.
This article does not operate the OCI-side portal and covers only what can be checked from the AWS CLI. The CLI results below were all measured in us-east-1, a region supported by OCI.
What I Verified
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
I retrieved the list of Environments that can serve as destinations.
aws interconnect list-environments --region us-east-1
Two Multicloud-type Environments were returned. I am excerpting only the array elements. Each element also contains an Environment ID field, but the values are not shown.
{
"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 values. available means a new Connection can be requested for that Environment. limited means it can be used but the overall capacity is limited, and unavailable means it is currently not available.
The bandwidths are also defined in the same CLI reference. bandwidths.available is the bandwidth currently available, and bandwidths.supported is the bandwidth that the Environment plans to support.
The OCI side, which was added later, had a state of available. Both bandwidths.available and bandwidths.supported had the same eight levels from 500Mbps to 100Gbps. The Google Cloud side, which came first, had a state of limited. bandwidths.available had five levels from 500Mbps to 10Gbps, and bandwidths.supported had eight levels.
location contained the region name on the destination CSP side, not the AWS Region. OCI's us-ashburn-1 and Google Cloud's us-east4 are both regions in Northern Virginia, the same as us-east-1.
Checking the AWS-side Attachment Target (Attach Point)
Specifying the OCI Environment, I checked the Attach Point that serves as the AWS-side attachment target. list-attach-points returns only the valid Attach Points that the caller can access.
The actual Environment ID is not shown and is written as <environment-id>.
aws interconnect list-attach-points --environment-id <environment-id> --region us-east-1
{
"attachPoints": []
}
In the test account used this time, there were no Attach Points to enumerate, and an empty array was returned.
Input Fields Visible Before Creation
I did not create a Connection and only checked the shape of the request. --generate-cli-skeleton input does not send an API request and only outputs the JSON for input.
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 seven fields, the one whose usage 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, and you specify either directConnectGateway or arn, but 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 check the presence and meaning of fields in the latest CLI reference. The JSON above is the output from the version at the time of writing this article.
AWS-side Pricing
I read the AWS-side billing conditions from the pricing page and summarized them in a table. This is a summary based on the description at the time of writing.
| Item | Details |
|---|---|
| Billing unit | Hourly billing based on bandwidth and an automatically determined Tier |
| Data transfer fee | No per-GB data transfer fee for Interconnect |
| Billing start/end | From creation to deletion |
| Rounding | Per hour, rounded up |
| Tier | Five 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 and Region |
| CSP-side fees | CSP-side pricing must be checked separately from the AWS side |
Summary
The destination CSPs for AWS Interconnect - multicloud have grown to two, with OCI joining Google Cloud. Before operating the OCI-side portal, I was able to compare the state of both Environments using only the AWS CLI.
The only AWS Region that supports connections with OCI at present is us-east-1. I look forward to future developments of AWS Interconnect - multicloud, such as the expansion of supported regions including the Tokyo Region and the addition of Microsoft Azure as a destination CSP.
