AWS prescriptive-guidance documentation change
Summary
Updated links, service names (AWS Transform MGN), image paths, and DNS terminology (Route 53 Profiles). Clarified private channel options as AWS VPN/Direct Connect.
Security assessment
Changes involve terminology updates (e.g., 'Route 53 Profiles' instead of 'Route 53 inbound resolver') and service name standardization. No evidence of addressing vulnerabilities or security incidents. The modifications improve accuracy but don't introduce security features or mitigate risks.
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 728154d03..ad3482621 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 @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating on-premises servers to AWS over private networks by using AWS Transform MGN](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating on-premises servers to AWS over private networks by using AWS Transform MGN](introduction.html) @@ -9 +9 @@ -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 (Site-to-Site VPN or 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 AWS Transform MGN 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. @@ -11 +11 @@ The following diagram illustrates the architecture in the hybrid scenario where - + @@ -13 +13 @@ The following diagram illustrates the architecture in the hybrid scenario where -This architecture simplifies the requirements for the staging area subnet, because HTTPS communications from agents don't travel through the private channel. Also, there is no need to create additional Amazon S3 interface VPC endpoints or Amazon Route 53 inbound resolver endpoints for DNS traffic, because source servers will use their traditional DNS servers to resolve the standard, public DNS names of MGN and Amazon S3 endpoints. +This architecture simplifies the requirements for the staging area subnet, because HTTPS communications from agents don't travel through the private channel. Also, there is no need to create additional Amazon S3 interface VPC endpoints or Amazon Route 53 Profiles inbound resolver endpoints for DNS traffic, because source servers will use their traditional DNS servers to resolve the standard, public DNS names of MGN and Amazon S3 endpoints.