AWS prescriptive-guidance documentation change
Summary
Updated terminology and links: changed 'Site-to-Site VPN' to 'AWS VPN', expanded product names (MGN to AWS Transform MGN), fixed punctuation, and improved consistency in service naming (S3 to Amazon S3, EBS to Amazon EBS).
Security assessment
Changes are editorial improvements without security implications. No vulnerabilities, weaknesses, or security incidents are addressed. Updates focus on branding consistency and documentation clarity.
Diff
diff --git a/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/architecture.md b/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/architecture.md index 3af6b5a23..a4279347f 100644 --- a//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/architecture.md +++ b//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/architecture.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) @@ -15 +15 @@ This section provides a detailed description of the most restrictive scenario, w -The [staging subnet](https://docs.aws.amazon.com/mgn/latest/ug/subnet.html) is the most important part of the replication infrastructure. This is where all MGN [replication servers](https://docs.aws.amazon.com/mgn/latest/ug/replication-server-settings.html) will be launched, and it contains the IP addresses the replication traffic will be directed to. For inbound private data replication, configure the [replication server settings](https://docs.aws.amazon.com/mgn/latest/ug/template-vs-server.html) for MGN with the [Use private IP option](https://docs.aws.amazon.com/mgn/latest/ug/use-private-ip.html). +The [staging subnet](https://docs.aws.amazon.com/mgn/latest/ug/subnet.html) is the most important part of the replication infrastructure. This is where all AWS Transform MGN [replication servers](https://docs.aws.amazon.com/mgn/latest/ug/replication-server-settings.html) will be launched, and it contains the IP addresses the replication traffic will be directed to. For inbound private data replication, configure the [replication server settings](https://docs.aws.amazon.com/mgn/latest/ug/template-vs-server.html) for MGN with the [Use private IP option](https://docs.aws.amazon.com/mgn/latest/ug/use-private-ip.html). @@ -17 +17 @@ The [staging subnet](https://docs.aws.amazon.com/mgn/latest/ug/subnet.html) is t -For [outbound requirements](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-443-Staging), you can use the [Create public IP](https://docs.aws.amazon.com/mgn/latest/ug/use-private-ip.html#public-ip) option to choose whether replication servers will communicate with required AWS services (Amazon S3, MGN, Amazon EC2) over private or public IP. The standard options to provide outbound internet connectivity are listed in the [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-443-Staging): either a public IP address with an internet gateway or a private IP address with a NAT gateway. Both options allow you to implement a simplified hybrid scenario in which data replication traffic goes over a private connection (Site-to-Site VPN or AWS Direct Connect) while replication servers communicate with AWS services over the public network. +For [outbound requirements](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-443-Staging), you can use the [Create public IP](https://docs.aws.amazon.com/mgn/latest/ug/use-private-ip.html#public-ip) option to choose whether replication servers will communicate with required AWS services (Amazon S3, MGN, Amazon EC2) over private or public IP. The standard options to provide outbound internet connectivity are listed in the [MGN documentation](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-443-Staging): either a public IP address with an internet gateway or a private IP address with a NAT gateway. Both options allow you to implement a simplified hybrid scenario in which data replication traffic goes over a private connection (AWS VPN or AWS Direct Connect) while replication servers communicate with AWS services over the public network. @@ -28 +28 @@ However, having public outbound connectivity is usually prohibited in closed cor -To learn more about VPC endpoints, see the [AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html) documentation. +To learn more about VPC endpoints, see the [AWS PrivateLink documentation](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html). @@ -47 +47 @@ This guide focuses on a more restrictive scenario where even HTTPS traffic to AW - * An [inbound DNS resolver endpoint](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-network-to-vpc), to allow on-premises sources and DNS servers to resolve private IP addresses for VPC endpoints, located in the staging subnet + * An [inbound DNS resolver endpoint](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resolver.html#resolver-overview-forward-network-to-vpc), to allow on-premises sources and DNS servers to resolve private IP addresses for VPC endpoints, located in the staging subnet. @@ -54 +54 @@ This guide focuses on a more restrictive scenario where even HTTPS traffic to AW -The target subnet is any subnet that you plan to launch your servers into, including test and cutover instances. These subnets have no network connectivity requirement at all, and could be located in any other VPC in the same AWS account and Region. This is because Application Migration Service uses Amazon EC2 APIs to create new test or cutover instances (which is why replication servers in the staging subnet require outbound HTTPS connectivity to Amazon EC2), and accesses Regional S3 snapshots created from replicated EBS volumes. None of these operations require direct network access to or from the target subnet, so this could even be a completely isolated private subnet. +The target subnet is any subnet that you plan to launch your servers into, including test and cutover instances. These subnets have no network connectivity requirement at all, and could be located in any other VPC in the same AWS account and Region. This is because MGN uses Amazon EC2 APIs to create new test or cutover instances (which is why replication servers in the staging subnet require outbound HTTPS connectivity to Amazon EC2), and accesses Regional Amazon S3 snapshots created from replicated Amazon EBS volumes. None of these operations require direct network access to or from the target subnet, so this could even be a completely isolated private subnet. @@ -56 +56 @@ The target subnet is any subnet that you plan to launch your servers into, inclu -However, MGN also [automatically installs](https://docs.aws.amazon.com/mgn/latest/ug/AWS-Related-FAQ.html#Which-AWS-Services-Automatically-Installed-Target) several tools such as EC2Config or AWS Systems Manager Agents (SSM Agents) on target instances, and these activities require outbound HTTPS/TCP port 443 connectivity from target instances and subnets. +However, MGN also [automatically installs](https://docs.aws.amazon.com/mgn/latest/ug/AWS-Related-FAQ.html#Which-AWS-Services-Automatically-Installed-Target) several tools, such as EC2Config or AWS Systems Manager Agents (SSM Agents) on target instances, and these activities require outbound HTTPS/TCP port 443 connectivity from target instances and subnets.