This four week course focuses on migrating workloads to AWS. We will focus on analyzing your current environment, planning your migration, AWS services that are commonly used during your migration, and the actual migration steps.
Hands-on labs are available, though not required for this class. Access to the labs is limited to paid enrolled students. You can audit this course without taking the labs. As we dive into each of the services covered in this class, there will be links to documentation where you can find example applications and code samples.
If you are new to AWS, we strongly suggest that you take “AWS Fundamentals: Going Cloud Native” (https://www.coursera.org/learn/aws-fundamentals-going-cloud-native) course available on Coursera to provide an introduction to AWS concepts and services.

Impartido por:

Seph Robinson

Sean Rinn

Transcripción

- [Sean] In phase two of preparing for your migration, the focus is on discovery and planning. As a consultant, I frequently had the task of combing through a company's environment to try and track down all of the in use software and to create spreadsheets of which servers ran which services. The AWS Application Discovery Service helps you to plan your migration to the AWS cloud by collecting usage and configuration data about your on-premises servers. Application Discovery Service offers two ways of performing discovery and collecting data about your on-premises servers; agentless and agent-based. Agentless discovery works with VMware vCenter, and can be performed by deploying the AWS Agentless Discovery Virtual Appliance. After the discovery connector is configured it identifies virtual machines and hosts associated with vCenter. The discovery connector collects configuration information about your servers, like server host names, IP addresses, Mac addresses, and disc resource allocations. The discovery connector also collects metrics about the VMs. These data points can be extremely useful in your migration planning activities, especially if you are using the replatform approach. It can inform decisions like what type and size of EC2 instance to use. Knowing both the average and peak utilization metrics for things like CPU, RAM, and disk I/O, you can make a more informed decision about how to design your environment in AWS. It's important to note, however, discovery connector cannot look inside each of the VMs, so it cannot figure out what processes are running on each VM, or what network connections exist. If you need insights into that type of information, then using an agent-based approach will be required. Agent-based discovery can be performed by deploying the AWS Application Discovery Agent on each of your VMs and physical servers. The agent will then collect static configuration data, similar to the discovery connector. In addition to those static config details, the agent will record detailed time series systems performance information, inbound and outbound network connections, and processes that are running. You can export this data to perform an analysis and to identify network connections between servers for grouping servers as applications. The Application Discovery Service is integrated with our AWS Migration Hub, which helps to create a single pane of glass view into migration progress. After the service has performed its discovery, you will be able to view the discovered servers, group them into applications, and then use the Migration Hub to track the migration status of each application. All of the data that is collected by the Application Discovery Service can be exported for analysis using tools like Amazon Athena and Amazon QuickSight. Overall, the AWS Application Discovery Service helps you to obtain a snapshot of your current state of your data center servers, and the data collected helps to create a cost-optimized migration plan based on your unique business requirements.