AWS Migration Hub
AWS Discovery Services
AWS Server Migration Services
The course is part of these learning paths
In this course we will learn to recognize and explain the migration services available from AWS and AWS partners, and how to run a migration using the AWS Server Migration Service.
This course is suited to anyone running or involved in a cloud migration project. As a pre-requisite, I recommend completing our “Getting Started with Cloud Migration” course first so you have some understanding of migration projects and the benefits of the migration services to a cloud migration project.
In this course, we will learn to apply and use the migration services available from AWS.
First, we will explore the AWS Migration Hub service - which provides a simple way to discover, track and manage the migration of servers and applications.
Then we will learn to use and apply the AWS Application Discovery Service - which provides a way to discover and audit applications and servers running in both hardware and virtualized environments.
Following that we will apply and use the AWS Server Migration Service within the migration hub to manage migrating virtual machines from an on-premise or datacenter environment to the AWS public cloud.
I recommend completing our Getting Started with Migrating to the Cloud course prior to this course so you understand the basic concepts and benefits of cloud migrations. If you are new to Cloud Computing, I'd recommend completing our What is Cloud Computing? course first so you have an understanding of cloud computing concepts.
This course is a blend of instructional learning and demonstration. In this course we cover the following topics:
- The AWS Migration Hub - which provides a simple way to manage migration of severs and applications.
- The AWS Discovery Services -we explore the AWS Discovery Connector and the Discovery Agent which enable us to audit and quantify a migration project.
- The AWS Server Migration Service - which provides a way to manage migrating vmware and HyperV virtual machines to the AWS Cloud.
If you have thoughts or suggestions for this course, please contact Cloud Academy at firstname.lastname@example.org.
- [Instructor] Hi and welcome back. In this short lecture we'll set up the AWS Discovery Connector. To do this we first need to download and deploy the OVA file from the AWS website. So, first we choose to download the agent from the AWS site here. Now we need to sign into vCenter as a VMware administrator. Once in there choose File, Deploy OVF Template. Now the most important thing to remember is the disk formatting, so on the Disk Format page select one of the Thick Provision disk types, ideally Thick Provision Eager Zeroed because it has the best performance and reliability. It does, however, require a couple of hours to zero out the disk, so there is gonna be some delay, so don't choose Thin Provision. That option makes deployment faster but significantly reduces disk performance in the long run. The console displays the IP address of the connector console, so save that IP address into a secure location so you can access it later. You're gonna need it to complete the connector setup process. So, after you complete this initial setup, you can access the Connector settings by using SSH and the Connector IP address: root@Connector_IP_address. So, the default username is ec2-user and the default password is ec2pass. Okay, a few things to consider in the setup. The agent list Discovery Connector has an auto update feature, so turning on the auto update ensures that you have the latest version of the Discovery Connector, so you can enable the auto updates under the Actions menu to just choose Enable Auto-Updates. Now, a few common problems to avoid. So, the Agentless Discovery Connector doesn't support standalone ESX hosts, so you need to have all hosts registered in vCenter. If you don't see inventory information coming through to the migration hub after starting data collection with the connector, make sure you have registered the connector with your vCenter server. So, you may need to stop and start the services a few times to confirm that it is registered. The Discovery Connector can see all the VMs but not within the actual VM itself, so you'll get some information but not of the information about what's actually inside the virtual machine. Discovery Connector doesn't provide the same level of granularity as you do get with the Discovery Agent. To discover data about all ESX hosts and VMs under the current vCenter set, set your role in the vCenter user to read only and that will show you all the hosts. However, perhaps you only plan to migrate a subset of VMs or perhaps you have constraints on reporting and visibility of your entire fleet so you may not want to report all services within your vCenter environment. Now, you can use these permission settings to restrict which hosts and VMs are included in your data collection, so you can either allow all hosts and VMs under the current vCenter to be inventoried or you can grant permissions on a case-by-case basis to restrict access to those that you do not want to make visible. That brings this lector on the Discovery Connector to a close.
About the Author
Head of Content
Andrew is an AWS certified professional who is passionate about helping others learn how to use and gain benefit from AWS technologies. Andrew has worked for AWS and for AWS technology partners Ooyala and Adobe. His favorite Amazon leadership principle is "Customer Obsession" as everything AWS starts with the customer. Passions around work are cycling and surfing, and having a laugh about the lessons learnt trying to launch two daughters and a few start ups.