AWS Migration Hub

(1)

AWS Migration Hub

User Guide

(2)

AWS Migration Hub: User Guide

Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be aﬃliated with, connected to, or sponsored by Amazon.

(3)

What Is AWS Migration Hub?

AWS Migration Hub (Migration Hub) provides a single place to discover your existing servers, plan migrations, and track the status of each application migration. The Migration Hub provides visibility into your application portfolio and streamlines planning and tracking. You can visualize the connections and the status of the servers and databases that make up each of the applications you are migrating, regardless of which migration tool you are using.

Migration Hub gives you the choice to start migrating right away and group servers while migration is underway, or to ﬁrst discover servers and then group them into applications. Either way, you can migrate each server in an application and track progress from each tool in the AWS Migration Hub.

Migration Hub supports migration status updates from the following tools:

• AWS Application Migration Service (Application Migration Service)–AWS Application Migration Service is the primary migration service recommended for lift-and-shift migrations to AWS. For more information about Application Migration Service, see AWS Application Migration Service and Application Migration Service Documentation.

• AWS Server Migration Service (AWS SMS)–For more information about AWS SMS, see AWS Server Migration Service and AWS SMS Documentation.

Warning

As of March 31, 2022, AWS will discontinue AWS Server Migration Service (AWS SMS). You must complete your active migration projects that are using AWS SMS by March 31, 2022.

Going forward, we recommend AWS Application Migration Service (Application Migration Service) as the primary migration service for lift-and-shift migrations. For more information, see Using the AWS Migration Hub with Application Migration Service.

• AWS Database Migration Service (AWS DMS)–For more information about AWS DMS, see AWS Database Migration Service and AWS DMS Documentation.

To access these tools, open the AWS Migration Hub console at https://console.aws.amazon.com/

migrationhub/, and in the navigation pane under Migrate, choose Tools. (You must ﬁrst have an AWS account and credentials to access the Migration Hub console. For information about signing up for AWS, see Setting up (p. 3).)

Are you a ﬁrst-time user of AWS Migration Hub?

On your ﬁrst use of the AWS Migration Hub console, you’re prompted to select a Migration Hub home region where your migration tracking data will be stored. You can choose a home region on the Settings page of the console. After you select a home region, you are redirected automatically to the console in that AWS Region. You must make a selection before you can perform any write action from the console, SDK, or CLI interfaces.

If you are a ﬁrst-time user of AWS Migration Hub, we recommend that you read the following sections in order:

• Getting started (p. 5)

• The AWS Migration Hub home Region (p. 19)

To learn about sending status to or querying status from AWS Migration Hub using the AWS SDK or AWS CLI, see the following API references:

(6)

Are you a ﬁrst-time user of AWS Migration Hub?

• AWS Migration Hub API (p. 60)

• AWS Migration Hub Home Region API

NoteOnly your migration tracking data is stored in your home region. You can migrate into any AWS Region that is supported by the migration tool that you use.

(7)

Sign up for AWS

Setting up

Before you use AWS Migration Hub for the ﬁrst time, if you have not done so, complete the following tasks:

1.Sign up for AWS (p. 3) 2.Create an IAM user (p. 3)

Sign up for AWS

When you sign up for Amazon Web Services (AWS), you are charged only for the services that you use. If you already have an AWS account, you can skip this step.

If you have an AWS account already, skip to the next task. If you don't have an AWS account, use the following procedure to create one.

To create an AWS account

1. Open https://portal.aws.amazon.com/billing/signup.

2. Follow the online instructions.

Part of the sign-up procedure involves receiving a phone call and entering a veriﬁcation code on the phone keypad.

Note your AWS account number, because you'll need it for the next task.

Create an IAM user

Services in AWS, such as AWS Migration Hub, require that you provide credentials when you access them, so that the service can determine whether you have permissions to access its resources. AWS recommends that you do not use the root credentials of your AWS account to make requests. Instead, create an IAM user, and grant that user full access. We refer to these users as administrator users. You can use the administrator user credentials, instead of root credentials of your account, to interact with AWS and perform tasks, such as create a bucket, create users, and grant them permissions. For more information, see Root Account Credentials vs. IAM User Credentials in the AWS General Reference and IAM Best Practices in the IAM User Guide.

If you signed up for AWS but have not created an IAM user for yourself, you can create one using the IAM console.

To create an administrator user for yourself and add the user to an administrators group (console)

1. Sign in to the IAM console as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password.

Note

We strongly recommend that you adhere to the best practice of using the Administrator IAM user that follows and securely lock away the root user credentials. Sign in as the root user only to perform a few account and service management tasks.

(8)

Create an IAM user

2. In the navigation pane, choose Users and then choose Add user.

3. For User name, enter Administrator.

4. Select the check box next to AWS Management Console access. Then select Custom password, and then enter your new password in the text box.

5. (Optional) By default, AWS requires the new user to create a new password when ﬁrst signing in. You can clear the check box next to User must create a new password at next sign-in to allow the new user to reset their password after they sign in.

6. Choose Next: Permissions.

7. Under Set permissions, choose Add user to group.

8. Choose Create group.

9. In the Create group dialog box, for Group name enter Administrators.

10. Choose Filter policies, and then select AWS managed - job function to ﬁlter the table contents.

11. In the policy list, select the check box for AdministratorAccess. Then choose Create group.

Note

You must activate IAM user and role access to Billing before you can use the

AdministratorAccess permissions to access the AWS Billing and Cost Management console. To do this, follow the instructions in step 1 of the tutorial about delegating access to the billing console.

12. Back in the list of groups, select the check box for your new group. Choose Refresh if necessary to see the group in the list.

13. Choose Next: Tags.

14. (Optional) Add metadata to the user by attaching tags as key-value pairs. For more information about using tags in IAM, see Tagging IAM entities in the IAM User Guide.

15. Choose Next: Review to see the list of group memberships to be added to the new user. When you are ready to proceed, choose Create user.

You can use this same process to create more groups and users and to give your users access to your AWS account resources. To learn about using policies that restrict user permissions to speciﬁc AWS resources, see Access management and Example policies.

