Arkinu
AWS service comparison

AWS Application Discovery Service vs AWS Transform MGN: differences and when to use each

AWS Application Discovery Service
AWS Transform MGN

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Migration and Transfer

AWS Application Discovery Service

On the radar· Application Discovery Service no longer accepts new customers

Collects usage and configuration data about on-premises servers and databases to plan a migration to AWS, for example to group servers into applications based on their network connections. It has not accepted new customers since November 7, 2025; AWS points to AWS Transform as the alternative.

Exam phrases that point here

  • «collect information about on-premises servers to plan the migration to AWS»

    Application Discovery Service inventories on-premises servers and databases (configuration, CPU, memory, and disk usage) to decide what to migrate and how to size it on AWS. Note: since November 7, 2025 it no longer accepts new customers, and AWS suggests AWS Transform for new projects.

    When not: Discovering is not migrating: if the scenario asks to move the servers to EC2, it points to AWS Transform MGN (formerly AWS Application Migration Service), and if it asks to move the data of a database, to AWS DMS. In a current scenario, the tool AWS recommends for discovery is AWS Transform.

  • «identify the network dependencies between servers before migrating them»

    The Discovery Agent records each server's inbound and outbound network connections; with them you can see which servers talk to each other and group them into applications to migrate together.

    When not: The VMware Agentless Collector does not see the processes running inside each VM. If you only need resource usage and nothing must be installed on the servers, the agentless collector is enough; if the goal is to monitor network traffic already in AWS, think of VPC Flow Logs, not this service.

  • «discover the VMware vCenter virtual machines without installing an agent on each one»

    The Agentless Collector is deployed as an appliance (OVA) in vCenter and from there it discovers the hosts and VMs, with their configuration and their average and peak usage.

    When not: If there are physical servers or you need to know which processes run inside each machine, the agentless collector is not enough and the Discovery Agent is installed on each server.

  • «estimate the size and cost of EC2 instances based on the actual usage of on-premises servers»

    The performance and usage data the service collects can be exported for a cost model or used to generate EC2 instance type recommendations.

    When not: If the servers are already in AWS and the goal is to right-size the instances in use, the clue points to AWS Compute Optimizer.

  • «query the discovery data of all servers with SQL in one place»

    With data exploration turned on, the data from the Discovery Agents is periodically stored in an S3 bucket and queried with Amazon Athena, which comes with predefined queries for performance, processes, and network dependencies.

    When not: This continuous export only works with data from the Discovery Agents, not with data from the Agentless Collector. If the source data does not come from discovery, the usual combination is S3 + Athena without this service.

Study AWS Application Discovery Service →

Migration and Transfer

AWS Transform MGN

On the radar· Application Migration Service is now AWS Transform MGN

Automates 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
Study AWS Transform MGN →