From the course: AWS Essential Training for Developers

How to choose AWS services

- Amazon Web Services has over a hundred different services, and it just seems like they're adding more and more each year. Now, don't worry. You're not going to be an expert in every service. I'm not an expert in every service. They've got AWS Ground Station for helping you communicate with your fleet of satellites in orbit. I don't have satellites in orbit, but if I ever run into a situation where I need to download data from satellites, I know that AWS has a service for that, and at that time, I'll just read the documentation and start looking for some other courses in our catalog that can give me some more information on how Ground Station works. This is how you'll walk around your AWS Starship as well. Once you've identified a potential need for an AWS service that you haven't used yet, you'll walk into that unused room of your Starship, turn on the lights and start twirling knobs and dials, and then explore a catalog for a course that's going to take you deeper into how to actually use that service when developing for your application. So it's important that you start learning what kinds of services AWS offers, what AWS has named that service, and the architecture icon for that service that you'll find in the documentation, blogs, and in other courses. Okay, fine. So why are we even doing this? As an example, let's say that your mobile application has a feature that lets your users upload video taken from a job site. You could install some open source tools directly onto some AWS servers, and build a background job that processes these videos in different sizes and formats, or you could have just used the Elastic Trans Coder Service, which is cheaper, more scalable, easier to use, and saved yourself a ton of time and money. You just need to know that Elastic Transcoder processes videos. And when you have a potential need for it, look up its pricing, figure out how it works, which might include reading a few architecture diagrams, and then determine if it's right for your project. Once again, you aren't going to use every service that AWS offers, but you should know what all the services can do for you, so that when you're building your app, you can use the right tool for the right job. Oh, and to make things a little more interesting for you, AWS has published new versions of the architecture icons, as you'll see in these clips from the AWS, "This is my architecture" video series. So sometimes you're going to see diagrams that use the new icons, and then sometimes you'll see diagrams that use the old icons. For this course, we use the new icons. And these are usually labeled on the diagrams so don't think you need to memorize the service name for all of them. However, when I show you the old and the new icon at the same time, these are common services that aren't typically labeled on the diagram. - So these are the only instances where I suggest you learn both icons, the name of the service, so this is Route53 as an example, and a brief summary of what this service does. Route53 is for DNS records, and I'll get into all that in a later video. But before we start diving into a bunch of AWS services, we're going to cover some key security concepts that you're going to see come up again and again in the various AWS services, and we're going to show you how to safely use your AWS Starship for the first time so you don't crash it into the side of a planet. Then, we're going to start from the bottom of the Starship in our engine room, and we're going to get our hands dirty with some servers and some storage options, and go through some cloud networking concepts. From there, we're going to move up to the nicer decks of our Starship, where AWS has done all the work of managing servers and databases, and look at the various tools they have for quickly deploying your code, or helping you quickly develop a mobile application, or leverage machine learning in your application for text recognition or voice detection. Along the way, we'll encounter several terms that you might have heard related to cloud computing, such as infrastructure as a service, big data, and serverless architecture. Hey, listen, don't worry, we're going to break down all the buzzwords for you, so get ready to learn.

Contents