Q: What is the output of AWS Server Migration Service?
Each server volume replicated is saved as a new Amazon Machine Image (AMI), which can be launched as an EC2 instance (virtual machine) in the AWS cloud.
Q: What kind of servers can be migrated to AWS using AWS Server Migration Service?
Currently, you can migrate virtual machines from VMware vSphere and Windows Hyper-V to AWS Server Migration Service.
Q: How do I track the status of the migration?
Visit the AWS Server Migration Service dashboard in the AWS Management Console to see the status of the replication.
Q: What operating systems does AWS Server Migration Service support?
AWS Server Migration Service supports migrating Windows Server 2003, 2008, 2012, and 2016, and Windows 7, 8, and 10; Red Hat Enterprise Linux (RHEL), SUSE/SLES, CentOS, Ubuntu, Oracle Linux, Fedora, and Debian Linux operating systems. Learn more.
Q: How long can I replicate my server volumes from on-premises to AWS?
You can replicate your on-premises servers to AWS for up to 90 days (per server). Usage time is calculated from the time a server replication begins until you terminate the replication job. After 90 days, your replication job will be automatically terminated. If you want to increase this limit, please discuss your use case with the AWS Support team.
Q: What is the difference between EC2 VM Import and AWS Server Migration Service?
AWS Server Migration Service is a significant enhancement of EC2 VM Import. The AWS Server Migration Service provides automated, live incremental server replication and AWS Console support. For customers using EC2 VM Import for migration, we recommend using AWS Server Migration Service.
Q: Are the 80/8080/443 ports required for AWS Server Migration Service?
To use AWS Server Migration Service, the 80/8080/443 ports to you accounts need to be opened, which requires you to complete the ICP recordal process or ICP exception process. Please contact your account manager or log a case with customer support to initiate the ICP recordal process or ICP exception process.
AWS Server Migration Service Connector
Q: What is the AWS Server Migration Service Connector?
The connector appliance is a pre-configured FreeBSD virtual machine (in OVA format). To set up AWS Server Migration Service, you need to first deploy the AWS Server Migration Service Connector virtual appliance on your on-premises VMware vCenter environment.
Q: How many AWS Server Migration Service Connectors do I need to install?
You need to install one AWS Server Migration Service Connector for each VMware vCenter environment.
Q: Can I use a proxy for communicating with the AWS Server Migration Service?
Yes. The AWS Server Migration Service Connector supports password-based proxy; it does not support NTLM-based proxy.
Q: Are server volumes securely transferred from my data center to AWS?
Yes. Replicated server volumes are encrypted in transit by Transport Layer Security (TLS).
Q: What data does the AWS Server Migration Service Connector capture from VMware vCenter?
The AWS Server Migration Service Connector captures VM inventory information from VMware vCenter and replicates server volumes to AWS.
Q: How do I update the AWS Server Migration Service Connector?
Updates are automatically downloaded and applied when you enable the auto-upgrade option; otherwise, they can be applied on-demand.
Q: Is it secure to deploy the AWS Server Migration Service Connector on my virtualization environment?
Yes, the AWS Server Migration Service Connector only captures basic VM inventory information and snapshots of server volumes from VMware vCenter and does not gather any sensitive information.
Q: Where are my replicated server volumes stored?
Your replicated server volumes are converted to AMIs and stored in your AWS account.
Hyper-V VM migration
Q: What are the key benefits of using AWS Server Migration Service for migrating on premise Hyper-V VMs?
By automating an incremental replication of live server volumes to the AWS cloud as AMIs, SMS allows customers to speed up migration process and reduce manual labor of migration significantly. SMS orchestrates server migrations by allowing customers to schedule replications and track the progress of a group of servers, alleviating the logistical burden of coordinating large-scale server migrations. With the support of incremental replication, customers are able to test server migrations easily. With the support of AWS console-based GUI, customers are able to start and manage migration and track progress easily.
Q: Who can benefit from AWS Server Migration Service for Hyper-V?
Any customer who is looking to migrate their Microsoft Hyper-V virtual machines managed by SCVMM or standalone Hyper-Vs to AWS will benefit from Hyper-V support in SMS. This may include enterprise customers, System integrators, and IT consulting firms who help enterprise customers migrate Hyper-V workloads to AWS.
Q: What components does AWS Server Migration Service have for Hyper-V VM migration?
SMS has an on-premises appliance, the SMS Connector, which talks to the service in AWS. The Connector incrementally transfers volumes of running Hyper-V VMs to the SMS service, and the service creates the AMI incrementally from the transferred volume.
Q: What permissions are required in System Center to deploy SMS Connector and start migration?
The SMS connector securely communicates with the SCVMM server using Windows remote management protocol (WinRM). Connector requires a non-admin AD user that is added to “Remote Management Users” group on the SCVMM host, has limited permissions on the CMIV2 and SCVMM WMI objects and is a part of the “Delegated administrator” group within SCVMM. A firewall port needs to be opened on the SCVMM server to allow for secure transfer of remote commands from Connector deployed on a private network within your datacenter. The AD user also needs read permissions on the VM data store on the Hyper-V machine. For additional security, customers may configure WinRM to allow only encrypted traffic over SSL using self-signed certificate and limit access to Connector IP/hostname alone.For more details, please refer to the SMS technical documentation.
Q: How do I set up AWS Server Migration Service for Hyper-V?
AWS console will walk you through a wizard that help you download and install the SMS Connector. You will need to work with your system administrators to create an active directory user for Hyper-V VM migration use. AWS SMS provides an interactive PowerShell script, to be executed with administrative privileges on your Hyper-V host, that automates the permissions setup/configuration. You will provide the AD user credentials and networking/proxy settings as necessary in the SMS Connector. For more details, please refer to the SMS technical documentation.
Q: Do I need to have SCVMM for AWS SMS to work with my Hyper-V hosts?
No. The SMS Connector can be configured to use SCVMM or standalone Hyper-V VMs.
Q: I’m operating both VMware and Hyper-V environments. Can I migrate VMware VMs and Hyper-V VMs simultaneously?
Yes, but you will need two separate SMS Connectors to simultaneously migrate VMs from both VMware and Hyper-V environments.
Q: What versions of Hyper-V, a component of the Windows server, does SMS support?
SMS Supports Hyper-V running on Windows Servers 2012 R2 and above.
Q: What operating systems does AWS Server Migration Service support?
AWS Server Migration Service supports migrating Windows Server 2003, 2008, 2012, and 2016, and Windows 7, 8, and 10; Red Hat Enterprise Linux (RHEL), SUSE/SLES, CentOS, Ubuntu, Oracle Linux, Fedora, and Debian Linux operating systems.
Q: How can I view my on-premises Hyper-V VM inventory in AWS console?
After configuring the SMS Connector, customers can import their on-premises Hyper-V inventory by clicking on the "Import server catalog" button in "AWS Console --> Server Migration --> Servers" tab.
Q: I’m going to migrate Hyper-V and VMware VMs simultaneously. Can I view the inventory of Hyper-V and VMware VMs together in a single pane of glass in AWS console?
Yes. SMS enables you to view the VM inventory of both Microsoft’s Hyper-V and VMware environments in a single pane of glass. After you import your on-premises Hyper-V VM inventory by clicking on the "Import server catalog" button in AWS SMS console, SMS automatically collects the VM inventory from all the SMS Connectors, deployed across Hyper-V and VMware environments, as a default.
Q: Can I see the VM inventory of Hyper-V and VMware environments separately?
Yes, on the ‘servers’ page on the AWS SMS console, you can filter by VM manager in the search bar to show only the VMs imported from Hyper-V or VMware environments.
Q: How can I distinguish Hyper-V VMs from VMware VMs during migration?
Yes, on the ‘replication jobs’ page on the AWS SMS console, you can filter by VM manager in the search bar to show only the progress of SMS replication jobs for VMs from Hyper-V or VMware environments.
Q: Can I track the progress of Hyper-V and VMware VMs migration simultaneously?
Yes. Customers can track the progress of Hyper-V and VMware VM migration in a single pane of glass under the ‘Replication Jobs’ page on the AWS SMS console.