What Is AWS Migration Hub & How It Works ?

How does Migration Hub works in AWS?

What Is AWS Migration Hub & How It Works ?


AWS offers multiple solutions to help you migrate to AWS cloud including database, server and application migration services,  Storage Gateway, Snowball and Snowmobile. Different workloads require different tools. AWS Migration Hub is a service that provides a unified console to track activities across multiple tools, providing better visibility.

It also provides key metrics and progress for individual applications, regardless of which tools have been used to migrate them.

You can use the tools that best fit your needs and track the process, across all those tools in a single place. The hub lets you track your process into any AWS region that your AWS tool supports and this hub has no extra layer of charge, you only pay for the tools used and any other resources being used in AWS. There are three different types of AWS services whose activities can be traced to the hub.

AWS Application Migration Service:

The hub is built on top of application discovery service and it uses Discovery for your servers and your applications. That is where you group your servers into applications, and then you track those applications into your hub as you migrate the servers and databases there.

AWS Server Migration Service: This helps you move WAMPs into AWS and it is integrated with the hub. Once you connect it to the hub you can then track the status of all your tasks in the server migration service inside the hub and you can group them into applications and track them as a unit throughout the process.

AWS Database Migration Service:

It helps you both rehost and re-platform databases into AWS. For re-host, you can move into the homogeneous platform into the AWS, for re-platforming or upgrading you can move your database from the basic version to the upgraded version of the same platform or, you can go from one platform to the other (the heterogeneous way). The process will send status into the hub and then you can view it alongside the status of the AWS server or any of the partner tools inside of the application groups.


There are two ways to use the AWS migration hub. One is to start with discovery and then use the track. Deploy connectors or agents into your dataset, depending on the information you need and what level of detail is needed. Then once you deploy those, start collecting your servers and start grouping them into applications. You can do this from the console, or you can export the data, analyze it outside of the hub, and then bring in your app groupings via the CLI or console.

Once you are ready to move your first applications you’ll start collecting and connecting your tools. So, you might pick server and database migration service and you authorize them to send status to your hub. Once you have authorized those tools you have your app groupings, you can start migrating the application in the tool. Itself.

Once you have moved all the applications of the source server, you can decommission it. Another way is to use only the migration track. The alternative way is to make a discovery using some other tool, or simply skip the discovery process and start migrating. You select the tools, authorize them to send status to the hub and then you can go to the tool itself and set up your migration tasks.

No Comments

Post A Comment



16 + 2 =