To sign in as this new IAM user, sign out of the AWS Management Console, and then use the following URL, where your_aws_account_id is your AWS account number without the hyphens (for example, if your AWS account number is 1234-5678-9012, your AWS account ID is 123456789012):

https://your_aws_account_id.signin.aws.amazon.com/console/

Enter the IAM user name and password that you just created. When you're signed in, the navigation bar displays your_user_name@your_aws_account_id.

If you don't want the URL for your sign-in page to contain your AWS account ID, you can create an account alias. From the IAM dashboard, click Create Account Alias and enter an alias, such as your company name. To sign in after you create an account alias, use the following URL:

https://your_account_alias.signin.aws.amazon.com/console/

To verify the sign-in link for IAM users for your account, open the IAM console and check under AWS Account Alias on the dashboard.

(9)

Assumptions

Getting started with AWS Migration Hub

In this section, you can ﬁnd information about how to get started with AWS Migration Hub. Included are steps to introduce you to the initial console pages that Migration Hub presents to a new user.

Before you begin, be sure to set your home Region, either from the console or by using commands in the CLI.

The ﬁrst time you view the Migration Hub console, you'll be prompted to choose a home Region. You can choose and view your current home Region on the Migration Hub Settings page. To navigate to the Settings page, choose Settings in the navigation pane. After the home Region is set, it can only be changed by contacting AWS Support. For information, see The AWS Migration Hub home Region (p. 19).

NoteIf you are a developer or are interested in sending migration status from a migration tool, script, or custom code, see AWS Migration Hub API (p. 60) and AWSAWS Migration Hub Home

Region API Reference.

All Migration Hub and AWS Application Discovery Service API commands must be called from within the home Region only, and they require you to call GetHomeRegion at least once before you call any other API, to obtain the account's Migration Hub home Region. Calls originating from outside your home Region are rejected.

Topics

• Assumptions (p. 5)

• Access to AWS Migration Hub (p. 6)

• Discovering on-premises resources using AWS discovery tools (p. 6)

• Migrate to AWS using Migration Hub migration tools and tracking (p. 10)

• Strategy Recommendations (p. 14)

• Refactor Spaces (p. 14)

Assumptions

For the Migration Hub walkthroughs, we make the following assumptions:

• You have signed up for AWS. For more information, see Setting up (p. 3).

• You have selected your Migration Hub home Region.

Here's what to expect:

• Migration Hub monitors the status of your migrations in all AWS Regions, provided that your migration tools are available in each Region.

• The migration status of every AWS Region undergoing migration is shown in your home Region console.

• The migration tools that integrate with Migration Hub store all data about your migration status in Migration Hub. The data is stored in your selected home Region.

• The migration tools do not send a status unless you have authorized their connection.

(10)

Access to AWS Migration Hub

• For a list of AWS Regions where you can use Migration Hub, see the Amazon Web Services General Reference.

• For more information about working with your home Region, see the section about The AWS Migration Hub home Region (p. 19).

Access to AWS Migration Hub

AWS Migration Hub tracks the status of application migrations on the AWS Migration Hub console in your home Region. The Getting Started section and other sections of this guide use the console to illustrate migration functionality. Open the AWS Migration Hub console at https://

console.aws.amazon.com/migrationhub/.

Additionally, you can use the AWS Migration Hub API to track the status of your migrations from other tools, or to send custom migration status to AWS Migration Hub. For more information about the Migration Hub API, see AWS Migration Hub API (p. 60). You'll also need to call the GetHomeRegion API from the Migration Hub home region API when working with Migration Hub programmatically.

The AWS SDKs assist you to develop applications that interact with Migration Hub. The AWS SDKs for Java, .NET, and PHP wrap the underlying Migration Hub API to simplify your programming tasks. For information about downloading the SDK libraries, see Sample Code Libraries.

Discovering on-premises resources using AWS discovery tools

AWS Migration Hub (Migration Hub) provides a single place to discover your existing servers, plan migrations, and track the status of each application migration. Before migrating you can discover information about your on-premises server and application resources to help you build a business case for migrating or to build a migration plan.

Discovering your servers ﬁrst is an optional starting point for migrations, gathering detailed server information, and then grouping the discovered servers into applications to be migrated and tracked.

Migration Hub also gives you the choice to start migrating right away and to group servers during migration.

You get the data about your servers and applications into the AWS Migration Hub console by using the following discovery tools.

• Migration Hub import – With Migration Hub import, you can import information about your on- premises servers and applications into Migration Hub, including server speciﬁcations and utilization data. You can also use this data to track the status of application migrations. For more information, see Migration Hub import in the Application Discovery Service User Guide.

• AWS Agentless Discovery Connector – The Discovery Connector is a VMware appliance that can collect information about VMware virtual machines (VMs). You install the Discovery Connector as a VM in your VMware vCenter Server environment using an Open Virtualization Archive (OVA) ﬁle. Using the Discovery Connector minimizes the time required for initial on-premises infrastructure assessment. For more information, see AWS Agentless Discovery Connector in the Application Discovery Service User Guide.

• AWS Application Discovery Agent – The Discovery Agent is AWS software that you install on your on- premises servers and VMs to capture system conﬁguration, system performance, running processes, and details of the network connections between systems. Agents support most Linux and Windows operating systems, and you can deploy them on physical on-premises servers, Amazon EC2 instances, and virtual machines. For more information, see AWS Application Discovery Agent in the Application Discovery Service User Guide.

(11)

Step 1: Choose and deploy discovery tools

Topics

• Step 1: Choose and deploy AWS discovery tools (p. 7)

• Step 2: View server details and dependencies (p. 8)

• Step 3: Group servers as applications (p. 9)

Step 1: Choose and deploy AWS discovery tools

You get the data about your servers and applications into the AWS Migration Hub console by using the AWS discovery tools.

To use the discovery tools

1. In the Migration Hub console navigation pane, choose Discover and then choose Tools.

2. On the Discovery Tools page, you can download AWS discovery tools or import data.

To help you decide whether to download a Discovery Connector or a Discovery Agent, see Compare Connectors and Agents in the Application Discovery Service User Guide.

