AWS Server Migration Service
User Guide

Replicating VMs Using the AWS SMS Console

Use the AWS SMS console to import your server catalog and migrate your on-premises servers to Amazon EC2. You can perform the following tasks:

To replicate a server using the console

  1. Install the Server Migration Connector as described in Getting Started with AWS Server Migration Service, including the configuration of an IAM service role and permissions.

  2. In a web browser, open the SMS homepage.

  3. In the navigation menu, choose Connectors. Verify that the connector you deployed in your VMware environment is shown with a status of healthy.

  4. If you have not yet imported a catalog, choose Servers, Import server catalog. To reflect new servers added in your VMware environment after your previous import operation, choose Re-import server catalog. This process can take up to a minute.

  5. Select a server to replicate and choose Create replication job.

  6. On the Configure server-specific settings page, in the License type column, select the license type for AMIs to be created from the replication job. Linux servers can only use Bring Your Own License (BYOL). Windows servers can use either an AWS-provided license or BYOL. You can also choose Auto to allow AWS SMS to select the appropriate license. Choose Next.

  7. On the Configure replication job settings page, the following settings are available:

    • For Replication job type, choose a value. The replicate server every interval option creates a repeating replication process that creates new AMIs at the interval you provide from the menu. The One-time migration option triggers a single replication of your server without scheduling repeating replications.

    • For Start replication run, configure your replication run to start either immediately or at a later date and time up to 30 days in the future. The date and time settings refer to your browser’s local time.

    • For IAM service role, provide (if necessary) the IAM service role that you previously created.

    • (Optional) For Description, provide a description of the replication run.

    • For Enable automatic AMI deletion, configure AWS SMS to delete older replication AMIs in excess of a number that you provide in the field.

    Choose Next.

  8. On the Review page, review your settings. If the settings are correct, choose Create. To change the settings, choose Previous. After a replication job is set up, replication starts automatically at the specified time and interval.

In addition to your scheduled replication runs, you may also start up to two on-demand replication runs per 24-hour period. On the Replication jobs page, select a job and choose Actions, Start replication run. This starts a replication run that does not affect your scheduled replication runs, except in the case that the on-demand run is still ongoing at the time of your scheduled run. In this case, the scheduled run is skipped and rescheduled at the next interval.

To monitor and modify server replication jobs

  1. In the AWS SMS console, choose Replication jobs. You can view all replication jobs by scrolling through the table. In the search bar, you can filter the table contents on specific values.

  2. Select a single replication job to view details about it in the lower pane. The Job details tab displays information about the current replication run, including the ID of the latest AMI created by the replication job. The Run history tab shows details about all of the replication runs for the selected replication job.

  3. To change any job parameters, select a job on the Replication jobs page and choose Actions, Edit replication job. After entering new information in the Edit configuration job form, choose Save to commit your changes.


    You may need to refresh the page for the changes to become visible.

To shut down replication

  1. After you have finished replicating a server, you can delete the replication job. Choose Replication jobs, select the desired job, choose Actions, and then choose Delete replication jobs. In the confirmation window, choose Delete. This stops the replication job and cleans up any artifacts created by the service (for example, the job's S3 bucket). This does not delete any AMIs created by runs of the stopped job.


    You may need to refresh the page for the changes to become visible.

  2. To clear your server catalog after you no longer need it, choose Servers, Clear server catalog. The list of servers is removed from AWS SMS and your display.

  3. When you are done using a connector and no longer need it for any replication jobs, you can disassociate it. Choose Connectors and select the connector to disassociate. Choose Disassociate at the top-right corner of its information section and choose Disassociate again in the confirmation window. This action deregisters the connector from AWS SMS.