AWS network-manager documentation change
Summary
Removed 'Tunnel-less Connect' terminology and made structural edits to routing documentation
Security assessment
Terminology changes and documentation restructuring about BGP routing. No security vulnerabilities mentioned or addressed. Focuses on protocol capabilities rather than security features.
Diff
diff --git a/network-manager/latest/cloudwan/cloudwan-connect-attachment.md b/network-manager/latest/cloudwan/cloudwan-connect-attachment.md index e7b4114af..34ff694bf 100644 --- a/network-manager/latest/cloudwan/cloudwan-connect-attachment.md +++ b/network-manager/latest/cloudwan/cloudwan-connect-attachment.md @@ -5 +5 @@ -Tunnel-less ConnectRoutingThird-party appliance limitations +RoutingThird-party appliance limitations @@ -19 +19 @@ A Connect attachment must be created in the same AWS account that owns the core -## Tunnel-less Connect +## @@ -21 +21 @@ A Connect attachment must be created in the same AWS account that owns the core -AWS Cloud WAN supports Tunnel-less Connect for VPC Connect attachments. Tunnel-less Connect provides a simpler way to build a global SD-WAN using AWS. Third-party SD-WAN appliances can peer with Cloud WAN using Border Gateway Protocol (BGP) without needing to deploy IPsec or GRE-based tunnels between the appliance and Cloud WAN. This allows you to deploy a Cloud WAN core network across multiple AWS Regions and to connect one or more of your third-party SD-WAN appliances to core network edges in each Region. Because Tunnel-less Connect has no tunneling overhead, it provides better performance and peak bandwidth on TLC attachments. IPSec provides 1.25G, allowing you to combine up to eight tunnels while providing up to the entire VPC attachment bandwidth. GRE supports only 5G, which means you'd need to deploy specialized techniques, such as ECMP (Equal Cost Multi-pathing), for scaling bandwidth across tunnels. +AWS Cloud WAN supports for VPC Connect attachments. provides a simpler way to build a global SD-WAN using AWS. Third-party SD-WAN appliances can peer with Cloud WAN using Border Gateway Protocol (BGP) without needing to deploy IPsec or GRE-based tunnels between the appliance and Cloud WAN. This allows you to deploy a Cloud WAN core network across multiple AWS Regions and to connect one or more of your third-party SD-WAN appliances to core network edges in each Region. Because has no tunneling overhead, it provides better performance and peak bandwidth on TLC attachments. IPSec provides 1.25G, allowing you to combine up to eight tunnels while providing up to the entire VPC attachment bandwidth. GRE supports only 5G, which means you'd need to deploy specialized techniques, such as ECMP (Equal Cost Multi-pathing), for scaling bandwidth across tunnels. @@ -23 +23 @@ AWS Cloud WAN supports Tunnel-less Connect for VPC Connect attachments. Tunnel-l -You can use the console or API to specify the Tunnel-less Connect protocol. +You can use the console or API to specify the protocol. @@ -25 +25 @@ You can use the console or API to specify the Tunnel-less Connect protocol. -In order to use Tunnel-less Connect, note the following: +In order to use , note the following: @@ -29 +29 @@ In order to use Tunnel-less Connect, note the following: - * Attachment policy tags or resource names are used to associate the Tunnel-less Connect attachment to the SD-WAN segment. + * Attachment policy tags or resource names are used to associate the attachment to the SD-WAN segment. @@ -42 +42 @@ In order to use Tunnel-less Connect, note the following: -Tunnel-less Connect uses BGP for dynamic routing. Therefore, any third-party SD-WAN appliance you want to use for Tunnel-less Connect must support BGP. SD-WAN appliances peer with a core network using the Connect attachment functioning in a tunnel-less manner. It uses native BGP to dynamically exchange routing and reachability information between SD-WAN appliance in the VPC and the core network edge. We recommend using a different autonomous number (ASN) on your SD-WAN appliance from the one configured on the core network edge. +uses BGP for dynamic routing. Therefore, any third-party SD-WAN appliance you want to use for must support BGP. SD-WAN appliances peer with a core network using the Connect attachment functioning in a tunnel-less manner. It uses native BGP to dynamically exchange routing and reachability information between SD-WAN appliance in the VPC and the core network edge. We recommend using a different autonomous number (ASN) on your SD-WAN appliance from the one configured on the core network edge. @@ -44 +44 @@ Tunnel-less Connect uses BGP for dynamic routing. Therefore, any third-party SD- -Tunnel-less Connect also supports also supports Multiprotocol extension for BGP (MP- BGP) in order to support both IPv4/IPv6 address families. +also supports also supports Multiprotocol extension for BGP (MP- BGP) in order to support both IPv4/IPv6 address families. @@ -46 +46 @@ Tunnel-less Connect also supports also supports Multiprotocol extension for BGP -You'll need to configure the following in the VPC route table used for Tunnel-less Connect: +You'll need to configure the following in the VPC route table used for :