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

- [Seph] AWS is API centric. Hopefully you find that news relieving. Over the past few weeks we've been looking at a lot of the tools that AWS has that help with merging environments when migrating. But if you had to work with those tools manually, one by one, only through a management console, it would likely drive you crazy. So to make life easier, AWS is API centric. What I mean by this is that a large majority of AWS services and tools have directly accessible APIs that you can use for creating, configuring, and managing the services you employ. The reason I bring this up is because especially when you're trying to handle the very difficult and sensitive task of migrating data in applications across environments, handling everything manually is going to cause a lot of headache, a lot of trouble shooting, and timing is gonna be very difficult to predict and test on a large scale. If, on the other hand, you're able to automate many of the tasks, the scale of what you can do grows exponentially. Essentially it goes from a mad scientist running around, flipping all of the levers and switches, to a better equipped mad scientist monitoring what's going on while their assistants are able to handle all of the tasks. To access the APIs within AWS, there are a couple of options. One, you can use the various SDKs that provide access to the interfaces and two, you can use the AWS Command Line Interface, or CLI. Both of these give you direct access that allows you to fine tune and test what you need to do and takes away a lot of the manual effort that you would otherwise have to deal with. The power of these are that they allow you to create scripts and applications to handle a lot of the work not only during migration, but also when managing, optimizing, and configuring your environment post migration. It is very important that using the APIs becomes habit as soon as possible. If you're not already familiar, I highly suggest you start with the AWS CLI. This is a toolset that is easy to install locally and gives you the ability to do anything you would be able to do in the management console and more. Try out different tasks, test your various scripts, and see how it can help you.