If you have already performed discovery using an AWS Migration Partner discovery tool or have existing data from data sources such as a Conﬁguration Management Database (CMDB) or IT Asset Management System (ITAM), you can use Migration Hub import to upload this data. For more information, see Migration Hub Import in the Application Discovery Service User Guide.

The following sections describe how to deploy either an ??? (p. 7) or an AWS Application Discovery Agent (p. 7).

Discovery using the AWS Agentless Discovery Connector

The following procedure describes the discovery process using an AWS Agentless Discovery Connector for collecting data about your on-premises resources.

The Discovery Connector is a VMWare appliance (OVA), and can only collect information about VMWare VMs.

You use a Discovery Connector because it lets you quickly assess your infrastructure using a tool that isn’t speciﬁc to any operating system, without having to install anything on the servers themselves.

To discover resources using an agentless connector

1. In the Migration Hub console navigation pane, under Discover, choose Tools, and then choose Download connector.

2. Deploy and conﬁgure the agentless connector by following the instructions in Download the Discovery Connector in the AWS Application Discovery Service User Guide.

3. After you have successfully installed the agentless connector, return to the Migration Hub console navigation pane, under Discover choose Data Collectors. Then, refresh your internet browser.

4. On the Connectors tab, select the connector(s) that you want to start.

5. Choose Start data collection.

To install additional connectors, repeat the procedure.

Discovery using the AWS Application Discovery Agent

The following procedure describes the discovery process for collecting data about your on-premises resources using an AWS Application Discovery Agent.

(12)

Step 2: View server details

You can install Discovery Agents on both your VMs and physical servers to not only discover your on-premises servers, but also to capture technical speciﬁcations, system performance, network dependencies, and to process information. Network dependency and process information is available, but only for export. Use the Application Discovery Service CLI to export the data and analyze it outside of the Migration Hub. For more information, see describe-export-tasks.

The beneﬁt of using a Discovery Agent is that it provides more detailed information than using the agentless Discovery Connector. This information includes system performance and resource utilization.

By contrast, the beneﬁt of using a discovery connector is that it provides a more eﬃcient and faster on- premises infrastructure assessment.

To discover resources using an agent

1. In the Migration Hub console navigation pane, under Discover, choose Tools, and then choose Download agent.

2. In the Download agent dropdown list, choose one of the download options.

3. Deploy and conﬁgure the agent by following the instructions in AWS Application Discovery Agent in the AWS Application Discovery Service User Guide.

4. After you have successfully installed the agentless connector, return to the in the Migration Hub console navigation pane, under Discover choose Data Collectors. Then, refresh your internet browser.

5. On the Agents tab, select the agent(s) that you want to start.

6. Choose Start data collection.

To install additional agents, repeat the procedure.

Step 2: View server details and dependencies

The following procedures describe how to view detailed information about servers discovered with AWS discovery tools.

Viewing server details

The following procedure describes how to view information about the servers discovered by using any of the AWS discovery tools.

To view details about a discovered server

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

2. To view details about the server, choose the hostname of the server from the Server info column.

The server's detail page displays information about the server, such as hostname, IP address, performance metrics, and so on.

Exploring server network connections

If you use AWS Application Discovery Agent for discovery, you can explore server network connections by using the network diagram in AWS Migration Hub.

Start exploring by choosing a single server or by choosing multiple servers at the same time. Use the network diagram to explore your discovered servers and their connections to help you decide on how to group them together to assist in your migration planning.

To explore network connections starting with a single server 1. In the navigation pane, under Discover, choose Servers.

(13)

Step 3: Group servers

2. To view details about the server, choose the hostname of the server from the Server info column.

The server's detail page displays information about the server, such as hostname, IP address, performance metrics, and so on.

3. Choose Network. The icon for the server you choose is centered in the network diagram.

Connections fan out from the center server to servers that are directly connected to the server you choose.

4. Choose a server icon to see details about the server. For information about how to work with the network diagram, see Viewing network connections in Migration Hub (p. 30).

To explore network connections starting with multiple servers 1. In the navigation pane, under Discover, choose Servers.

2. To see the network connections for multiple servers, select the check box for each of the servers you want in the network diagram, and then choose Visualize network.

3. You can modify the network diagram for the servers you chose. For information on how to work with the network diagram, see Viewing network connections in Migration Hub (p. 30).

Step 3: Group servers as applications

The following procedures describe how to group servers as applications. Because applications can have multiple servers, it can help simplify migration tracking to group them into logical units.

Grouping servers as applications from the servers list

The following procedure shows you how to select the servers you want to group for your application, how to create your application and name it, and how to add identifying tags.

TipYou can import application groups in bulk using the AWS CLI for Application Discovery Service and calling the CreateApplication API. For more information, see CreateApplication in the Application Discovery Service API Reference.

To group servers into a new or existing application from the servers list 1. In the navigation pane, choose Servers.

2. In the servers list, select the check box for each of the servers that you want to group into a new or existing application.

a. You can also search and ﬁlter on any of the criteria speciﬁed in the headers of the server list.

In the search box choose an item from the dropdown, then choose an operator from the next dropdown, and then type in your criteria.

b. Optionally, for each selected server, you can add a descriptive tag by choosing Add tag from the Actions menu. Doing so shows a dialog box where you can type a value for Key, and optionally a value for Value.

3. To create your application, or add to an existing one, choose Group as application.

4. In the Group as application dialog box, choose either Group as a new application or Add to an existing application.

a. If you chose Group as a new application, type a name in the Application name ﬁeld.

Optionally, you can type a description in the Application description ﬁeld.

b. If you chose Add to an existing application, choose an application from the Choose existing application dropdown menu.

(14)

Migrate and track

5. Choose Group.

Grouping servers as applications from the network diagram

You must select the servers in the network diagram that you want to group into a new or existing application.

The following procedure shows you how to select the servers you want to group for your application from the network diagram, how to create your application and name it, and how to add identifying tags.

To group servers into a new or existing application from the network diagram 1. Set up a network diagram following one of the procedures in the Exploring server network

connections (p. 8) section.

2. You can use the following options to select servers from the network diagram:

• Choose a server node icon. Details about the server show in the server details pane, where you choose Select server.

• Open the context (right-click) menu on the server node icon, and then choose Select server.

