Migration workflows
Migration workflows are created using templates. The predefined templates provided by Migration Hub Orchestrator
offer automation capabilities and facilitate the migration of your on-premises servers and
applications to AWS. A template consists of one or more step groups that contain at least one
step each. You can create a migration workflow with one of the predefined templates, or with a
custom template that you can create.
Each template will have different prerequisites and configuration options. You should refer
to the documentation for the template that you intend to use before creating a migration workflow.
Once you create a migration workflow, you can perform various actions to customize it for your use
case. For more information, see Templates.
Considerations and limitations
The following are considerations and limitations when working with migration workflows:
-
You can make modifications to a migration workflow after it's created.
-
You can only make modifications to step groups and steps that you have added to a
migration workflow.
-
A step must be placed within a step group. You can choose to add a step to an existing
step group or create a new step group.
-
A step group must have at least one step.
-
A step can't be added to a step group with a status of
Completed.
-
To delete an ongoing migration workflow, you must pause it first.
Creating step groups
You can add step groups using the Migration Hub Orchestrator console or the AWS CLI. Each step group must contain
a step.
- Console
-
To add step groups using the Migration Hub Orchestrator console
-
Sign in to the AWS Management Console and access the Migration Hub Orchestrator console at https://console.aws.amazon.com/migrationhub/orchestrator/.
-
In the left navigation pane, under Orchestrate, choose
Workflows.
-
On the Workflows page, select the workflow and choose
View details.
-
Under Steps, select an existing step group.
-
Choose Add, Add step group above or
Add step group below.
-
For Step group name, enter a name.
-
(Optional) for Step Group description, enter a
description.
-
For Name, enter a name for the step.
-
(Optional) For Description, enter a description for the
step.
-
(Optional) For Script location, choose Amazon S3
URI or Upload a file.
-
If you chose Amazon S3 URI, provide the following details:
-
For Script run command, enter a command to run the
script.
-
For Script run environment, choose On
premises or AWS.
-
If you chose On premises, for Server,
choose a server from the dropdown menu. The resources listed are based on what you
configured in AWS Application Discovery Service. For more information, refer to the documentation on the
template your workflow was created from in the Templates
section.
-
If you chose AWS, for EC2 instance,
select the instances to run the script on.
-
If you chose Upload a file, provide the following
details:
-
For Script file, choose Choose file
and select a shell or PowerShell script file to use.
-
For Script run command, enter a command to run the
script.
-
For Script run environment, choose On premises or
AWS. The servers listed are the application servers that you
configured in AWS Application Discovery Service. For more information, refer to the documentation on the
template your workflow was created from in the Templates
section.
-
If you chose On premises, for
Server, choose a server from the dropdown menu. The resources
listed are based on what you configured in AWS Application Discovery Service. For more information,
refer to the documentation on the template your workflow was created from in the
Templates
section.
-
If you chose AWS, for EC2
instance, select the instances to run the script on.
If you don’t make a selection for Script location, the step’s type will be set to Manual which requires user intervention.
After completing the manual procedure for the step, you must update the status to complete for the migration workflow to continue.
- AWS CLI
-
You can use the CreateWorkflowStepGroup API operation to add step groups to a
workflow.
Creating steps in an existing step group
You can add steps using the Migration Hub Orchestrator console or the AWS CLI.
- Console
-
To add steps using the Migration Hub Orchestrator console
-
Sign in to the AWS Management Console and access the Migration Hub Orchestrator console at https://console.aws.amazon.com/migrationhub/orchestrator/.
-
In the left navigation pane, under Orchestrate, choose
Workflows.
-
On the Workflows page, select the workflow that you want to
customize and choose View details.
-
Select the step group in which you want to add steps.
-
Under Steps, select Add, Add step
to group.
-
For Name, enter a name for the step.
-
(Optional) For Description, enter a description for the
step.
-
(Optional) For Script location, choose Amazon S3
URI or Upload a file.
-
If you chose Amazon S3 URI, provide the following details:
-
For Script run command, enter a command to run the
script.
-
For Script run environment, choose On
premises or AWS.
-
If you chose On premises, for Server,
choose a server from the dropdown menu. The resources listed are based on what you
configured in AWS Application Discovery Service. For more information, refer to the documentation on the
template your workflow was created from in the Templates
section.
-
If you chose AWS, for EC2 instance,
select the instances to run the script on.
-
If you chose Upload a file, provide the following
details:
-
For Script file, choose Choose file and
select a shell or PowerShell script file to use.
-
For Script run command, enter a command to run the
script.
-
For Script run environment, choose On premises or
AWS. The servers listed are the application servers that you
configured in AWS Application Discovery Service. For more information, refer to the documentation on the
template your workflow was created from in the Templates
section.
-
If you chose On premises, for Server,
choose a server from the dropdown menu. The resources listed are based on what you
configured in AWS Application Discovery Service. For more information, refer to the documentation on the
template your workflow was created from in the Templates
section.
-
If you chose AWS, for EC2 instance,
select the instances to run the script on.
If you don’t make a selection for Script location, the step’s type will be set to Manual which requires user intervention.
After completing the manual procedure for the step, you must update the status to complete for the migration workflow to continue.
- AWS CLI
-
You can use the CreateWorkflowStep API operation to add steps to a step
group.
Updating step groups
You can update step groups using the Migration Hub Orchestrator console or the AWS CLI.
- Console
-
To update step groups
-
Sign in to the AWS Management Console and access the Migration Hub Orchestrator console at https://console.aws.amazon.com/migrationhub/orchestrator/.
-
In the left navigation pane, under Orchestrate, choose
Workflows.
-
On the Workflows page, select the workflow that you want to
customize and choose View details.
-
If you need to update the order of step groups in the workflow:
-
In the Steps pane, select an existing step group.
-
Choose Move up or Move down to reorder the
step groups as needed.
-
If you need to update information about a step group:
-
In the Steps pane, select an existing step group, then choose
Actions, Edit step group.
-
Update the Step group name and Step group
description as required.
-
Choose Save.
- AWS CLI
-
You can use the UpdateWorkflowStepGroup API operation to update the step groups
in a workflow.
You can only update step groups that you have added to a migration workflow that isn't
running or paused.
Updating steps
You can update steps using the Migration Hub Orchestrator console or the AWS CLI.
- Console
-
To update steps
-
Sign in to the AWS Management Console and access the Migration Hub Orchestrator console at https://console.aws.amazon.com/migrationhub/orchestrator/.
-
In the left navigation pane, under Orchestrate, choose
Workflows.
-
On the Workflows page, select the workflow that you want to
customize and choose View details.
-
In the Steps pane, select the step group in which you need to
update.
-
Choose Expand all to view the steps within the step group.
-
If you need to update the order of step groups in the workflow:
-
In the Steps pane, select the step you need to move within the
step group.
-
Choose Move up or Move down to reorder the
step as needed.
-
If you need to update information about a step group:
-
In the Steps pane, select an existing step group, then choose
Actions, Edit step.
-
Update the Step name and Step group
description, and Script location configuration as
required.
-
Choose Save.
- AWS CLI
-
You can use the UpdateWorkflowStep API operation to update the steps in a step
group.
You can only update steps that you have added to a migration workflow that isn't running or
paused.
Deleting step groups
You can delete step groups using the Migration Hub Orchestrator console or the AWS CLI.
- Console
-
You can only delete step groups when the following conditions are met:
-
The workflow has a Status of Not started or
Paused.
-
The step group has a Status of Awaiting
dependencies.
-
The step group has a Managed by value of
Custom.
To delete step groups
-
Sign in to the AWS Management Console and access the Migration Hub Orchestrator console at https://console.aws.amazon.com/migrationhub/orchestrator/.
-
In the left navigation pane, under Orchestrate, choose
Workflows.
-
On the Workflows page, select the workflow that you want to
customize and choose View details.
-
In the Steps pane, select the step group to delete.
-
Choose Actions, Delete step group.
-
Enter delete
and choose Delete to
proceed.
- AWS CLI
-
You can use the DeleteWorkflowStepGroup API operation to delete step groups in a
workflow.
Deleting steps
You can delete steps using the Migration Hub Orchestrator console or the AWS CLI.
- Console
-
You can only delete steps when the following conditions are met:
-
The workflow has a Status of Not started or
Paused.
-
The step has a Status of Awaiting
dependencies.
-
The step has a Managed by value of
Custom.
To delete steps
-
Sign in to the AWS Management Console and access the Migration Hub Orchestrator console at https://console.aws.amazon.com/migrationhub/orchestrator/.
-
In the left navigation pane, under Orchestrate, choose
Workflows.
-
On the Workflows page, select the workflow that you want to
customize and choose View details.
-
In the Steps pane, select the step group that contains the step to
delete.
-
Choose Expand all to view the steps within the step group.
-
Select the step to delete.
-
Choose Actions, Delete step.
-
Enter delete
and choose Delete to
proceed.
- AWS CLI
-
You can use the DeleteWorkflowStep API operation to delete steps in a step
group.
Running workflows
For guidance on running a migration workflow, refer to the documentation for the template
that was used. For more information on the available templates, see Templates.
Pausing workflows
You can pause a running migration workflow using the Migration Hub Orchestrator console or the AWS CLI. You can
only pause a running workflow.
- Console
-
- AWS CLI
-
You can use the UpdateWorkflow API operation to pause a workflow.
Deleting workflows
You can delete migration workflows using the Migration Hub Orchestrator console or the AWS CLI. The workflow must
have a Status of Not started,
Paused, or Failed.
- Console
-
To delete a migration workflow
-
Sign in to the AWS Management Console and access the Migration Hub Orchestrator console at https://console.aws.amazon.com/migrationhub/orchestrator/.
-
In the left navigation pane, under Orchestrate, choose
Workflows.
-
On the Workflows page, select the workflow that you want to
delete.
-
Choose Actions, Delete.
-
Enter delete
and choose Delete to
proceed.
- AWS CLI
-
You can use the DeleteWorkflow API operation to delete a paused or failed
workflow.