AWS wellarchitected documentation change
Summary
Updated terminology from 'AWS VPN' to 'Site-to-Site VPN' in the context of failover recommendations for Direct Connect connections.
Security assessment
The change clarifies the specific VPN service type (Site-to-Site VPN) but does not address security vulnerabilities, mitigations, or security features. The content focuses on performance limitations (throughput, ECMP support) during failover scenarios rather than security controls or risks.
Diff
diff --git a/wellarchitected/2023-04-10/framework/rel_planning_network_topology_ha_conn_private_networks.md b/wellarchitected/2023-04-10/framework/rel_planning_network_topology_ha_conn_private_networks.md index bb8fa9719..0367f7074 100644 --- a//wellarchitected/2023-04-10/framework/rel_planning_network_topology_ha_conn_private_networks.md +++ b//wellarchitected/2023-04-10/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.