• Choose Select all to select all the servers for grouping that are in your diagram. Only the servers with the Discovery Agent running on them can be selected.

• Hold shift to select multiple servers at the same time.

Selected servers are shown in a list in the same pane as the server details. You can toggle back and forth between the server details view and the selected server list view by choosing the server icon.

3. After you select one or more servers, create your application, or add to an existing one, by choosing Group as application.

4. In the Group as application dialog box, choose either Group as a new application or Add to an existing application.

a. If you chose Group as a new application, type a name in the Application name ﬁeld. The servers that are members of the group are labeled on the diagram with the application name.

Optionally, you can type a description for Application description.

b. If you chose Add to an existing application, choose an application from the Choose existing application dropdown menu.

5. Choose Group.

6. Optionally, you can add a descriptive tag to the selected servers by choosing Add tag from the Actions menu. Doing so shows a dialog box where you can type a value for Key, and optionally a value for Value.

Migrate to AWS using Migration Hub migration tools and tracking

You can start migrating with or without ﬁrst using the Migration Hub discovery tools. Directly migrating servers is eﬃcient because your servers are migrating while you simultaneously group them into applications.

Remember that if you haven't selected a Migration Hub home Region, the ﬁrst time you view the console, you'll be required to select one.

(15)

Migrate

It is important to understand that connecting a migration tool to Migration Hub is how you authorize that tool to communicate migration status to Migration Hub in your home Region. Without this authorization, Migration Hub will not track your migration.

As you perform the migration, the servers you are migrating appear in the Servers page. On this page you can logically deﬁne and group all the servers that comprise the applications you are migrating. You can also group more servers into either an existing or a new application at a later time. To get to the Servers page, in the Migration Hub console navigation pane, under Discover, choose Servers.

The following topics guide you through the migration process.

Topics

• Migrate using Migration Hub migration tools (p. 11)

• Track the status of your migrations in Migration Hub (p. 13)

Migrate using Migration Hub migration tools

This section describes how to use the AWS Migration Hub to migrate your on-premises servers and application resources to AWS and how to track the migration.

Topics

• Step 1: Connect migration tools to Migration Hub. (p. 11)

• Step 2: Migrate using the connected migration tools (p. 12)

• Step 3: Group servers as applications (p. 12)

Step 1: Connect migration tools to Migration Hub.

Migration happens outside AWS Migration Hub using AWS migration tools or partner migration tools. To access these tools, in the Migration Hub console navigation pane under Migrate, choose Tools.

The table following lists the supported tools.

Resource type Migration tool

Server AWS Application Migration Service (Application

Migration Service)–AWS Application Migration Service is the primary migration service recommended for lift-and-shift migrations to AWS. For more information about Application Migration Service, see AWS Application Migration Service and Application Migration Service Documentation.

AWS Server Migration Service (AWS SMS)–

For more information about AWS SMS, see AWS Server Migration Service and AWS SMS Documentation.

Warning

As of March 31, 2022, AWS will

discontinue AWS Server Migration Service (AWS SMS). You must complete your active migration projects that are using AWS SMS by March 31, 2022. Going

(16)

Migrate

Resource type Migration tool

forward, we recommend AWS Application Migration Service (Application Migration Service) as the primary migration service for lift-and-shift migrations. For more information, see Using the AWS Migration Hub with Application Migration Service.

Database AWS Database Migration Service (AWS DMS)–

For more information about AWS DMS, see AWS Database Migration Service and AWS DMS Documentation.

The preceding tools communicate directly to Migration Hub giving an aggregated view of their migrated progress and status so they can be tracked through Migration Hub.

The following steps walk you through connecting (authorizing) your selected migration tool.

To connect (authorize) a migration tool

1. In the Migration Hub console navigation pane under Migrate, choose Tools.

2. Decide upon which AWS migration tool or integrated partners' tool to migrate your application.

3. Choose Connect in the box to authorize the migration tool you selected to communicate with Migration Hub.

a. AWS migration tools utilize a one-click authorization process that automatically adds the required AWS Identity and Access Management (IAM) permissions role once you choose Connect.

b. Integrated partners' tools take you to their website when you choose Connect where you will be instructed on how to complete authorization.

Note

Note that if you are using API's or do not want to authorize through Migration Hub's console, you can learn about manual role creation in New User IAM Setup (p. 38).

Step 2: Migrate using the connected migration tools

The following steps walk you through the migration of a previously deﬁned application.

To migrate an application

1. In the Migration Hub console navigation pane under Migrate, choose Tools.

2. If you connected (authorized) an AWS migration tool, choose the console link. If you connected (authorized) an integrated partner's tool, choose the website link.

3. When you have been linked to either the tool's console or website, follow the migration instructions for your selected migration tool as migration happens outside of Migration Hub.

4. After your application's migration has started, return to the Migration Hub console.

Step 3: Group servers as applications

The following steps walk you through the process of grouping servers as applications when directly migrating with a migration tool without performing discovery ﬁrst. (You already did this, if you

(17)

Track

ﬁrst performed discovery as described in Discovering on-premises resources using AWS discovery tools (p. 6) before migrating.)

After the migration tool has started, you'll see the servers listed in Migration Hub from the migration updates sent from the migration tool. You can select the servers and group them as applications. Keep in mind that the server information communicated to Migration Hub from the migration tool is not as detailed as what is collected from a discovery tool.

The following steps show you how to select the server or servers you want to group for your application, how to create your application and name it, and how to add identifying tags.

To group servers into a new or existing application

1. In the Migration Hub console navigation pane, under Discover, choose Servers.

2. In the severs list, select each of the servers that you want to group into a new or existing application.

a. You can also search and ﬁlter on any of the criteria speciﬁed in the headers of the server list.

Click inside the search bar and choose an item from the dropdown, then choose an operator from the next dropdown, and then type in your criteria.

b. Optionally, for each selected server, you can add a descriptive tag by choosing Add tag. A dialog box appears where you can type a value for Key, and optionally, a value for Value.

3. Create your application, or add to an existing one, by choosing Group as application.

4. In the Group as application dialog box, select either Group as a new application or Add to an existing application.

