AWS directconnect documentation change
Summary
Expanded documentation on IP address configuration for Direct Connect, adding details about RFC 3927 and recommended practices for VPC traffic
Security assessment
While the changes provide more detailed networking guidance, they don't specifically address security vulnerabilities or introduce new security features
Diff
diff --git a/directconnect/latest/UserGuide/add-peer-to-vif.md index c0b0a34fc..bfc9f4a77 100644 --- a/directconnect/latest/UserGuide/add-peer-to-vif.md +++ b/directconnect/latest/UserGuide/add-peer-to-vif.md @@ -41 +41,5 @@ Use the following procedure to add a BGP peer. -If you let AWS auto-assign IP addresses, a /29 CIDR will be allocated from 169.254.0.0/16. AWS does not recommend this option if you intend to use the customer router peer IP address as the source and destination for traffic. Instead you should use RFC 1918 or other addressing, and specify the address yourself. For more information about RFC 1918 see [ Address Allocation for Private Internets](https://datatracker.ietf.org/doc/html/rfc1918). +When configuring AWS Direct Connect virtual interfaces, you can specify your own IP addresses using RFC 1918, use other addressing schemes, or opt for AWS assigned IPv4 /29 CIDR addresses allocated from the RFC 3927 169.254.0.0/16 IPv4 Link-Local range for point-to-point connectivity. These point-to-point connections should be used exclusively for eBGP peering between your customer gateway router and the Direct Connect endpoint. For VPC traffic or tunnelling purposes, such as AWS Site-to-Site Private IP VPN, or Transit Gateway Connect, AWS recommends using a loopback or LAN interface on your customer gateway router as the source or destination address instead of the point-to-point connections. + + * For more information about RFC 1918, see [Address Allocation for Private Internets](https://datatracker.ietf.org/doc/html/rfc1918). + + * For more information about RFC 3927, see [Dynamic Configuration of IPv4 Link-Local Addresses](https://datatracker.ietf.org/doc/html/rfc3927).