AWS prescriptive-guidance documentation change
Summary
Changed 'AWS VPN or AWS Direct Connect' to 'AWS VPN or Direct Connect' in architecture description
Security assessment
This is a minor terminology adjustment without security implications. The documentation continues to emphasize using private network channels for all traffic, but doesn't introduce new security information or address vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/restrictive.md b/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/restrictive.md index 55b047135..7aa28500a 100644 --- a//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/restrictive.md +++ b//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/restrictive.md @@ -7 +7 @@ -The following diagram displays the architecture of the most restrictive scenario, where all traffic goes over the private channel (AWS VPN or AWS Direct Connect) between the source environment and AWS. +The following diagram displays the architecture of the most restrictive scenario, where all traffic goes over the private channel (AWS VPN or Direct Connect) between the source environment and AWS.