Migrating on-premises servers to the cloud in large-scale environments can be a complex undertaking without an orchestrator that automates the process, schedules tasks, minimizes bandwidth usage, and reduces cutover times. In this article, I will guide you through efficiently migrating on-premises workloads to AWS using the AWS Server Migration Service (AWS SMS), with a detailed step-by-step approach.
What is the AWS Server Migration Service?
Launched in October 2016, AWS SMS was designed to streamline the server migration process. It supports the migration of on-premises virtual machines (VMs) without requiring agents, making use of a virtual appliance. The service offers several key benefits:
- It automates incremental replication of live server volumes to AWS, minimizing downtime during cutover.
- It facilitates large-scale server migrations in a cost-efficient manner.
- It supports a wide array of operating systems.
- It manages and tracks migration progress through a user-friendly interface.
AWS SMS is particularly advantageous for scaled migrations from VMware environments to AWS, where considerations like downtime, agentless tools, incremental replication, and pre-cutover application testing are essential. The service is offered at no cost; you only pay for the storage resources utilized during migration, including Amazon EBS snapshots and Amazon S3 storage.
Currently, AWS SMS is available in several regions, including GovCloud (US), US East (N. Virginia), US West (Oregon), US East (Ohio), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Seoul), and Asia Pacific (Mumbai).
How Does it Work?
The migration process with AWS SMS involves four stages, as depicted in the accompanying diagrams. The final outcome of this service is an Amazon Machine Image (AMI), generated for each replication run until the job is either deleted or automatically terminated after 90 days.
Migration stages are iterative, with adjustable replication intervals ranging from a minimum of 12 hours to a maximum of 24 hours. The lifecycle of this iterative cycle lasts for 90 days, after which the replication job concludes. You can select a group of VMs for migration, with AWS SMS supporting up to 50 concurrent VM migrations per account.
How Do You Use AWS SMS?
To utilize AWS SMS, a connector that oversees the migration workflow is necessary. This connector is deployed within the vCenter environment.
Before deploying the SMS connector, ensure that your environment meets the AWS SMS requirements and has the correct firewall settings. Failing to adjust the firewall for stateful outbound connections for DHCP, DNS, HTTPS, ICMP, and NTP services will lead to deployment failures.
You will also need to create a vCenter service account and an IAM user with the appropriate permissions, as outlined in the AWS SMS documentation. For more insights on this topic, check out this excellent resource.
Deploying the Server Migration Connector Virtual Appliance
The Server Migration Connector is a preconfigured FreeBSD virtual machine available in OVA format for VMware environments. Download the latest version of the connector from AWS and log in to the vCenter with the necessary credentials for deployment.
Once you access the vCenter, right-click on it and select “Deploy OVF Template.” Specify the OVF template’s source location and proceed through the setup process, selecting appropriate options for storage and network configurations.
Before configuring the connector, ensure it can resolve the FQDN of vCenter and ESXi hosts. If any network settings need adjustment, log in to the connector appliance console and follow the Advanced Network Configuration guide.
Configuring the Connector
Open a web browser and navigate to the Connector VM’s IP address to launch the setup wizard. Follow the prompts to review the license agreement, create a password, and configure network settings. Enter your AWS credentials and vCenter service account details, and upon accepting the vCenter certificate, complete the registration process.
Once registered, verify the connector’s status on the Connectors page, which is segmented into various sections for easy management.
Now you can proceed to import your server inventory and orchestrate your migration events. For more details on related topics, you might find this blog post engaging.
Importing the Server Catalog
After the connector is installed and registered, access the AWS SMS console and select “Connectors,” followed by “Import server catalog” to compile your complete server list. Note that this process may take some time, and you can re-import or clear the server catalog whenever necessary.
Creating a Migration Job
Before initiating a migration job, ensure sufficient space is available in the datastore.
In conclusion, AWS SMS serves as a powerful tool for simplifying server migrations to the cloud, making the process more manageable and efficient.
Leave a Reply