AWS vpn documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in two instances.
Security assessment
This is a minor terminology update without security implications. No security context, vulnerabilities, or security features are referenced in the change.
Diff
diff --git a/vpn/latest/s2svpn/VPN_CloudHub.md b/vpn/latest/s2svpn/VPN_CloudHub.md index c94caccff..97ea3d2ef 100644 --- a//vpn/latest/s2svpn/VPN_CloudHub.md +++ b//vpn/latest/s2svpn/VPN_CloudHub.md @@ -32 +32 @@ For this scenario, do the following: -Sites that use AWS Direct Connect connections to the virtual private gateway can also be part of the AWS VPN CloudHub. For example, your corporate headquarters in New York can have an AWS Direct Connect connection to the VPC and your branch offices can use Site-to-Site VPN connections to the VPC. The branch offices in Los Angeles and Miami can send and receive data with each other and with your corporate headquarters, all using the AWS VPN CloudHub. +Sites that use Direct Connect connections to the virtual private gateway can also be part of the AWS VPN CloudHub. For example, your corporate headquarters in New York can have an Direct Connect connection to the VPC and your branch offices can use Site-to-Site VPN connections to the VPC. The branch offices in Los Angeles and Miami can send and receive data with each other and with your corporate headquarters, all using the AWS VPN CloudHub.