a. If you chose Group as a new application, type a name for Application name. Optionally, you can type a description for Application description.

b. If you chose Add to an existing application, select the radio button next to the application name in the list box.

5. Choose Save. A green conﬁrmation message appears at the top of the screen.

Next steps

After you complete the migration steps, proceed to

• Track the status of your migrations in Migration Hub (p. 13)

Track the status of your migrations in Migration Hub

With a migration underway, you can track its progress status as well as details for each server grouped to the application. This status is communicated to Migration Hub from the migration tool at key points during the migration.

To track an application's migration status

1. After your application's migration has started, return to Migration Hub console and then choose Dashboard in the navigation pane.

2. Under Most recently updated applications, choose the name of your migrating application. Doing this displays the application's detail screen.

• If you do not see all of your application's servers listed in the application's details page, it could be because you have not grouped those servers into this application yet. See Updates About My Migrations Don't Appear Inside an Application (p. 58).

3. The ﬁrst time a migration task is started for a server associated with the application, applications with this status will change to the In progress status, automatically. After verifying the in-progress

(18)

Strategy Recommendations

migration status from the application's detail screen, if the status is still Not started, you can manually change it to In progress. To change the status, choose In progress from the Update status menu.

4. Choose Conﬁrm. A green conﬁrmation message appears at the top of the screen, and the status label changes to In progress.

5. When the data in the application's detail screen indicates migration has completed, and you've performed testing and veriﬁcation, change the status from In progress to Completed from the Update status menu.

6. Choose Conﬁrm. A green conﬁrmation message appears at the top of the screen, and the status label changes to Completed.

For more information about tracking, see Migration Hub tracking, tagging, and console navigation tips (p. 15).

Strategy Recommendations

Migration Hub Strategy Recommendations helps you plan migration and modernization initiatives by oﬀering migration and modernization strategy recommendations for viable transformation paths for your applications. For more information about Strategy Recommendations, see What is Migration Hub Strategy Recommendations?.

Refactor Spaces

AWS Migration Hub Refactor Spaces is the starting point for incremental application refactoring to microservices in AWS. For more information about Refactor Spaces, see What is AWS Migration Hub Refactor Spaces?.

(19)

Tracking migration updates

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.

Topics

• Tracking migration updates (p. 15)

• Tracking metrics using the dashboards (p. 16)

• Tagging migration resources (p. 17)

• Navigating from the dashboard and the navigation pane (p. 17)

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 ﬁve minutes for the initial update to appear in the updates page.

Tracking when you perform discovery ﬁrst 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 ﬁnd 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.

(20)

Tracking when you migrate without performing discovery

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.

a. 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.

b. 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 (p. 12) and Track the status of your migrations in Migration Hub (p. 13).

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 ﬁve minutes and refreshing the page.

If after an initial wait of ﬁve 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 oﬃcially 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 conﬁrmation 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 dashboards

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

(21)

Main dashboard

The main dashboard gathers data from the Discover and Migrate dashboards in a central location.

The main dashboard consists of four at-a-glance status and information panes as well as a consolidated list of links for quick access. These panes 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 diﬀerent states, and to track the migration progress over time.

To reach the main dashboard, choose Dashboard from the navigation pane.

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 oﬀ.

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 ﬁeld from Application Discovery Service. For more information, see the following topics:

• Querying Discovered Conﬁguration Items in the Application Discovery Service User Guide.

• Using Cost Allocation Tags in the AWS Billing and Cost Management User Guide.

Navigating from the dashboard and the navigation pane

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

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

To See Do This Which Is the Same As

All servers From the total number of servers inside the Discovery summary box in the Main dashboard, choose View all servers.

1. In the navigation pane, choose Servers.

All agents From the total number of agents in the Discovery summary box in the Main Dashboard, choose View all agents.

1. In the navigation pane, choose Data Collectors.

2. Choose the Agents tab.

All connectors From the total number of connectors in the Discovery summary box in the Main dashboard, choose View all connectors.

1. In the navigation pane, choose Data Collectors.

2. Choose the Connectors tab.

(22)

Navigating from the dashboard and the navigation pane

To See Do This Which Is the Same As

All applications From either the Main dashboard or Migrate dashboard, in the Most recently updated applications pane, choose View all applications

Or, from the Discover dashboard in the Servers & Applications pane, choose View all applications.

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

2. Choose Applications.

Application details...

• migration status

• server list

From either the Main dashboard or Migrate dashboard in the Most recently updated applications box, choose the application's status box.

1. In the navigation pane, choose Migrate.

2. Choose Applications.

3. In the Application Name column, choose the application name.

Server details...

• basic information

• performance information

From either the Main dashboard or Migrate dashboard, in the Most recently updated applications pane, choose the application. Then choose the server name in the Server ID column.

1. In the navigation pane, choose Servers.

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

(23)

Choose a Migration Hub home Region

The AWS Migration Hub home Region

Your AWS Migration Hub data is stored in your home Region for purposes of discovery, planning, and migration tracking. The status of migrations for your entire portfolio appears in your selected home Region.

You can specify a home Region from the Migration Hub Settings page or from the Migration Hub Home Region API Reference. For information about changing the Migration Hub home Region after it is set, see Changing your Migration Hub home Region (p. 20).

Choose a Migration Hub home Region

On your ﬁrst use of the AWS Migration Hub console, select a Migration Hub home Region. If you haven’t selected a home Region, you’ll be prompted to make a selection before you can perform any write action from the console, SDK, or CLI. After you select a home Region, you are redirected automatically to the console in that AWS Region.

You can choose and view your current home Region on the AWS Migration Hub Settings page. To navigate to the Settings page, choose Settings from the left navigation.

For a list of the available AWS Migration Hub home Regions, see AWS Migration Hub endpoints in the AWS General Reference.

The Migration Hub console in your home Region gives you detailed visibility into discovery and migration, regardless of whether you are moving applications into one AWS Region or ten. From your Migration Hub home Region, you can track your migration into any AWS Region.

All of the discovery and migration tracking data sent from AWS tools or partner migration tools is stored and processed in your home Region, regardless of the migrating application’s target Region.

