AWS GovCloud (US)
User Guide

AWS Server Migration Service (AWS SMS)

To use Server Migration Connector with the AWS GovCloud (US) Region, follow these steps on your Server Migration Connector VM to permanently convert your connector virtual appliance to an AWS GovCloud (US) connector.

  1. Launch the VMware vSphere Client and locate your connector VM in the inventory tree. Right-click the connector VM, and choose Open Console.

  2. Log in as ec2-user with the password ec2pass.

  3. Run the following command:

    sudo enable-govcloud
  4. In a web browser, access the connector VM at its IP address (https://ip-address-of-connector/) to open the setup wizard. You should now see AWS GovCloud (US) Region as the only region listed in the AWS Region drop-down list.

For more information about AWS SMS, see the AWS SMS User Guide.

ITAR Boundary

The ITAR boundary defines where customers are allowed to store ITAR-regulated data for this service in the AWS GovCloud (US) Region. You must comply with the boundaries in order to maintain ITAR compliance. If you do not have any ITAR-regulated data in the AWS GovCloud (US) Region, this section does not apply to you. The following information identifies the ITAR boundary for this service:

ITAR-Regulated Data Permitted

ITAR-Regulated Data Not Permitted

  • All data entered, stored, and processed on an encrypted, non-root, non-boot partition in a VMware virtual machine can contain ITAR-regulated data.

  • VMware metadata is not permitted to contain ITAR-regulated data. This metadata includes any text shown in vSphere Client on any virtual machine's Summary tab, Tasks & Events tab, or Edit Settings dialog in the vCenter Server inventory.

  • Do not enter ITAR-regulated data in the following fields:

    • VM names or paths

    • VMDK paths

    • IP addresses or host names of VMs, ESXi hosts, or vCenter Server

    • User name of any vCenter service account created for the use of SMS Connector

  • Do not enter ITAR-regulated data into the root or boot partition of any virtual machine being imported using the Server Migration Service.

On this page: