AWS prescriptive-guidance documentation change
Summary
Updated 'AWS Direct Connect services' to 'Direct Connect services' in private subnet configuration
Security assessment
Terminology refinement without changes to security architecture or access controls.
Diff
diff --git a/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/configuration.md b/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/configuration.md index 3c6f411d7..ce831f263 100644 --- a//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/configuration.md +++ b//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/configuration.md @@ -24 +24 @@ The following sections assume that the initial Application Migration Service con -For the restrictive scenario, you configure the required AWS resources in the private subnet of a staging VPC. This subnet has no connectivity to the internet (there's no internet gateway attached to the routing table as a default route). Instead, it uses either a virtual gateway associated with an [AWS Site-to-Site VPN](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html) gateway (connected through an IPsec tunnel to an on-premises gateway), or it's connected to a transfer gateway or to AWS Direct Connect services to provide private interconnectivity to the on-premises data centers. +For the restrictive scenario, you configure the required AWS resources in the private subnet of a staging VPC. This subnet has no connectivity to the internet (there's no internet gateway attached to the routing table as a default route). Instead, it uses either a virtual gateway associated with an [AWS Site-to-Site VPN](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html) gateway (connected through an IPsec tunnel to an on-premises gateway), or it's connected to a transfer gateway or to Direct Connect services to provide private interconnectivity to the on-premises data centers.