---
title: "How DeepL keeps closest-exit routing during maintenance with AWS Cloud WAN"
description: "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."
---

# How DeepL keeps closest-exit routing during maintenance with AWS Cloud WAN

[AWS](https://yomu.fyi/company/aws) · Guzman Freigedo · Nov 9, 2026

**Type:** Problem & solution

## Summary

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.

## Context

DeepL operates a multi-Region hybrid network across AWS Regions in Europe, North America, and Asia, with two European data centers connected via MPLS. It uses AWS Cloud WAN with a global Direct Connect gateway attached natively to the core network, and three Direct Connect locations (Dublin, Copenhagen, Stockholm). In steady state, egress traffic leaves through the closest Direct Connect location to minimize latency. The team needed to take one Direct Connect link out of service for maintenance while keeping other Regions on their local exit.

## Approach / What changed

DeepL uses an AS\_PATH prepend on the Direct Connect virtual interface of the link being maintained. This makes the path from the Direct Connect gateway to the core network edge in the affected Region longer than the paths from peer edges, so the affected edge prefers a peer path and traffic crosses the core network to exit through another Direct Connect location. The other Regions’ edges still see their local path as the shortest, preserving closest-exit routing.

## Takeaways

- With Direct Connect attached natively to AWS Cloud WAN, each core network edge makes the egress decision based on the preserved on-premises AS\_PATH, not on Direct Connect BGP communities.
- An AS\_PATH prepend on the link being maintained changes the egress decision only on the core network edge that uses that link, leaving other Regions’ closest-exit routing intact.
- During a drain, inter-Region data transfer charges apply because traffic from the affected Region crosses the core network to exit through another Direct Connect location.

## FAQ

### Why does DeepL use at least two AS\_PATH prepends?

A single prepend only ties the AS\_PATH length with peer paths. On a tie, AWS Cloud WAN prefers the route propagated from the Direct Connect gateway, so the drained location would still be used. DeepL uses at least two prepends, and in practice five for margin.

### How does DeepL control which fallback location takes the traffic?

With default path selection, AWS Cloud WAN chooses between equal peer paths, so you don't control whether Copenhagen or Stockholm takes the displaced traffic. Routing policies, which DeepL plans to adopt, address this by allowing explicit preference.

### How does DeepL handle traffic from data centers toward AWS during a drain?

The prepend only steers traffic leaving AWS. Traffic from the data centers toward AWS is chosen by DeepL's own routers. During a drain, DeepL lowers BGP local preference on its routers for routes learned over the drained link's sessions, so that traffic also moves off the link.

**Tags:** [AWS](https://yomu.fyi/topic/aws), [AWS Cloud WAN](https://yomu.fyi/topic/aws-cloud-wan), [BGP](https://yomu.fyi/topic/bgp), [Direct Connect](https://yomu.fyi/topic/direct-connect), [Networking](https://yomu.fyi/topic/networking)

- Source: [AWS](https://aws.amazon.com/blogs/architecture/how-deepl-keeps-closest-exit-routing-during-maintenance-with-aws-cloud-wan)
- Source URL: https://aws.amazon.com/blogs/architecture/how-deepl-keeps-closest-exit-routing-during-maintenance-with-aws-cloud-wan
- Ingested by Yomu: 2026-11-09T21:00:09.082Z

[Read original post](https://aws.amazon.com/blogs/architecture/how-deepl-keeps-closest-exit-routing-during-maintenance-with-aws-cloud-wan)