For example, you can select US West (Oregon) as your AWS Migration Hub home Region, then perform discovery of your datacenters, and analyze and identify your applications. Then if you use AWS

Application Migration Service (Application Migration Service) to migrate into the Oregon and Frankfurt AWS Regions, you can track your Application Migration Service migrations at the application level in Migration Hub. Throughout each step in this example, your migration team uses Migration Hub in one AWS Region only: the home Region you selected, which is the US West (Oregon) Region.

Set a home Region for discovery

To start discovery and planning, you can deploy data collectors, such as AWS Application Discovery Agent or AWS Agentless Discovery Connector, into your data centers. These tools send data to the AWS Migration Hub service in your home Region, and the information is displayed on your home Region console.

Before you install your data collectors, your home Region must be set. Before collecting data, you must register your collectors in your home Region. If you're using the AWS CLI, you must set up your AWS CLI to use the home Region as the default Region. Instructions for how to set your home Region in the AWS CLI are provided in the AWS CLI sections of this guide.

(24)

Set a home Region for migration reporting

AWS Application Discovery Agent discovers data for many types of hardware, hypervisors, and operating systems including Linux and Windows. An agent must be installed on each host that is targeted for migration. For speciﬁc information about the data ﬁelds that are returned by AWS Application Discovery Agent, see the AWS Application Discovery Agent user guide.

AWS Agentless Discovery Connector discovers data for VMWare vCenter hosts and systems, using VMWare metadata. For speciﬁc information about the data ﬁelds that are returned by AWS Agentless Discovery Connector, see the AWS Agentless Discovery Connector user guide

Alternatively, you can import a .csv ﬁle by means of the AWS Migration Hub Import capability.

Set a home Region for migration reporting

When you’re ready to migrate, use the migration tools that best ﬁt your needs. Options include AWS Application Migration Service (Application Migration Service), AWS Database Migration Service (AWS DMS), or one of many third-party tools. Migrate your servers and applications into any AWS Region, and the migration progress reported by each tool is stored in your home Region. Stored data provides a single discovery and migration planning repository for your entire portfolio, and a single view of your migrations in multiple AWS Regions.

Authorize your migration tools, such as Application Migration Service, to read discovery data from and send migration status to Migration Hub in your home Region. The migration tools read application groupings and send basic identifying information for each resource. For example, the hostname, IP address, MAC address, and VMware or hypervisor identiﬁers are sent, along with the resource’s migration status, from the migration’s destination Region to the Migration Hub home Region.

Changing your Migration Hub home Region

After it is set, the Migration Hub home Region can only be changed by contacting AWS Support. If you change the Migration Hub home Region, data collected in the old home Region doesn't migrate to the new home Region. You'll need to recollect the data in the new home Region.

Working with the Migration Hub home Region APIs

You can call the AWS Migration Hub, AWS Application Discovery Service, and AWS Migration Hub home Region APIs from within your home Region only. API calls for write actions (create, notify, associate, disassociate, import, or put) originating from outside your home Region are rejected, except for the ability to register your agents and connectors. API calls for read actions (list, describe, stop, and delete) are permitted outside of your home Region.

NoteYou can register agents and collectors outside your home Region. However, the

StartDataCollection API call in AWS Application Discovery Service prevents you from enabling data collection from outside the home Region.

The AWS Migration Hub home Region APIs are available speciﬁcally for working with your Migration Hub home Region. A general description of each API is provided next. For speciﬁc API usage, see the AWS Migration Hub Home Region API reference.

CreateHomeRegionControl

This API sets up the home Region. It applies to the calling account only.

(25)

Working with the Migration Hub home Region APIs

GetHomeRegion

Returns the calling account’s home Region, if conﬁgured. This API is used by other AWS services to determine the regional endpoint for calling AWS Application Discovery Service and Migration Hub.

You must call GetHomeRegion at least once before you call any other Application Discovery Service and Migration Hub APIs, to obtain the account's Migration Hub home Region.

DescribeHomeRegionControls

This API permits ﬁltering on the ControlId, HomeRegion, and RegionControlScope ﬁelds.

(26)

Prerequisites

Amazon EC2 instance recommendations

Amazon EC2 instance recommendations provide you with the ability to estimate the cost of running your existing servers in AWS. This feature analyzes the details about each server, including server speciﬁcation, CPU, and memory utilization data. The compiled data is then used to recommend the least expensive Amazon EC2 instance type that can handle the existing performance workload.

Recommendations are returned along with per-hour instance pricing.

Based on your business needs, you can choose additional preferences such as billing options, region, Amazon EC2 instance type exclusions and the CPU/RAM sizing (average, peak, percentile) to further optimize your Amazon EC2 instance recommendations and associated costs.

Topics

• Prerequisites (p. 22)

• How Amazon EC2 instance recommendations work (p. 22)

• Generating Amazon EC2 recommendations (p. 23)

• Understanding your Amazon EC2 recommendations (p. 24)

• Additional considerations (p. 28)

Prerequisites

Before you can get Amazon EC2 instance recommendations, you must have data about your on-premises servers in Migration Hub. This data can come from the discovery tools (Discovery Connector or Discovery Agent) or from Migration Hub import. For more information on using these tools and features, see the following links:

• Migration Hub import – This allows you to import details of your on-premises environment directly into Migration Hub using a predeﬁned CSV template.

• Discovery Connector – This is a VMware appliance that can collect information only about VMware virtual machines (VMs).

• Discovery Agent – This is AWS software that you install on on-premises servers and VMs targeted for discovery and migration.

NotePercentile-based recommendations are only generated for servers with data collected by a Discovery Connector from March 12th, 2019 onwards, or by a Discovery Agent.

How Amazon EC2 instance recommendations work

This feature recommends the most cost-effective Amazon Elastic Compute Cloud instance type that can satisfy your existing server specifications and utilization requirements while taking into account your selected instance preferences. The server specifications that are used to generate your recommendations are:

• Number of processors

• Number of logical cores

• Total amount of RAM

(27)

Generating Amazon EC2 recommendations

• Operating system family

• Usage data including peak, average, and percentiles of CPU and RAM

