AWS whitepapers documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in Cloud WAN network connectivity context
Security assessment
Brand name shortening without technical changes. Network segmentation discussion remains unchanged with no new security implications.
Diff
diff --git a/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/aws-cloud-wan.md b/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/aws-cloud-wan.md index 02a218173..54017cb2e 100644 --- a//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/aws-cloud-wan.md +++ b//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/aws-cloud-wan.md @@ -7 +7 @@ -AWS Cloud WAN is a new way to connect networks together that we were previously able to do with Transit Gateways, VPC Peering, and IPSEC VPN tunnels. Previously you would configure one or more VPCs, connect them together with one of the previous methods, and use IPSEC VPN or AWS Direct Connect to connect to on-premises networks. You would have your network and security posture constructs defined in one place, and your networks in another. Cloud WAN allows you to centralize all of these constructs in a single place. By policy, you can segment your networks to determine who can talk to who, and isolate production traffic via these segments from development or test workloads, or your on premises networks. +AWS Cloud WAN is a new way to connect networks together that we were previously able to do with Transit Gateways, VPC Peering, and IPSEC VPN tunnels. Previously you would configure one or more VPCs, connect them together with one of the previous methods, and use IPSEC VPN or Direct Connect to connect to on-premises networks. You would have your network and security posture constructs defined in one place, and your networks in another. Cloud WAN allows you to centralize all of these constructs in a single place. By policy, you can segment your networks to determine who can talk to who, and isolate production traffic via these segments from development or test workloads, or your on premises networks.