Migrating VMs to AWS
In this very first short article of a two-section series, Posey offers an overview of how to migrate a virtual machine to the Amazon Net Companies cloud.
Migrating virtual devices (VMs) to the cloud has historically been a daunting approach. Fortunately, Amazon Net Companies (AWS) gives some resources that can make the migration approach a lot easier. In this two-section short article series, I want to give you an overview of how to migrate a VM to the AWS cloud.
Right before I get begun, I will need to issue out that a cloud migration isn’t an operation to be taken evenly. There are numerous points that will need to be regarded as all through the arranging stage of the migration. These content never handle migration arranging, and provide only to familiarize you with some of the migration resources. So with that claimed, let’s get begun.
Commence the approach by clicking on the AWS Migration Hub selection in the listing of AWS providers (it can be in the Migration part). This will result in AWS to open up the Migration Hub interface. When the Migration Hub dashboard seems, simply click on the Get Started off with Discovery button, followed by the Watch AWS Discovery Instruments button.
As you can see in Figure 1, AWS gives two various discovery resources. The very first of these resources is the AWS Discovery Connector. The AWS Discovery Connector is an agentless resource which is designed to work with VMware vCenter. If the VMs that you will need to migrate exist in a VMware setting and you’re employing vCenter Server to take care of your VMware hosts, then the AWS Discovery Connector is unquestionably the resource of preference.
The other selection is to use the AWS Discovery Agent. The AWS Discovery Agent is the resource of preference for migrating VMs that aren’t working on VMware, or that run in a smaller sized VMware setting which is not geared up with a vCenter Server. Incidentally, the Discovery Agent can also be employed to migrate workloads that are working on physical servers. For the needs of this two-section series, I will be employing the Discovery Agent.
AWS gives both equally a Linux and a Windows version of the agent. Right before you may be capable to install the agent, you may will need to obtain and install the x86 version of the Microsoft Visible Studio C++ Redistributable. You can obtain this ingredient from below.
There are two points that are worth noting about the requirement for the Microsoft Visible Studio C++ Redistributable. First, the AWS documentation particularly references the 2015 version, but newer variations will work. Next, if you have issues having the Microsoft Visible Studio C++ Redistributable to install efficiently, then make guaranteed that the process that you’re putting in it on to has all of the most up-to-date updates.
Once you’ve got mounted the Microsoft Visible C++ Redistributable on to the process that you prepare to migrate, you may will need to install the AWS Discovery Agent. The approach for doing so is a very little little bit difficult, due to the fact the agent contains a regular setup wizard. Having said that, if you run the setup wizard, the agent will install on your process, but it would not do something due to the fact the agent would not know how to connect with your AWS account. As these, you’re heading to have to install the agent from the command line. When doing so, you’re also heading to have to specify your vital ID and your magic formula vital. The command syntax appears to be like this:
msiexec.exe /i AWSDiscoveryAgentInstaller.msi Area=”us-west-2″ Essential_ID=”
If you look at Figure 2, you can see that I downloaded the agent and copied it to a folder named AWS Discovery Agent. From there, I ran the command syntax (the keys are concealed for the sake of security).
As you look at Figure 2, you may recognize that the installer would not generate any seen output. To find out whether or not the agent has been mounted, open up the Manage Panel and go to Programs | Programs and Characteristics. The Programs and Characteristics display screen must listing the AWS Discovery Agent among the mounted purposes. You can see what this appears to be like in Figure three.
It can acquire fifteen minutes or more for the agent to begin populating the AWS console with details. While you’re waiting around, I suggest opening the Company Manage Manager (by coming into the Companies.msc command at the server’s Run prompt) and checking to make guaranteed that the AWS Discovery Agent and AWS Discovery Updater providers are mounted and working. You can see what this appears to be like in Figure four.
Now that the AWS Discovery Agent is mounted, it can be time to begin working toward a migration. I will clearly show you the up coming actions in Component 2.
Brien Posey is a sixteen-time Microsoft MVP with many years of IT knowledge. As a freelance writer, Posey has prepared hundreds of content and contributed to quite a few dozen guides on a large assortment of IT subjects. Prior to heading freelance, Posey was a CIO for a countrywide chain of hospitals and health and fitness treatment services. He has also served as a community administrator for some of the country’s greatest coverage organizations and for the Section of Protection at Fort Knox. In addition to his continued work in IT, Posey has put in the very last quite a few several years actively coaching as a industrial scientist-astronaut applicant in preparing to fly on a mission to research polar mesospheric clouds from house. You can follow his spaceflight coaching on his Net internet site at.