Amazon EC2 instance recommendations returns the best Amazon EC2 instance type match based on server speciﬁcation as well as the performance dimensions you provided. To match the performance dimensions, the service adjusts the server’s speciﬁcation by multiplying the original CPU and RAM values by the usage percentage.

Generating Amazon EC2 recommendations

In the Export Amazon EC2 instance recommendations page of the Migration Hub console, you'll choose your recommendation preferences. These preferences include resource sizing, instance type preferences, and instance type exclusions. Use the following procedure to generate your Amazon EC2 instance recommendations.

To generate Amazon EC2 instance recommendations

1. Open a browser and sign into the Migration Hub console at https://console.aws.amazon.com/

migrationhub.

2. In the navigation pane, under Assess, choose Amazon EC2 instance recommendations.

3. Choose your Amazon EC2 instance sizing preference for your discovered servers. You can choose one of the following options.

• Maximum utilization – This option sizes your instance recommendations based oﬀ of the maximum (peak) CPU and RAM utilization data that was collected by the discovery tools.

• Current server speciﬁcation – You have the two options of Direct match or Custom match.

• Custom match – Scales the CPU and RAM speciﬁcations for your instances relative to the collected speciﬁcation data. For example setting CPU to 50% and RAM to 60% will generate recommendations that assume 50% utilization of your discovered CPU usage and 60%

utilization of your total RAM usage.

• Direct match – Matches the recommendations based oﬀ of the exact CPU and RAM speciﬁcation data collected by the discovery tools you used to get the data into Migration Hub.

• Average utilization – This option sizes your instance recommendations based oﬀ of the average CPU and RAM utilization data that was imported or collected by the discovery tools.

• Percentile of utilization – If you used an AWS Application Discovery Agent or an AWS Agentless Discovery Connector to collect your server data, you can generate your recommendations using percentiles of time-series utilization data. Percentile-based recommendations are only generated for servers with data collected by a Discovery Connector from March 12th, 2019 onwards, or by a Discovery Agent.

For all the data points collected for CPU and RAM utilization, a percentile is a value that exists below a given percentage of utilization since data has been discovered. For example, the 75th percentile represents the value under 75 percent of all the RAM and CPU utilization data that has been discovered.

4. Choose your Amazon EC2 instance type preferences, including AWS Region, tenancy, and pricing model.

• Region – Your AWS Region selection aﬀects Amazon EC2 instance availability and pricing.

• Tenancy – This deﬁnes how EC2 instances are distributed across physical hardware and aﬀects pricing.

• Shared – Multiple customers may share the same physical hardware.

• Dedicated – Only your instances will run on the same physical hardware.

(28)

Understanding your Amazon EC2 recommendations

• Pricing Model – This deﬁnes the kind of billing and commitment you intend to use for your instances.

• On-Demand – Requires no long-term commitment.

• Reserved – requires 1-3 year commitment and provides discounts and additional conﬁdence in your ability to launch instances when needed. For more information on reserved instance pricing model information, see Reserved Instances in the Amazon EC2 User Guide for Linux Instances

5. Optionally, choose any Amazon EC2 instance type exclusions to prevent speciﬁc types of instances from appearing in your recommendations.

6. When you're done setting your preferences, choose Export recommendations. This will begin generating your recommendations.

When the process is complete, your browser will automatically download a compressed archive (ZIP) file, containing a comma-separated values (CSV) file with your recommendations. The file is named EC2InstanceRecommendations-sizing-preferences-year-month-day-hour-minute.csv.

Large datasets can take a few minutes to generate recommendations. You can generate new recommendations at any time by repeating this procedure with a diﬀerent set of preferences.

Understanding your Amazon EC2 recommendations

The downloaded CSV ﬁle has the following categories of information within it:

• Server identification – This information identifies each server. Each row of the CSV file contains information specific to a single server identified by a ServerID, HostName, and/or ExternalId.

• Requested recommendations – These are your generated results based on your CPU/RAM sizing preferences.

• User preferences – These are the preferences that were speciﬁed while requesting recommendations.

This information can be used to track and compare diﬀerent results from generating multiple recommendations for the same set of servers.

• Server conﬁguration – This information deﬁnes the set of on-premises servers that were used to generate your recommendations.

The following table defines the different columns for an Amazon EC2 recommendations CSV file.

Import Field Name Description Examples

ServerId A unique ID created by AWS and applied

to a server after it's been discovered. d-server-00qag3caex2sjm d-server-01op2h5rnypwjy Server.ExternalId A custom identiﬁer that allows you to

mark each record as unique. For example, ExternalId can be the inventory ID for the server in your data center.

Inventory Id 1 Server 2 CMBD Id 3 Server.HostName The host name of the server. We

recommend using the fully qualiﬁed domain name (FQDN) for this value.

ip-1-2-3-4 localhost.domain

(29)

Server.VMware.VMName The name of the virtual machine. Corp1 Recommendation.EC2.

Remarks Error messages and other important

information about a speciﬁc server's Amazon EC2 instance recommendation.

Server.OS.Name wasn't recognized. "Linux" was used as the default operating system for this instance recommendation.

Server.OS.Name The name of the operating system. Linux Windows.Hat Server.OS.Version The version of the operating system. 16.04.3

NT 6.2.8 Server.CPU.

NumberOfProcessors For bare hardware servers discovered by an agent, this is the number of Physical CPUs. For data collected by agents running in virtualized environments, this can be the number of vCPUs allocated.

However this varies depending on the virtualization platform.

4

Server.CPU.NumberOfCores For bare hardware servers discovered by an agent, this is the total number of physical cores for all processors. For data collected by agents in virtualized environments, this varies depending on the virtualization platform.

8

Server.CPU.

NumberOfLogicalCores The total number of threads that can run concurrently on all CPUs in a server.

Some CPUs support multiple threads to run concurrently on a single CPU core. In those cases, this number will be larger than the number of physical (or virtual) cores.

16

Recommendation.EC2.

RequestedCPU.UsagePct The percent of

Server.CPU.NumberOfCores used to create the recommendation.

0.9

Recommendation.EC2.

RequestedvCPU The

Server.CPU.NumberOfLogicalCores value multiplied by the

Recommendation.EC2.

