Migration and Transfer
AWS Transform MGN
On the radar· Application Migration Service is now AWS Transform MGNAutomates the migration of physical, virtual, or other-cloud servers to AWS (rehosting) by continuously replicating them at the block level and converting them so they boot on AWS. As a result, the final cutover usually takes minutes. It was formerly called AWS Application Migration Service.
Exam phrases that point here
«migrate the servers as they are (lift-and-shift) to Amazon EC2»
AWS Transform MGN (formerly AWS Application Migration Service) does rehosting: it replicates physical, virtual, or other-cloud servers and converts them so they boot as EC2 instances, without redesigning the application. It is the same service under its current name; in older questions it appears as Application Migration Service.
When not: If you only need to move the data of a database, or change engines, it points to AWS DMS. If the goal is to redesign the application (for example, to containers or serverless) instead of moving it as is, MGN would only be a first step.
«migrate hundreds of servers with minimal downtime during cutover»
Continuous block-level replication keeps an up-to-date copy of each disk in AWS; the cutover only launches the instances from that copy, which is why it usually takes minutes.
When not: If what needs to move is files (not entire servers), the clue points to AWS DataSync; if it is databases that must keep receiving changes, to AWS DMS with CDC.
«test the migrated servers in AWS without affecting the source environment»
MGN launches test instances from the replica while the source server keeps running and replicating; you can test as many times as needed before the cutover.
When not: If the scenario is about testing changes to an application already in AWS with little risk (for example, blue/green deployments), the answer is in the deployment tools, not in MGN.
«move EC2 instances to another Region or to another AWS account»
The sources MGN supports include EC2 instances themselves, to move them between Regions or accounts.
When not: If the goal is a backup or disaster recovery across Regions, AWS Backup or AWS Elastic Disaster Recovery fits, not a migration with MGN.
«replicate the servers to AWS without using the public internet»
MGN replication can go over a VPN, AWS Direct Connect, or another private connection, using private IPs to the staging subnet.
When not: The private connection is a networking requirement, not a feature of the service: the same clue can appear with DataSync or DMS. What decides the answer is what is being moved: entire servers, files, or databases.
Often paired with
- Amazon EC2