AWS prescriptive-guidance documentation change
Summary
Changed 'AWS VPN or AWS Direct Connect' to 'AWS VPN or Direct Connect' in architecture diagram description
Security assessment
The change appears to be a terminology/style update rather than addressing security concerns. It maintains the same security posture by continuing to recommend private channels (VPN/Direct Connect) for replication data.
Diff
diff --git a/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/hybrid1.md b/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/hybrid1.md index f2e8eeac4..799aa0b46 100644 --- a//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/hybrid1.md +++ b//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/hybrid1.md @@ -7 +7 @@ -The following diagram illustrates the architecture in the hybrid scenario where HTTPS egress traffic is allowed from any source servers and is used to communicate with Application Migration Service and Amazon S3 endpoints, whereas the replication data on TCP port 1500 goes over the private channel (AWS VPN or AWS Direct Connect) between the source environment and AWS. +The following diagram illustrates the architecture in the hybrid scenario where HTTPS egress traffic is allowed from any source servers and is used to communicate with Application Migration Service and Amazon S3 endpoints, whereas the replication data on TCP port 1500 goes over the private channel (AWS VPN or Direct Connect) between the source environment and AWS.