RequestedCPUPercentUse value, rounded up to the next integer.

16

Server.RAM.TotalSizeInMB The total RAM, in MB, available on the

server. 64

128

(30)

Recommendation.EC2.

RequestedRAM.UsagePct The percent of the RAM usage for a discovered server. This is used if you chose Current server speciﬁcation with a Custom match when you chose your sizing preferences.

0.8

Recommendation.EC2.

RequestedRAMinMB The Server.RAM.TotalSizeInMB value multiplied by the

Recommendation.EC2.

RequestedRAMPercentUse value.

800

Recommendation.

EC2.Instance.Model The recommended Amazon EC2 instance

model. c5.18xlarge

Recommendation.EC2.

Instance.vCPUCount The number of vCPUs in the

recommended Amazon EC2 instance model.

12

Recommendation.EC2.

Instance.RAM.TotalSizeinMB The amount of memory for the recommended Amazon EC2 instance model.

1000

Recommendation.EC2.

Instance.Price.UpfrontCost This is the upfront cost to reserve the

instance, in US dollars. 1343.50

Recommendation.EC2.

Instance.Price.HourlyRate The hourly rate for the instance, in US

dollars. 1.32

Recommendation.EC2.

Instance.Price.

AmoritzedHourlyRate

The hourly price based on the instance type preferences you chose, in US dollars. For long term contracts this value includes the upfront cost plus the hourly cost averaged over the contract.

For all upfront pricing, this value is zero.

2.12

Recommendation.EC2.

Instance.Price.

EﬀectiveDate.UTC

The eﬀective date for an hourly instance

price, recorded in the UTC time zone. 2019-04-23 14:23:00

Recommendation.EC2.

Instance.OSType The operating system used to create the recommendation and pricing. Currently only Linux, Windows, RHEL, and SLES are supported.

Red Hat Enterprise Linux

UserPreference.

Recommendation.CPUSizing The CPU preference you chose for CPU/

RAM sizing on the sizing preferences. Custom Match - 50% of CPU Spec

UserPreference.

Recommendation.RAMSizing The RAM preference you chose for CPU/

RAM sizing on the preferences. Custom Match - 70% of RAM Spec

UserPreference.Region The region you selected for the price and availability of Amazon EC2 recommendations.

US West (Oregon)

UserPreference.EC2.Tenancy Tenancy used to determine instance type

and instance price per hour. Shared

(31)

UserPreference.EC2.

PricingModel Pricing model to determine the instance price per model. This value can be either On Demand or Reserved.

On Demand

UserPreference.EC2.

PricingModel.ContractTerm Contract term to determine instance

price per hour. 3-year Standard

"ONE_YEAR"|"THREE_YEAR"

UserPreference.EC2.

PricingModel.Payment Payment model to determine instance

price per hour. "ALL_UPFRONT"|

"PARTIAL_UPFRONT"|

"NO_UPFRONT"

UserPreference.EC2.

ExcludedInstances The instances that you chose to exclude

from your recommendations. t2.large, m4 family Applications A comma-delimited list of applications

that include this server, in quotes. This value can include existing applications and/or new applications that are created upon import.

Application1

"Application2, Application3"

Tags A comma-delimited list of tags

formatted as name:value. "zone:1, critical:yes"

"zone:3, critical:no, zone:1"

Server.SMBiosId System management BIOS (SMBIOS) ID.

Server.VMware.MoRefId The managed object reference ID. Must be provided with a VMware.VCenterId.

Server.VMware.VCenterId Virtual machine unique identiﬁer. Must be provided with a VMware.MoRefId.

Server.VMware.vCenterName The name of the Center where the VM is

managed.

Server.VMware.vmFolderPath The directory path of the VM ﬁles.

Server.CPU.UsagePct.Avg The average CPU utilization when the

discovery tool was collecting data. 45 23.9 Server.CPU.UsagePct.Max The maximum CPU utilization when the

discovery tool was collecting data. 55.34 24 Server.RAM.UsedSizeInMB.Avg The average amount of RAM used in the

given server, in MB.

Server.RAM.UsedSizeInMB.Max The maximum amount of RAM used in

the given server, in MB.

Server.RAM.UsagePct.Avg The average RAM utilization when the discovery tool was collecting data.

Server.RAM.UsagePct.Max The maximum RAM utilization when the discovery tool was collecting data.

Server.NumberOfDisks The number of physical hard disks on a

host.

AWS Migration Hub

AWS Migration Hub

User Guide

AWS Migration Hub: User Guide

Table of Contents

What Is AWS Migration Hub?

Are you a ﬁrst-time user of AWS Migration Hub?

Setting up

Sign up for AWS

Create an IAM user

Getting started with AWS Migration Hub

Assumptions

Access to AWS Migration Hub

Discovering on-premises resources using AWS discovery tools

Step 1: Choose and deploy AWS discovery tools

Discovery using the AWS Agentless Discovery Connector

Discovery using the AWS Application Discovery Agent

Step 2: View server details and dependencies

Viewing server details

Exploring server network connections

Step 3: Group servers as applications

Grouping servers as applications from the servers list

Grouping servers as applications from the network diagram

Migrate to AWS using Migration Hub migration tools and tracking

Migrate using Migration Hub migration tools

Step 1: Connect migration tools to Migration Hub.

Step 2: Migrate using the connected migration tools

Step 3: Group servers as applications

Track the status of your migrations in Migration Hub

Strategy Recommendations

Refactor Spaces

Migration Hub tracking, tagging, and console navigation tips

Tracking migration updates

Tracking when you perform discovery ﬁrst and then migrate

Tracking when you migrate without performing discovery

Troubleshooting and manually mapping migration updates

Tracking metrics using the dashboards

Main dashboard

Tagging migration resources

Navigating from the dashboard and the navigation pane

The AWS Migration Hub home Region

Choose a Migration Hub home Region

Set a home Region for discovery

Set a home Region for migration reporting

Changing your Migration Hub home Region

Working with the Migration Hub home Region APIs

Amazon EC2 instance recommendations

Prerequisites

How Amazon EC2 instance recommendations work

Generating Amazon EC2 recommendations

Understanding your Amazon EC2 recommendations