Migration Hub tracking, tagging, and console navigation tips - AWS Migration Hub
Tracking migration updatesTracking metrics using the dashboardTagging migration resources

Migration Hub tracking, tagging, and console navigation tips

This section describes how to track migrations, tag migration resources, and navigate the AWS Migration Hub console.

Tracking migration updates

In order to better understand how Migration Hub helps you monitor progress of a migration, there are three concepts to understand in the Migration Hub:

  • Applications

  • Resources (for example, servers)

  • Updates

Migration tools like AWS Application Migration Service (Application Migration Service), AWS Database Migration Service (AWS DMS), and integrated partners' tools send updates to AWS Migration Hub. These updates include information about how a particular resource migration (for example, server or database) is progressing. One or more resources are grouped together to make an application. Each application has a dedicated page in Migration Hub where you can go to see the updates for all the resources in the application.

When Migration Hub receives an update, it is displayed on the updates page. There can be a delay of up to five minutes for the initial update to appear in the updates page.

Tracking when you perform discovery first and then migrate

If you started performing discovery using AWS discovery tools, the servers list will likely be populated before you start migrating. Migration Hub attempts to automatically map updates from migration tools to servers in the servers list. If it cannot find a match in the discovered servers list, then Migration Hub will add a server corresponding to the migration update to the servers list and automatically map the update to the server.

Sometimes, when using AWS discovery tools, the automatic mapping of migration updates to servers can be incorrect. You can see updates and their mappings on the Updates page and can correct the mapping by choosing Edit.

See Step 2.a in To determine if a migration update must be manually mapped to a discovered server procedures below. If you have to frequently correct mappings after performing discovery, contact AWS Support.

To determine if a migration update must be manually mapped to a discovered server

  1. In the navigation pane, under Migrate, select Updates.

  2. Verify if the Mapped servers column is populated for every row of migration updates.

    1. If the Mapped servers column is populated for every row of migration updates, this means auto-mapping was supported by the migration tool and manual mapping is not required. To edit the server mapping, select the server, and then choose Edit server mapping.

    2. If one or more rows of the Mapped servers columns is not populated, this is an indication that manual mapping is required. Proceed to the next set of procedures.

Tracking when you migrate without performing discovery

If you did not perform discovery with an AWS discovery tool, then Migration Hub will add a server that corresponds with the migration update to the servers list and automatically map the update to the server. You can group servers as applications and then start tracking the migration on the application’s details page in the Migrate section of the console. For more information, see Step 3: Group servers as applications and Track the status of your migrations in Migration Hub.

Troubleshooting and manually mapping migration updates

You can verify that the migration update is mapped to a server by viewing the update on the Updates page. If a server has not been mapped to a migration and you just started the migration task, see if it appears as mapped after waiting five minutes and refreshing the page.

If after an initial wait of five minutes the update is still not mapped to a server, then you can manually map the update to a server by selecting the Map button. For more information, see the following procedure, To manually map a migration update to a discovered server. For officially supported migration tools, you should not need to manually map migration updates. If this happens frequently, please contact AWS Support.

The following steps show you how to manually map a migration update to a discovered server that was not able to be automapped.

To manually map a migration update to a discovered server

  1. In the navigation pane, under Migrate, select Updates.

  2. For each migration update row that has a Map button present in the Action column, select the Map button.

  3. In the Map to discovered server box, select the radio button of the server you want to map to the migration update.

  4. Choose Save. A green confirmation message appears at the top of the screen.

  5. Verify that the server name of the server you just mapped is now present in the Mapped servers column.

Tracking metrics using the dashboard

Dashboards provide a way to quickly see status and progress summary data, and also help you navigate to more detailed data.

Dashboard

The dashboard consists of four at-a-glance status and information sections as well as links for quick access to more details. These sections allow you to understand the summary status of most recently updated applications and also get quick access to any of them, to get an overview of applications in different states, and to track the migration progress over time.

To reach the Dashboard, choose Dashboard from the Migration Hub console navigation pane.

After viewing dashboard data summaries, you might want to retrieve more detail without interrupting your workflow. You do this by navigating directly from the relevant status or information pane on the dashboard.

In the following table, you can find instructions on how to navigate from a dashboard to the information you want to see. You can also find instructions on how to get to this information by using the navigation pane.

To navigate to the Dashboard, choose Dashboard from the Migration Hub console navigation pane.

To See Do This Which Is the Same As
All servers

On the Dashboard in the Discovery summary section, under Servers, choose the number.

In the Migration Hub console navigation pane, choose Servers.
All agents

On the Dashboard in the Discovery summary section, under Agents, choose the number.

In the navigation pane, under Discover choose Data Collectors, and then choose the Agents tab.
All applications

On the Dashboard in the Discovery summary section, under Applications, choose the number.

In the navigation pane, under Migrate, choose Applications.
Application details

On the Dashboard in the Most recently updated applications section, choose the name of the application to see details.

  1. In the navigation pane, under Migrate, choose Applications.

  2. In the Application name column, choose the name of the application.

Server details

  1. On the Dashboard in the Discovery summary section, under Servers, choose the number.

  2. In the Server info column, choose the server name.

  1. In the navigation pane, under Discover, choose Servers.

  2. In the Server info column, choose the name of the server.

Tagging migration resources

Migrated resources (Amazon EC2 instances or Amazon Machine Images (AMIs)) reported to Migration Hub by migration tools—like AWS Application Migration Service—are automatically tagged with Application Discovery Service server IDs.

If you turn on cost allocation tagging, you can view the cost of the AWS resources that are tagged by Migration Hub in the AWS Cost Explorer Service. Resource tagging by Migration Hub can’t be turned off. This tagging is implemented automatically and doesn't count against your limit of 50 tags per resource.

These resources have the aws:migrationhub:source-id tag, and the source-id matches the server.configurationId server asset field from Application Discovery Service. For more information, see the following topics: