AWS network-manager documentation change
Summary
Removed 'Route evaluation' section detailing Cloud WAN's route prioritization logic for core network edges
Security assessment
Deletion of operational documentation about routing logic. No evidence of security vulnerability fixes or security feature changes.
Diff
diff --git a/network-manager/latest/cloudwan/cloudwan-create-attachment.md b/network-manager/latest/cloudwan/cloudwan-create-attachment.md index f03ddd767..5bd87e461 100644 --- a//network-manager/latest/cloudwan/cloudwan-create-attachment.md +++ b//network-manager/latest/cloudwan/cloudwan-create-attachment.md @@ -7,2 +6,0 @@ -Route evaluation - @@ -51,31 +48,0 @@ You can create an attachment using either using the Network Manager console or b -## Route evaluation - -Cloud WAN evaluates routes at each core network edge in the following order: - - 1. The most specific route for the destination - - 2. For routes with the same destination IP address, but different targets, the following route priority is used: - - 1. Static routes - - 2. VPC-propagated routes in the same Region. - - 3. For dynamic routes received at the core network with an _unequal_ AS path length and/or MED BGP attributes, Cloud WAN evaluates them in the following order: - - 1. AS path length - - 2. MED - - 4. For dynamic routes received at the core network with _equal_ AS path length and MED BGP attributes, Cloud WAN evaluates them in the following order: - - 1. Direct Connect gateway-propagated routes. - - 2. Cloud WAN Connect-propagates routes in the same Region. - - 3. Site-to-Site VPN-propagated routes in the same Region. - - 4. Routes propagated from other sources, such as transit gateway peering and core network edges in other remote Regions over the AWS global infrastructure. If identical routes are received from two or more sources, a single attachment will be chosen in a deterministically random manner. - - - -