The Requirement to Associate DX Locations with Regions Has Been Removed from the AWS Direct Connect SLA
This page has been translated by machine translation. View original
Introduction
The AWS Direct Connect SLA was updated on July 24, 2026. The requirement in the Multi-Site SLA that at least one DX location be associated with the Endpoint's Region has been removed.
I could not find any announcement, such as on the official blog. Only the description on the SLA page and the Last Updated date were changed. I learned about this update from Mr. Kikuchi's post.
The removal applies to both Multi-Site Non-Redundant Deployment (99.9%) and Multi-Site Redundant Deployment (99.99%). The difference in requirements for Multi-Site Redundant (99.99%), which has more requirements, is as follows.
| Requirement | Old SLA (2022/05/19) | New SLA (2026/07/24) |
|---|---|---|
| At least one DX location is associated with the Endpoint's Region | Yes | Removed |
| 4 or more Connections, at least 2 each in 2 different locations | Yes | Yes |
| Each Connection is on a unique AWS device | Yes | Yes |
| Enterprise Support | Yes | Yes |
| Well-Architected Review | Yes | Yes |
| Private Endpoints in 2 or more AZs | Yes | Yes |
Multi-Site Non-Redundant (99.9%) requires a configuration with a total of at least 2 Connections across 2 different locations, and the same single line has been removed from it as well.
Verification Details
Differences Between the Old SLA and the New SLA
I compared the current SLA page (Last Updated: July 24, 2026) with the old SLA page (Last Updated: May 19, 2022). Both reflect their content as of July 30, 2026, and I checked the definition text and the Minimum Configuration Requirements table.
Old SLA:
Multi-Site Redundant Deployment is a Deployment that comprises at least four Connections deployed across a minimum of two different Direct Connect locations, each of which is configured to access the same Endpoint, where no fewer than two Connections are deployed in each of the two Direct Connection locations, at least one of the Direct Connection locations is associated with the AWS Region in which the Endpoint is hosted, each Connection is on a unique AWS device, and, with respect to private Endpoints, the Endpoint is deployed in two or more Availability Zones.
New SLA:
Multi-Site Redundant Deployment is a Deployment that comprises at least four Connections deployed across a minimum of two different Direct Connect locations, each of which is configured to access the same Endpoint, where no fewer than two Connections are deployed in each of the two Direct Connection locations, each Connection is on a unique AWS device, and, with respect to private Endpoints, the Endpoint is deployed in two or more Availability Zones.
The removed phrase is the following single item.
at least one of the Direct Connection locations is associated with the AWS Region in which the Endpoint is hosted
(At least one Direct Connect location is associated with the AWS Region in which the Endpoint is hosted)
The same phrase also appeared in the definition text of Multi-Site Non-Redundant Deployment (99.9%), and it was removed from 4 places in total: 2 definition texts and 2 rows of the Minimum Configuration Requirements table. For both the 2-Connection and 4-Connection configurations, the constraint on the associated Region is gone. All other requirements and figures were identical between the old and new versions.
Note that the quotations above go only as far as the configuration conditions in the definition text. The Enterprise Support and Well-Architected Review requirements are described in a later sentence of the definition text and in the requirements table.
Associated AWS Region of DX Locations
Looking at the 5 locations in Japan listed on the DX locations list, the associations were biased toward the Tokyo Region (as of July 30, 2026).
| Location | Associated AWS Region |
|---|---|
| Equinix TY2 (Tokyo) | Asia Pacific (Tokyo) |
| AT Tokyo CC1 (Tokyo) | Asia Pacific (Tokyo) |
| NEC Inzai (Inzai) | Asia Pacific (Tokyo) |
| Equinix OS1 (Osaka) | Asia Pacific (Tokyo) |
| Telehouse Osaka 2 (Osaka) | Asia Pacific (Osaka) |
Only one location, Telehouse Osaka 2, is associated with the Osaka Region, and Equinix OS1, which is located in Osaka, was associated with the Tokyo Region. Note that the Associated AWS Region is merely the Region it is associated with; other Regions can also be reached via a Direct Connect Gateway for private Endpoints, or via a Public VIF for public Endpoints.
Configurations Aiming for 99.99% in the Osaka Region
The greatest impact is on configurations that place 4 Connections, 2 each at DX locations in Tokyo and Osaka, and aim for 99.99% for an Endpoint in the Osaka Region (ap-northeast-3). Whether each combination qualifies is as follows.
| Configuration | Old SLA | New SLA |
|---|---|---|
| 2 at Telehouse Osaka 2 × 2 at Equinix TY2 | ✅ Eligible (Telehouse Osaka 2 is associated with the Osaka Region) | ✅ Eligible |
| 2 at Equinix TY2 × 2 at Equinix OS1 | ❌ Not eligible (does not include a location associated with the Osaka Region) | ✅ Eligible |
| 2 at Equinix TY2 × 2 at AT Tokyo CC1 | ❌ Not eligible | ✅ Eligible |
| 2 at Equinix OS1 × 2 at NEC Inzai | ❌ Not eligible | ✅ Eligible |
Because only one location is associated with the Osaka Region, under the old SLA the only choice was "2 at Telehouse Osaka 2 + 2 at a location associated with the Tokyo Region." Even a geographically separated configuration of 2 at Equinix TY2 in Tokyo + 2 at Equinix OS1 in Osaka was not eligible for 99.99% for an Endpoint in the Osaka Region.
The determination is the same when aiming for 99.9% (Multi-Site Non-Redundant) with a 2-Connection configuration. A configuration of 1 at Equinix TY2 + 1 at Equinix OS1 was not eligible for an Endpoint in the Osaka Region under the old SLA, but becomes eligible under the new SLA.
On the other hand, the situation is different when the Endpoint is in the Tokyo Region (ap-northeast-1). Of the 5 locations in Japan, all 4 other than Telehouse Osaka 2 are associated with the Tokyo Region. Since choosing any 2 different locations guarantees at least one is associated with the Tokyo Region, this requirement was never a constraint even under the old SLA if you configure using only domestic locations, and this removal makes no difference.
Also, as stated in the exclusions on the SLA page, the SLA covers only Dedicated Connections owned by your own account. Hosted Connections and hosted virtual interfaces via APN partners are not covered.
Example in North America
A mismatch between the associated Region and the physical location also occurs in North America. In the DX locations list, Equinix DA2 (Dallas) and Equinix MI1 (Miami) are both associated with US East (Virginia).
A configuration placing 2 Connections at each of these 2 locations was not eligible for an Endpoint in US East (Ohio) under the old SLA, but under the new SLA it becomes eligible as long as the other requirements are met.
Summary
The requirement for association with the Associated AWS Region has been removed from the Multi-Site SLA, allowing more flexibility in choosing DX locations. It is a welcome update that reduces the matters to consider and coordinate when bringing in DX connections.
If you are considering line selection or configuration for DX connections, I recommend checking the new SLA.
