AWS whitepapers documentation change
Summary
Renamed 'AWS VPN CloudHub' to 'Site-to-Site VPN CloudHub' throughout the document, updating terminology and architecture references
Security assessment
The changes are purely terminological updates from 'AWS VPN CloudHub' to 'Site-to-Site VPN CloudHub' without altering security properties or introducing new security considerations. No vulnerabilities or security enhancements are mentioned.
Diff
diff --git a/whitepapers/latest/aws-vpc-connectivity-options/aws-vpn-cloudhub.md b/whitepapers/latest/aws-vpc-connectivity-options/aws-vpn-cloudhub.md index 1b0092f47..35dca4c0c 100644 --- a//whitepapers/latest/aws-vpc-connectivity-options/aws-vpn-cloudhub.md +++ b//whitepapers/latest/aws-vpc-connectivity-options/aws-vpn-cloudhub.md @@ -7 +7 @@ Additional resources -# AWS VPN CloudHub +# Site-to-Site VPN CloudHub @@ -9 +9 @@ Additional resources -Building on the AWS managed VPN options described previously, you can securely communicate from one site to another using the AWS VPN CloudHub. The AWS VPN CloudHub operates on a simple hub-and-spoke model that you can use with or without a VPC. Use this approach if you have multiple branch offices and existing internet connections and would like to implement a convenient, potentially low-cost hub-and-spoke model for primary or backup connectivity between these remote offices. +Building on the AWS managed VPN options described previously, you can securely communicate from one site to another using the Site-to-Site VPN CloudHub. The Site-to-Site VPN CloudHub operates on a simple hub-and-spoke model that you can use with or without a VPC. Use this approach if you have multiple branch offices and existing internet connections and would like to implement a convenient, potentially low-cost hub-and-spoke model for primary or backup connectivity between these remote offices. @@ -11 +11 @@ Building on the AWS managed VPN options described previously, you can securely c -The following figure shows the AWS VPN CloudHub architecture, with lines indicating network traffic between remote sites being routed over their AWS VPN connections. +The following figure shows the Site-to-Site VPN CloudHub architecture, with lines indicating network traffic between remote sites being routed over their Site-to-Site VPN connections. @@ -13 +13 @@ The following figure shows the AWS VPN CloudHub architecture, with lines indicat - + @@ -15 +15 @@ The following figure shows the AWS VPN CloudHub architecture, with lines indicat -_AWS VPN CloudHub_ +_Site-to-Site VPN CloudHub_ @@ -17 +17 @@ _AWS VPN CloudHub_ -AWS VPN CloudHub uses an Amazon VPC virtual private gateway with multiple customer gateways, each using unique BGP autonomous system numbers (ASNs). The remote sites must not have overlapping IP ranges. Your gateways advertise the appropriate routes (BGP prefixes) over their VPN connections. These routing advertisements are received and re-advertised to each BGP peer so that each site can send data to and receive data from the other sites. +Site-to-Site VPN CloudHub uses an Amazon VPC virtual private gateway with multiple customer gateways, each using unique BGP autonomous system numbers (ASNs). The remote sites must not have overlapping IP ranges. Your gateways advertise the appropriate routes (BGP prefixes) over their VPN connections. These routing advertisements are received and re-advertised to each BGP peer so that each site can send data to and receive data from the other sites.