AWS Migration Hub is no longer open to new customers as of November 7, 2025. For capabilities similar to AWS Migration Hub, explore [AWS Transform](https://aws.amazon.com/transform). # Migration Hub Journeys tasks and subtasks Tasks and subtasks A migration journey consists of phases. Phases consist of modules, which in turn consist of tasks and subtasks. For information about phases, see [Phases](phases.md). For information about modules, see [Modules](modules.md). For information about how to attach files to a task or a subtask, see [Attached files](attached-files.md). **Topics** + [ # Viewing Migration Hub Journeys tasks ](viewing-tasks.md) + [ # Reordering Migration Hub Journeys tasks ](reordering-tasks.md) + [ # Updating Migration Hub Journeys tasks ](updating-tasks.md) + [ # Migration Hub Journeys task automation ](task-automation.md) + [ # Adding subtasks ](creating-subtask.md) # Viewing Migration Hub Journeys tasks Viewing tasks **To view the tasks in a migration journey** 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey whose tasks you want to view. 1. Choose the **Tasks** tab. # Reordering Migration Hub Journeys tasks Reordering tasks **To reorder a task or change its status** You can change the order in which you want to perform a task relative to other tasks in the same module. The status of a task can be one of the following: **Planned**, **In progress**, **Completed**, or **Out of scope**. 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that contains the task. 1. Choose the **Tasks** tab. 1. Drag the task that you want to move and drop it at a different position relative to other tasks in the same status column or in a different column if you want to change its status. Every time you move a task, Migration Hub Journeys automatically saves that change. # Updating Migration Hub Journeys tasks Updating tasks **To edit the details of a task** The details of a task include its title, status, due date, estimated effort, effort spent, and assignee. Only members of the task's journey appear in the list of assignees. For information about membership, see [Individuals and teams](individuals-and-teams.md). 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that contains the task. 1. Choose the **Tasks** tab. 1. Choose the tile that represents the task whose details you want to edit. A right pane appears and shows the properties of the task, some of which are editable in that pane. To edit the rest of the properties of the task, choose the external link icon that appears in the top-right corner of this task details pane. # Migration Hub Journeys task automation Task automation **Note** The task-automation feature is in preview release. It is available in US East (N. Virginia). This is pre-release documentation. Both the task-automation feature and this documentation are subject to change. A task can have one of two execution types: `Manual` or `Automated`. The default execution type is `Manual`. When you execute an automated task, it runs a Migration Hub automation unit. For information about automation units, see [AWS Migration Hub Automation](https://docs.aws.amazon.com/migrationhub/latest/ug/mha.html). The following topics describe how to create an IAM role that you can use to automate tasks, how to set the execution type of a task to `Automated`, and how to execute an automated task. **Topics** + [ # IAM roles for Migration Hub Journeys task automation ](task-automation-role.md) + [ # Automating a manual Migration Hub Journeys task ](automate-task.md) + [ # Executing an automated Migration Hub Journeys task ](execute-autmated-task.md) # IAM roles for Migration Hub Journeys task automation IAM roles **Note** The task-automation feature is in preview release. It is available in US East (N. Virginia). This is pre-release documentation. Both the task-automation feature and this documentation are subject to change. Automated Migration Hub Journeys tasks require an account connection with an associated IAM role that has the following trust policy and permissions policy. For information about how to create an IAM role with these two policies, see [Create a role using custom trust policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-custom.html). For information about how to associate an IAM role with an account connection, see [Associating IAM roles with an AWS account connection in AWS Migration Hub Journeys](associate-roles.md). ## Trust policy The following trust policy allows Migration Hub Journeys to assume the role. To use this trust policy, replace *account-connection-ARN* with the ARN of a connection whose status is `Connected`. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "journeys.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "ArnLike": { "aws:SourceArn": "arn:aws:mgh:us-east-1:111122223333:connection/connection-id" } } }, { "Effect": "Allow", "Principal": { "Service": "journeys.amazonaws.com" }, "Action": "sts:TagSession" } ] } ``` ------ To set a condition based on an AWS account ID instead of on a connection ARN, you can use the following trust policy. However, keep in mind that this policy is more permissive than the policy with a condition based on connection ARN. The reason this trust policy is more permissive is that members of other migration journeys that have connections to the same AWS account can use it to run automation. Therefore, we recommend that you use the previous policy and set the condition based on a specific connection, instead of on an AWS account. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [{ "Effect": "Allow", "Principal": { "Service": "journeys.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "StringLike": { "aws:SourceAccount": "111122223333" } } }, { "Effect": "Allow", "Principal": { "Service": "journeys.amazonaws.com" }, "Action": "sts:TagSession" } ] } ``` ------ **Warning** Migration Hub Journeys no longer supports associating new IAM roles that have the following trust policy. If you already have a connection with an associated role that has the following trust policy, you can continue to use that role to execute automated tasks until January 31, 2025. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "journeys.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "ArnLike": { "aws:SourceArn": "arn:aws:mgh:us-east-1:111122223333:connection/connection-id" } } }, { "Effect": "Allow", "Principal": { "Service": "journeys.amazonaws.com" }, "Action": "sts:TagSession" } ] } ``` ------ ## Permissions policy The following permissions policy grants access to describe and run AWS Migration Hub automation units. ------ #### [ JSON ] **** ``` { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "mgn:ListApplications", "mgn:ListWaves", "mgn:ListConnectors", "mgh:ListCreatedArtifacts", "mgh:ListAutomationUnits", "mgh:ListMigrationTaskUpdates", "mgh:DescribeAutomationUnit", "mgh:CreateAutomationRun", "mgh:DescribeAutomationRun", "secretsmanager:ListSecrets" ], "Resource": "*" } ] } ``` ------ # Automating a manual Migration Hub Journeys task Automating a manual task **Note** The task-automation feature is in preview release. It is available in US East (N. Virginia). This is pre-release documentation. Both the task-automation feature and this documentation are subject to change. To automate a task, first ensure that you have the following two prerequisites. ## Prerequisites + Ensure that you have an AWS account connection. For information about account connections and how to create them, see [AWS account connections in AWS Migration Hub Journeys](account-connections.md). + Associate with the account connection an IAM role with the permissions described in [IAM roles for Migration Hub Journeys task automation](task-automation-role.md). ## To automate a task 1. Perform the steps described in [Updating Migration Hub Journeys tasks](updating-tasks.md) 1. In the **Task details** section, choose **Edit**. 1. For **Task type** choose **Automated**. 1. Choose **Browse automation unit**. 1. Select an account connection with which you have associated the IAM role described in [Prerequisites](#automation-prereqs). 1. Select the IAM role described in [Prerequisites](#automation-prereqs). 1. Select the automation unit that you want the task to run when you execute the task. 1. Choose **Select**. 1. Choose **Save changes**. # Executing an automated Migration Hub Journeys task Executing an automated task **Note** The task-automation feature is in preview release. It is available in US East (N. Virginia). This is pre-release documentation. Both the task-automation feature and this documentation are subject to change. This topic explains how to execute an automated task. For information about how to automate a task whose type is `Manual`, see [Automating a manual Migration Hub Journeys task](automate-task.md). **To execute an automated task** 1. Perform the steps described in [Updating Migration Hub Journeys tasks](updating-tasks.md) 1. Choose **Execute task**. 1. (Optional) Enter a name that can help identify this execution. 1. Choose a connection from the list of AWS account connections. For information about how to create a connection, see [AWS account connections in AWS Migration Hub Journeys](account-connections.md). 1. Choose the IAM role that you want to use to execute the task. 1. Choose **Execute task**. # Adding subtasks **To add a subtask to a task** A task can contain steps and subtasks. Subtasks can only contain steps. 1. Open the Migration Hub Journeys console. For information about how to access the console, see [Accessing AWS Migration Hub Journeys](setup.md). 1. In the left navigation pane, choose **Migration journeys**. 1. In the list of migration journeys, choose the name of the journey that contains the task. 1. Choose the **Tasks** tab. 1. Choose the tile that represents the task where you want to add a subtask. A right pane appears and shows the task details. 1. Choose the external link icon that appears in the top-right corner of this task-details pane. 1. In the **Subtasks** tab at the bottom of the page, choose **Create subtask**. 1. In the **Subtask settings** section, enter a title for the task. You can optionally specify a due date and the estimated effort and assign the subtask to a member of the journey. 1. You can also optionally add tools, acceptance criteria, and dependency tasks. 1. Choose **Create subtask**.