AWS network-manager documentation change
Summary
Clarified BGP peer address requirement to use private IPv4 and corrected typo in IPv6 address exchange documentation.
Security assessment
The change specifies 'private IPv4 address' instead of generic 'IPv4 address', promoting use of internal addresses as a security best practice to reduce exposure. However, there is no explicit evidence of a resolved security vulnerability. The typo correction ('addres' to 'address') is unrelated to security.
Diff
diff --git a/network-manager/latest/cloudwan/cloudwan-connect-peer-attachment.md b/network-manager/latest/cloudwan/cloudwan-connect-peer-attachment.md index 93050771b..1a293f297 100644 --- a//network-manager/latest/cloudwan/cloudwan-connect-peer-attachment.md +++ b//network-manager/latest/cloudwan/cloudwan-connect-peer-attachment.md @@ -89 +89 @@ The **Details** tab displays the **Connect protocol**. Make sure to choose a Con - 9. For the **Peer BGP address** , enter the appliance's IPv4 address. + 9. For the **Peer BGP address** , enter the appliance's private IPv4 address. @@ -93 +93 @@ The **Details** tab displays the **Connect protocol**. Make sure to choose a Con -BGP peering primarily uses IPv4 addresses, but it does support IPv6 addres exchange through MP-BGP. To establsih BGP sessions for IPv6 Unicast, you must have IPv4 Unicast addressing. +BGP peering primarily uses IPv4 addresses, but it does support IPv6 address exchange through MP-BGP. To establsih BGP sessions for IPv6 Unicast, you must have IPv4 Unicast addressing.