AWS whitepapers documentation change
Summary
Updated terminology from 'AWS VPN' to 'Site-to-Site VPN' in headings, image captions, and pricing links to align with product naming conventions
Security assessment
Changes focus on branding/naming consistency rather than addressing security vulnerabilities or introducing security features. The updates clarify product terminology but don't mention security controls, vulnerabilities, or security-related configuration changes.
Diff
diff --git a/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/vpn.md b/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/vpn.md index bf2c28622..13349ba6e 100644 --- a//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/vpn.md +++ b//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/vpn.md @@ -9 +9 @@ There are various ways to set up VPN to AWS: - + @@ -11 +11 @@ There are various ways to set up VPN to AWS: -__AWS VPN options__ +__Site-to-Site VPN options__ @@ -13 +13 @@ __AWS VPN options__ - * **Option 1: Consolidate VPN connectivity on Transit Gateway** — This option leverages the Transit Gateway VPN attachment on Transit Gateway. Transit Gateway supports IPsec termination for site-to-site VPN. Customers can create VPN tunnels to the Transit Gateway, and can access the VPCs attached to it.Transit Gateway supports both Static and BGP-based Dynamic VPN connections. Transit Gateway also supports [Equal-Cost Multi-Path](https://en.wikipedia.org/wiki/Equal-cost_multi-path_routing) (ECMP) on VPN attachments. Each VPN connection has a maximum of 1.25-Gbps throughput per tunnel. Enabling ECMP allows you to aggregate throughput across VPN connections, allowing to scale beyond the default maximum limit of 1.25 Gbps. In this option, you pay for [Transit Gateway pricing](https://aws.amazon.com/transit-gateway/pricing/) as well as [AWS VPN pricing](https://aws.amazon.com/vpn/pricing/). AWS recommendeds using this option for VPN connectivity. For more information, refer to the [Scaling VPN throughput using AWS Transit Gateway](https://aws.amazon.com/blogs/networking-and-content-delivery/scaling-vpn-throughput-using-aws-transit-gateway/) blog post. + * **Option 1: Consolidate VPN connectivity on Transit Gateway** — This option leverages the Transit Gateway VPN attachment on Transit Gateway. Transit Gateway supports IPsec termination for site-to-site VPN. Customers can create VPN tunnels to the Transit Gateway, and can access the VPCs attached to it.Transit Gateway supports both Static and BGP-based Dynamic VPN connections. Transit Gateway also supports [Equal-Cost Multi-Path](https://en.wikipedia.org/wiki/Equal-cost_multi-path_routing) (ECMP) on VPN attachments. Each VPN connection has a maximum of 1.25-Gbps throughput per tunnel. Enabling ECMP allows you to aggregate throughput across VPN connections, allowing to scale beyond the default maximum limit of 1.25 Gbps. In this option, you pay for [Transit Gateway pricing](https://aws.amazon.com/transit-gateway/pricing/) as well as [Site-to-Site VPN pricing](https://aws.amazon.com/vpn/pricing/). AWS recommendeds using this option for VPN connectivity. For more information, refer to the [Scaling VPN throughput using AWS Transit Gateway](https://aws.amazon.com/blogs/networking-and-content-delivery/scaling-vpn-throughput-using-aws-transit-gateway/) blog post. @@ -17 +17 @@ __AWS VPN options__ - * **Option 3: Terminate VPN on a virtual private gateway** **(VGW)** — This AWS Site-to-Site VPN service option enables a one-to-one connectivity design where you create one VPN connection (consisting of a pair of redundant VPN tunnels) per VPC. This is great way to get started with VPN connectivity into AWS, but as you scale the number of VPCs, managing a growing number of VPN connections can become challenging. Therefore, edge consolidation design leveraging Transit Gateway will eventually be a better option. VPN throughput to a VGW is limited to 1.25 Gbps per tunnel and ECMP load balancing is not supported. From a pricing perspective, you only pay for AWS VPN pricing, there is no charge for running a VGW. For more information, refer to [AWS VPN Pricing](https://aws.amazon.com/vpn/pricing/) and [AWS VPN on virtual private gateway](https://docs.aws.amazon.com/vpn/latest/s2svpn/how_it_works.html). + * **Option 3: Terminate VPN on a virtual private gateway** **(VGW)** — This AWS Site-to-Site VPN service option enables a one-to-one connectivity design where you create one VPN connection (consisting of a pair of redundant VPN tunnels) per VPC. This is great way to get started with VPN connectivity into AWS, but as you scale the number of VPCs, managing a growing number of VPN connections can become challenging. Therefore, edge consolidation design leveraging Transit Gateway will eventually be a better option. VPN throughput to a VGW is limited to 1.25 Gbps per tunnel and ECMP load balancing is not supported. From a pricing perspective, you only pay for AWS VPN pricing, there is no charge for running a VGW. For more information, refer to [Site-to-Site VPN Pricing](https://aws.amazon.com/vpn/pricing/) and [Site-to-Site VPN on virtual private gateway](https://docs.aws.amazon.com/vpn/latest/s2svpn/how_it_works.html).