AWS Interconnect - last mile Now Supports Preview with Equinix, So I Tried It Out with the AWS CLI
This page has been translated by machine translation. View original
Introduction
On November 4, 2026, the preview of AWS Interconnect - last mile with Equinix became available.
AWS Interconnect has two types: multicloud, which connects AWS with other clouds, and last mile, which connects your own infrastructure to AWS via a partner. This Equinix support is for last mile, and lets you connect to AWS from your own infrastructure in an Equinix data center. This article covers only last mile, and checks the AWS CLI output as of November 15, 2026, along with the AWS-side billing conditions.
For multicloud, the connection with Google Cloud became GA in April 2026, Oracle Cloud Infrastructure (OCI) became GA in July, and Microsoft Azure was added in preview in August.
Preview conditions
The announcement details are as follows.
- Connection source: Infrastructure in any of Equinix's 282 data centers. No need to arrange cross-connects or configure routers
- Bandwidth and pricing during the preview: 1 Gbps, free
- Supported metros
- San Jose metro → US West (N. California) (us-west-1)
- Northern Virginia metro → US East (N. Virginia) (us-east-1)
- At GA: Expected to be expandable from 1 to 100 Gbps
A metro is a location where a partner's facilities connect to AWS, and the AWS Region to connect to is determined for each metro.
In the console, you specify a Direct Connect gateway and the Equinix Fabric One project ID. You complete the setup by entering the activation key issued by AWS into the Fabric One portal.
Checking with the AWS CLI
Using AWS CLI 2.40.3, I checked the Environments in us-west-1 and us-east-1 on November 15, 2026.
Equinix Environments
list-environments returns multicloud Environments together with last mile ones. Here, multicloud is excluded and only the last mile Environments are shown.
aws interconnect list-environments --region us-west-1 --output json
In us-west-1, two last mile Environments were returned, and the Equinix one is the following.
{
"provider": {
"lastMileProvider": "equinix"
},
"location": "Silicon Valley",
"environmentId": "<environment-id>",
"state": "available",
"bandwidths": {
"available": [
"1Gbps"
],
"supported": [
"1Gbps"
]
},
"type": "LastMile",
"activationPageUrl": "https://portal.equinix.com/interconnection/fabric-one",
"remoteIdentifierType": "account"
}
The other last mile Environment in the same Region is the following.
{
"provider": {
"lastMileProvider": "megaport"
},
"location": "SanJose",
"environmentId": "<environment-id>",
"state": "available",
"bandwidths": {
"available": [
"1Gbps"
],
"supported": [
"1Gbps"
]
},
"type": "LastMile",
"activationPageUrl": "https://portal.megaport.com/services/create/aws-interconnect",
"remoteIdentifierType": "account"
}
aws interconnect list-environments --region us-east-1 --output json
In us-east-1, four last mile Environments were returned, and the Equinix one is the following.
{
"provider": {
"lastMileProvider": "equinix"
},
"location": "Northern Virginia",
"environmentId": "<environment-id>",
"state": "available",
"bandwidths": {
"available": [
"1Gbps"
],
"supported": [
"1Gbps"
]
},
"type": "LastMile",
"activationPageUrl": "https://portal.equinix.com/interconnection/fabric-one",
"remoteIdentifierType": "account"
}
The other last mile Environments in the same Region are the following three.
{
"provider": {
"lastMileProvider": "lumen"
},
"location": "Northern Virginia",
"environmentId": "<environment-id>",
"state": "available",
"bandwidths": {
"available": [
"1Gbps",
"2Gbps",
"5Gbps",
"10Gbps",
"20Gbps",
"50Gbps",
"100Gbps"
],
"supported": [
"1Gbps",
"2Gbps",
"5Gbps",
"10Gbps",
"20Gbps",
"50Gbps",
"100Gbps"
]
},
"type": "LastMile",
"activationPageUrl": "https://connect.lumen.com/enterprise/connections/create-cloud-interconnect",
"remoteIdentifierType": "account"
}
{
"provider": {
"lastMileProvider": "megaport"
},
"location": "Northern Virginia",
"environmentId": "<environment-id>",
"state": "available",
"bandwidths": {
"available": [
"1Gbps"
],
"supported": [
"1Gbps"
]
},
"type": "LastMile",
"activationPageUrl": "https://portal.megaport.com/services/create/aws-interconnect",
"remoteIdentifierType": "account"
}
{
"provider": {
"lastMileProvider": "lumen"
},
"location": "New York Metro (NY Metro)",
"environmentId": "<environment-id>",
"state": "available",
"bandwidths": {
"available": [
"1Gbps",
"10Gbps",
"2Gbps",
"5Gbps",
"20Gbps",
"50Gbps",
"100Gbps"
],
"supported": [
"1Gbps",
"2Gbps",
"5Gbps",
"10Gbps",
"20Gbps",
"50Gbps",
"100Gbps"
]
},
"type": "LastMile",
"activationPageUrl": "https://connect.lumen.com/enterprise/connections/create-cloud-interconnect",
"remoteIdentifierType": "account"
}
There is one Equinix Environment in each Region, with a state of available and only 1Gbps of bandwidth, which matches the target Regions and bandwidth in the announcement. The location in us-west-1 is Silicon Valley, which is written differently from the San Jose metro in the announcement.
To extract only the Equinix elements, filter with jq.
aws interconnect list-environments --region us-east-1 --output json | jq '.environments[] | select(.provider.lastMileProvider == "equinix")'
Input items for create-connection
I checked the items to pass to create-connection with --generate-cli-skeleton input.
aws interconnect create-connection --generate-cli-skeleton input
{
"description": "",
"bandwidth": "",
"attachPoint": {
"directConnectGateway": "",
"arn": ""
},
"environmentId": "",
"remoteAccount": {
"identifier": ""
},
"tags": {
"KeyName": ""
},
"clientToken": ""
}
The CLI help lists three required items: bandwidth, attachPoint, and environmentId. For attachPoint, you specify either directConnectGateway or arn. According to the user guide, the attach point is a Direct Connect gateway, which you may also create when setting up the connection.
AWS-side pricing
According to the last mile pricing page, the AWS-side charge is hourly, determined by the selected bandwidth and one of five automatically assigned tiers. There is no usage-based charge for data transfer volume. Billing runs from the creation to the deletion of the connection, rounded up to the hour.
Partner-side pricing is separate from this.
According to the announcement, it is free during the preview. As of this writing (November 15, 2026), the pricing page does not list Equinix prices.
Summary
The preview of AWS Interconnect - last mile with Equinix has started, making it possible to connect your own infrastructure in Equinix data centers to AWS.
Compared with conventional Direct Connect, there is no need to arrange cross-connects or configure routers, which reduces the effort and time needed to prepare a connection. Also, because AWS-side pricing is hourly, it looks usable for cases such as migrating data from on-premises to AWS, where you need a stable line only for the necessary period.
I look forward to the bandwidth expansion at GA, and to the expansion of the available Regions, which are currently North America only.
