Prepare and migrate waves - AWS Transform
Prepare wavesMigrate waves

Prepare and migrate waves

At this stage, you will see migration waves in the Job Plan pane. For each wave, perform the following steps. In some of these steps you will have the option of importing an updated inventory file. AWS Transform allows one import to a given target AWS account and target AWS Region at a time. This means that if you work on more than one wave simultaneously, or if there is more than one migration job running with the same target account, you must wait for an import to finish before you can perform another import in a different wave or job.

Prepare waves

Each wave includes a Set up migration wave task. On its Collaboration tab you can configure the wave's settings.

Set up migration wave

  1. In the Job Plan pane, expand the step Set up migration waves, and then choose Set EC2 recommendation preferences. Follow the instructions in the right pane, and then choose Continue. Learn more about Amazon EC2 recommendations in Generating Amazon EC2 recommendations in AWS Migration Hub.

  2. In the Staging area subnet section, you can choose a staging area subnet from the dropdown menu of the available subnets.

    Only subnets that are tagged in VPCs that are also tagged with these tag key-value pairs appear in the list. Learn more in Tag your VPCs and subnets.

  3. For each wave, choose your IP assigment approach:

    • Use source IP or the converted IP from the new CIDR

    • Use new IP using DHCP

  4. In the Job Plan pane, choose Confirm inventory for wave-name. Download the inventory file and review the list of servers and Amazon EC2 configurations. Modify the file if necessary, but do not remove columns or change the titles of the existing columns. You can control the operating system licensing options (BYOL / LI) and tenancy by specifying the configuration in columns with these headers: mgn:launch:placement:operating-system-licensing and mgn:launch:placement:tenancy. Learn more in Import parameters in the Application Migration Service user guide. After you choose whether to continue with the file you downloaded or to upload a version of the file that you updated, choose Continue.

Note

AWS Transform provides Amazon EC2 recommendations based on the utilization specification of your source VMs. You can modify the suggested Amazon EC2 instance types to include recommendations from the Migration Evaluator, AWS Optimization and Licensing Assessment (OLA), or a Migration assessment job.

Tag your VPCs and subnets

Your VPCs and their subnets must be tagged with these tags so that their subnets appear in AWS Transform's list of available subnets:

  • Key: CreatedFor Value: AWSTransform

  • Key: ATWorkspace Value: workspace ID

    Find your workspace ID in the AWS Transform web app URL, https:// ... /workspace/workspace-id/job/job-id

To tag your VPCs:

  1. In the AWS console, open VPC.

  2. Select a VPC.

  3. In VPC details choose Tags > Manage Tags > Add new tag, and add each tag. To tag each subnet:

To tag a VPC's subnets:

  1. Choose a subnet from the VPC.

  2. In the subnet, select the Tags tab.

  3. Select the Add new tag and add each tag.

  4. Save your changes.

Migrate waves

