AWS prescriptive-guidance documentation change
Summary
Updated service references from 'AWS Application Migration Service' to 'AWS Transform MGN' and adjusted related terminology
Security assessment
Changes involve rebranding/reference updates without altering security concepts. The documentation continues to discuss using VPC endpoints for private connectivity, but no new security content was added and there's no evidence of addressing a specific vulnerability.
Diff
diff --git a/prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/introduction.md b/prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/introduction.md index e72bd5c3a..061e10b88 100644 --- a//prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/introduction.md +++ b//prescriptive-guidance/latest/rehost-multi-account-architecture-interface-endpoints/introduction.md @@ -15 +15 @@ Targeted business outcomesIntended audience -Many organizations rehost (lift and shift) their applications to AWS from isolated or semi-isolated network environments, including on-premises data centers and other cloud or hybrid infrastructures, by using [AWS Application Migration Service](https://aws.amazon.com/application-migration-service/). These isolated networks typically do not allow any egress traffic to the public endpoints that are described in the [network requirements for Application Migration Service](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-1500). You can address this limitation by using virtual private cloud (VPC) interface endpoints, as discussed in 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). +Many organizations rehost (lift and shift) their applications to AWS from isolated or semi-isolated network environments, including on-premises data centers and other cloud or hybrid infrastructures, by using [AWS Transform MGN](https://aws.amazon.com/application-migration-service/). These isolated networks typically do not allow any egress traffic to the public endpoints that are described in the [network requirements for MGN](https://docs.aws.amazon.com/mgn/latest/ug/Network-Requirements.html#Communication-TCP-1500). You can address this limitation by using virtual private cloud (VPC) interface endpoints, as discussed in 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). @@ -17 +17 @@ Many organizations rehost (lift and shift) their applications to AWS from isolat -Many organizations also use a multi-account landing zone (MALZ) architecture for isolation, security, and per-account billing benefits. To enable lift-and-shift migration by using Application Migration Service over a secured network to multiple target AWS accounts, you must create VPC interface endpoints in every target AWS account. This adds to the cost and complexity of managing those resources. +Many organizations also use a multi-account landing zone (MALZ) architecture for isolation, security, and per-account billing benefits. To enable lift-and-shift migration by using MGN over a secured network to multiple target AWS accounts, you must create VPC interface endpoints in every target AWS account. This adds to the cost and complexity of managing those resources. @@ -35 +35 @@ The [solution to this scenario](./solution-2.html) involves creating VPC endpoin - * Your applications are mapped to different business units, and you want to migrate them to different AWS target accounts in the same AWS Region for billing and isolation purposes. You also want to use fewer VPCs for Application Migration Service staging, and you want to centrally manage routing for the staging VPCs to reduce costs and administrative overhead. + * Your applications are mapped to different business units, and you want to migrate them to different AWS target accounts in the same AWS Region for billing and isolation purposes. You also want to use fewer VPCs for MGN staging, and you want to centrally manage routing for the staging VPCs to reduce costs and administrative overhead.