AWS vpn documentation change
Summary
Updated terminology from 'VPN concentrator' to 'Site-to-Site VPN Concentrator' for consistency
Security assessment
The change is a terminology update without addressing security vulnerabilities or introducing security features.
Diff
diff --git a/vpn/latest/s2svpn/customer-gateway-device-windows.md b/vpn/latest/s2svpn/customer-gateway-device-windows.md index 1c56691dc..31cb54a21 100644 --- a//vpn/latest/s2svpn/customer-gateway-device-windows.md +++ b//vpn/latest/s2svpn/customer-gateway-device-windows.md @@ -150 +150 @@ The pre-shared key that is used to establish the IPsec VPN connection between `L -We suggest that you configure both tunnels as part of the VPN connection. Each tunnel connects to a separate VPN concentrator on the Amazon side of the VPN connection. Although only one tunnel at a time is up, the second tunnel automatically establishes itself if the first tunnel goes down. Having redundant tunnels ensure continuous availability in the case of a device failure. Because only one tunnel is available at a time, the Amazon VPC console indicates that one tunnel is down. This is expected behavior, so there's no action required from you. +We suggest that you configure both tunnels as part of the VPN connection. Each tunnel connects to a separate Site-to-Site VPN Concentrator on the Amazon side of the VPN connection. Although only one tunnel at a time is up, the second tunnel automatically establishes itself if the first tunnel goes down. Having redundant tunnels ensure continuous availability in the case of a device failure. Because only one tunnel is available at a time, the Amazon VPC console indicates that one tunnel is down. This is expected behavior, so there's no action required from you.