AWS wellarchitected documentation change
Summary
Replaced 'AWS VPN' with 'Site-to-Site VPN' terminology
Security assessment
Terminology update for VPN service naming. No security implications as technical limitations (throughput/ECMP) and failover recommendations remain unchanged. No vulnerabilities or security features discussed.
Diff
diff --git a/wellarchitected/2023-10-03/framework/rel_planning_network_topology_ha_conn_private_networks.md b/wellarchitected/2023-10-03/framework/rel_planning_network_topology_ha_conn_private_networks.md index 9d782a7ba..c3a52c261 100644 --- a//wellarchitected/2023-10-03/framework/rel_planning_network_topology_ha_conn_private_networks.md +++ b//wellarchitected/2023-10-03/framework/rel_planning_network_topology_ha_conn_private_networks.md @@ -30 +30 @@ If you choose to connect your VPC to your data center using a Direct Connect con -If you choose to fail over to VPN over the internet using AWS VPN, it’s important to understand that it supports up to 1.25-Gbps throughput per VPN tunnel, but does not support Equal Cost Multi Path (ECMP) for outbound traffic in the case of multiple AWS Managed VPN tunnels terminating on the same VGW. We do not recommend that you use AWS Managed VPN as a backup for Direct Connect connections unless you can tolerate speeds less than 1 Gbps during failover. +If you choose to fail over to VPN over the internet using Site-to-Site VPN, it’s important to understand that it supports up to 1.25-Gbps throughput per VPN tunnel, but does not support Equal Cost Multi Path (ECMP) for outbound traffic in the case of multiple AWS Managed VPN tunnels terminating on the same VGW. We do not recommend that you use AWS Managed VPN as a backup for Direct Connect connections unless you can tolerate speeds less than 1 Gbps during failover.