AWS prescriptive-guidance documentation change
Summary
Updated service references from 'Application Migration Service' to 'MGN' or 'Transform MGN' throughout the document, including console addresses, agent names, and pattern titles.
Security assessment
Changes are purely rebranding updates reflecting a service name change from 'Application Migration Service' to 'MGN'. No security vulnerabilities, configurations, or practices are modified. Network requirements (ports, protocols) and IAM roles remain unchanged.
Diff
diff --git a/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/deployment.md b/prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/deployment.md index e905a4731..a5125d9b4 100644 --- a//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/deployment.md +++ b//prescriptive-guidance/latest/rehost-servers-over-private-networks-mgn/deployment.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 Application Migration Service](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](welcome.html) @@ -24 +24 @@ Alternatively, you can deploy your PoC environment by following the steps in the -The following list outlines the major steps for manual deployments in your environment. For more information, see the AWS Prescriptive Guidance pattern [Connect to Application Migration Service data and control planes over a private network](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/connect-to-application-migration-service-data-and-control-planes-over-a-private-network.html?did=pg_card&trk=pg_card). +The following list outlines the major steps for manual deployments in your environment. For more information, see the AWS Prescriptive Guidance pattern [Connect to MGN data and control planes over a private network](https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/connect-to-application-migration-service-data-and-control-planes-over-a-private-network.html?did=pg_card&trk=pg_card). @@ -30 +30 @@ The following list outlines the major steps for manual deployments in your envir - * Application Migration Service, and enable the private DNS name (shared by the replication server and source server). + * MGN, and enable the private DNS name (shared by the replication server and source server). @@ -34 +34 @@ The following list outlines the major steps for manual deployments in your envir - * Amazon S3 (private DNS name not supported). Interface endpoints are supported across Direct Connect, Site-to-Site VPN, and VPC peering. Therefore, this is required for source servers only (and could be located on premises) to connect to the Application Migration Service control plane over a private network. + * Amazon S3 (private DNS name not supported). Interface endpoints are supported across Direct Connect, Site-to-Site VPN, and VPC peering. Therefore, this is required for source servers only (and could be located on premises) to connect to the MGN control plane over a private network. @@ -53 +53 @@ Source | Destination | Port | Description -**Source data center** | The Application Migration Service AWS Region-specific console address | 443 (TCP) | [Communication between the source servers and Application Migration Service over TCP port 443](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Source-Manager-TCP-443) +**Source data center** | The MGN AWS Region-specific console address | 443 (TCP) | [Communication between the source servers and MGN over TCP port 443](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Source-Manager-TCP-443) @@ -55 +55 @@ Source | Destination | Port | Description -**Staging area subnet** | The Application Migration Service AWS Region-specific console address | 443 (TCP) | [Communication between the staging area subnet and Application Migration Service over TCP port 443](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-443-Staging) +**Staging area subnet** | The MGN AWS Region-specific console address | 443 (TCP) | [Communication between the staging area subnet and MGN over TCP port 443](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-443-Staging) @@ -61 +61 @@ Source | Destination | Port | Description - 8. Create an AWS Identity and Access Management (IAM) role for installing Application Migration Service Agent. Attach managed policies and generate access keys and a secrets key. + 8. Create an AWS Identity and Access Management (IAM) role for installing MGN Agent. Attach managed policies and generate access keys and a secrets key. @@ -72 +72 @@ Source | Destination | Port | Description -The [Cloud Migration Factory on AWS](https://aws.amazon.com/solutions/implementations/cloud-migration-factory-on-aws/) automates the deployment of the Application Migration Service Agent for the private networks scenario, with additional command line parameters. When you deploy this solution (see options for [automated deployment](https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/deployment.html)), you can use these scripts and one of the following options: +The [Cloud Migration Factory on AWS](https://aws.amazon.com/solutions/implementations/cloud-migration-factory-on-aws/) automates the deployment of the MGN Agent for the private networks scenario, with additional command line parameters. When you deploy this solution (see options for [automated deployment](https://docs.aws.amazon.com/solutions/latest/cloud-migration-factory-on-aws/deployment.html)), you can use these scripts and one of the following options: @@ -83 +83 @@ These scripts automate the following: - * Application Migration Service Agent installation on a Windows server using private endpoints + * MGN Agent installation on a Windows server using private endpoints @@ -85 +85 @@ These scripts automate the following: - * Application Migration Service Agent installation on Linux servers using private endpoints + * MGN Agent installation on Linux servers using private endpoints