---
title: "AWS Cloud WAN: Where a Region's Egress Decision Is Made"
description: "AWS Cloud WAN is a managed core network that joins Regions, VPCs, and on-premises sites through attachments. This architecture view shows where the per-Region egress decision is made and how one link can be drained safely."
---

# AWS Cloud WAN: Where a Region's Egress Decision Is Made

**Type:** [Architecture](https://yomu.fyi/visual-explainers/category/architecture.md)

![Three-band diagram: on-premises data centers link over Direct Connect into a central Cloud WAN core network with three regional core edges, which attach to VPCs. Blue arrows show closest-exit egress; an amber dashed arrow shows one region rerouting across the core backbone during maintenance.](https://yomufyi.s3.us-east-1.amazonaws.com/visual-explainers/e3129365-3579-4329-be53-d01d9a4a5f9a/image-138e34fc-ce9f-41e0-9aed-278dc9341b76.webp)

> AWS Cloud WAN is a managed core network that joins Regions, VPCs, and on-premises sites through attachments. This architecture view shows where the per-Region egress decision is made and how one link can be drained safely.

## Explanation

AWS Cloud WAN is a managed core network that joins AWS Regions, VPC attachments, and on-premises sites through a single policy-governed backbone. Each Region has a core network edge that chooses the egress path, and in a hybrid setup that choice follows the preserved on-premises AS\_PATH rather than Direct Connect BGP communities. That distinction matters during maintenance: prepending the AS\_PATH on one Direct Connect link steers only the affected Region to a peer path across the core, while every other Region keeps its closest exit. The diagram maps those parts and the one decision point engineers actually tune.

## FAQ

### Why does a Cloud WAN core edge ignore Direct Connect BGP communities?

In DeepL's hybrid setup, each core network edge makes its egress decision from the preserved on-premises AS\_PATH, not from Direct Connect BGP communities. That is why prepending the AS\_PATH on one link changes the decision for the affected Region only. Other Regions keep their local exit because their paths remain the shortest.

### How do you drain one Direct Connect link without moving every Region's egress?

Apply an AS\_PATH prepend on the link being maintained. Only the affected Region's core edge then prefers a peer path and crosses the core network to another Direct Connect location, while the remaining Regions keep their closest exit.

### What do Cloud WAN routing policies add over per-link BGP tuning?

DeepL plans to adopt AWS Cloud WAN routing policies for deterministic failover and route summarization. That moves intent out of hand-tuned per-link BGP manipulation and into a declarative policy on the core network, which is easier to reason about during planned maintenance.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture.md), [AWS](https://yomu.fyi/topic/aws.md), [AWS Cloud WAN](https://yomu.fyi/topic/aws-cloud-wan.md), [Direct Connect](https://yomu.fyi/topic/direct-connect.md), [Networking](https://yomu.fyi/topic/networking.md), [Routing](https://yomu.fyi/topic/routing.md)

## Related reading

### [Databricks' Commitment to European Sovereignty](https://yomu.fyi/post/databricks-commitment-to-european-sovereignty.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Rory Patterson
- Published: Nov 9, 2026
- Type: Announcement

Databricks has invested in Europe since 2017, now serving thousands of enterprises across 17 cloud regions with over 2,000 employees. The company is expanding sovereign cloud commitments by building three new European regions on Azure Italy, Azure Spain, and AWS European Sovereign Cloud. Databricks is working with Microsoft to extend sovereign controls to Azure Databricks, including operational oversight and transparency measures. The platform will also be made natively available on AWS European Sovereign Cloud, a physically independent EU-operated cloud. Databricks plans to add further controls over time, including support for open standard compatible storage to keep data on-premises or in European clouds.


### [How DeepL keeps closest-exit routing during maintenance with AWS Cloud WAN](https://yomu.fyi/post/how-deepl-keeps-closest-exit-routing-during-maintenance-with-aws-cloud.md)
- Company: [AWS](https://yomu.fyi/company/aws.md)
- Author: Guzman Freigedo
- Published: Nov 9, 2026
- Type: Problem & solution

DeepL operates a multi-Region hybrid network across AWS Regions and two European data centers, using AWS Cloud WAN with a native Direct Connect gateway attachment. For planned maintenance, the team needed to drain a single Direct Connect link while preserving closest-exit egress for all other Regions. They identified that each core network edge makes the egress decision based on the preserved on-premises AS\_PATH, not on Direct Connect BGP communities. By applying an AS\_PATH prepend on the link being maintained, only the affected Region’s edge prefers a peer path, and traffic crosses the core network to another Direct Connect location. The other Regions keep their local exit because their paths remain the shortest. DeepL plans to adopt AWS Cloud WAN routing policies for deterministic failover and route summarization.


### [Atlas Data Federation And Online Archive Can Now Be Deployed In Azure](https://yomu.fyi/post/atlas-data-federation-and-online-archive-can-now-be-deployed-in-azure.md)
- Company: [MongoDB](https://yomu.fyi/company/mongodb.md)
- Published: Nov 9, 2026
- Type: Announcement

MongoDB announced the General Availability of Atlas Data Federation and Atlas Online Archive on Microsoft Azure. Atlas Data Federation can now be deployed directly in Azure and can query data in Azure Blob Storage and Azure Data Lake Storage Gen2 alongside Atlas clusters. Atlas Online Archive on Azure lets users choose AWS or Azure for archival storage, with new archives on Azure clusters defaulting to Azure regions if no pre-existing AWS archives exist. Both services do not support cross-cloud queries between AWS S3 and Azure Blob Storage in the same federated instance. These updates give Azure users more flexibility in data management and archiving within the Azure ecosystem.


### [How public sector organizations can govern AI at scale](https://yomu.fyi/post/how-public-sector-organizations-can-govern-ai-at-scale.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Kacey Hertan, Antonio Javier Samaniego Jurado
- Published: Nov 6, 2026
- Type: Problem & solution

Public sector organizations face unique governance challenges when adopting AI, including data residency restrictions, cost control, and model access, which often cause projects to stall because compliance and budget teams cannot get the answers they need. Traditional AI tools and third-party coding agents were not designed to address these requirements, leaving agencies unable to show regulators where data goes or which teams are driving spending. Databricks addresses this with Unity Gateway, a centralized AI governance solution built into its platform, allowing administrators to control which models are enabled, set hard spending caps by user or team, and enforce data residency policies. The platform also uses Smart Routing to direct routine tasks to lower-cost models, stretching budgets further without sacrificing quality. By providing unified visibility and controls, Unity Gateway enables public sector organizations to adopt AI at scale while meeting strict compliance and budget requirements, reversing the pattern of stalled adoption.