Deploy replication agents

  1. In the Job Plan pane, expand Deploy replication agents, and then choose Start replication agent deployment. You have two options:

    • Use AWS Transform to automate deployment: To automate the deployment of the agents on the source servers in this wave, AWS Transform uses an MGN connector already deployed in your account. For information about how to deploy an MGN connector in your account, see Set up the MGN Connector in the Application Migration Service User Guide.

      To use this option, perform the following steps:

      1. Open the AWS Systems Manager console at https://console.aws.amazon.com/systems-manager/.

      2. In the left navigation pane, under Node Tools, choose Fleet Manager.

      3. Choose the name of the managed instance of the MGN connector that you want AWS Transform to use for this wave.

      4. Tag the managed instance with the following key-value pairs.

        • Key: CreatedFor Value: AWSTransform

        • Key: ATWorkspace Value: workspace ID

        Find your workspace ID in the AWS Transform web app URL, https:// ... /workspace/workspace-id/job/job-id

      5. In AWS Transform, choose Use AWS Transform to automate deployment.

      6. Specify the MGN connector that you tagged and the AWS Secrets Manager secret that you want AWS Transform to use for this wave. You must create a single set of credentials for the MGN connector to use for deploying replication agents on all servers in a particular wave. For information about setting up the secret, see Register server credentials.

      7. If AWS Transform encounters errors during the deployment of the agent, you will see those errors in the Job Plan pane. Choose each error in the Job Plan pane to view its details in the Collaboration tab.

      8. After you resolve all errors, you can track the replication status for the wave by choosing Review replication status in the Job Plan pane.

    • Deploy replication agents on your own: You can deploy the replication agents on the source servers manually. Alternatively, you can use the MGN connector or another automation framework to deploy them on your own. For information about how to set up the MGN connector, see Set up the MGN Connector in the Application Migration Service User Guide.

      To deploy the replication agents manually, or use an automation framework other than the MGN Connector to deploy them, perform the following steps.

      1. Go to the AWS Application Migration Service console, and export a list of your servers. For instructions, see Exporting your data inventory.

      2. Filter the list by wave to obtain a list of the servers in the current wave.

      3. Follow the instructions under Installing the AWS Replication Agent. Specify the user-provided-id parameter, and for every server set its value to the server's mgn:server:user-provided-id as it appears in the .csv file that you exported from AWS Application Migration Service. AWS Transform connects the replication agent with the imported server using this parameter. If it's not provided, MGN will create a separate instance of source server for each agent that is installed.

    To see the replication agent installation status, check the AWS Systems Manager run command history at agent installation time. For information, see Understanding command statuses in the AWS Systems Manager User Guide.

    To see the replication status in real-time, go to the AWS Application Migration Service console. Status updates in the AWS Transform web app are delayed.

    For quotas related to replication, see AWS Application Migration Service service quota limits in the Application Migration Service User Guide.

    Note

    AWS Transform does not support MGN agentless replication. For information about agentless replication, see Agentless replication overview in the Application Migration Service User Guide.

  2. When replication is complete, expand Review the replication status in the Job Plan pane. In the right pane you can see the status of the replication and resolve replication alerts.

Note

To proceed, you must install the MGN replication agent on all servers in a wave. Disconnect and archive servers on which you don't install the replication agent. You can use the disconnect-from-service command to disconnect servers. To archive disconnected servers, use the mark-as-archived command. The archiving command only works for source servers whose lifecycle state is DISCONNECTED.

Launch test instances

  1. In the Job Plan pane, under Launch test instances, choose Confirm instance launch.

  2. Download the inventory file, review it, and choose whether to continue with the current file or upload a modified one, then choose Launch test instances. You can change the launch settings within the inventory file, but don't modify the list of source servers and applications.

Mark applications as ready for cutover

  1. In the Job Plan pane, expand Mark applications as ready for cutover, and choose Mark applications as ready for cutover.

  2. In the Collaboration tab, review the replication status of each application, and resolve replication alerts.

  3. Choose Mark for cutover.

Launch cutover instances

  1. In the Job Plan pane, under Launch cutover instances, choose Confirm instance launch.

  2. Download and open the inventory file, review the inventory, and choose whether to continue with the current inventory or upload a modified one. At this step, don't modify the list of source servers and applications listed in the inventory file. You can only change the launch settings within the inventory file.

  3. Choose whether to continue with the current inventory or upload a modified one, and then choose Continue.

  4. Choose Launch cutover instances.

Finalize cutover

  1. (Optional) Review the launched Amazon EC2 cutover instances, validate connectivity and run acceptance tests. If you want to fix anything because there's a connectivity issue or a problem in the testing, you need to revert the cutover. This is the time to revert it.

  2. In the Job Plan pane, expand Finalize cutover, and then choose Start finalizing cutover. Finalizing the cutover removes the replication agents. After you finalize the cutover you cannot make any changes, you cannot fix any connectivity issues, or anything else, and you cannot revert the cutover.

  3. Choose Finalize cutover.