Try our training for free.

Gain instant access to our entire IT training library for 1 week. Train anytime on your desktop, tablet, or mobile devices.

Note: This is a great informational course on AWS. However, Jeremy's newer AWS courses provide training for the AWS Certified Solution Architect certification....
Note: This is a great informational course on AWS. However, Jeremy's newer AWS courses provide training for the AWS Certified Solution Architect certification.

In this Amazon Web Services: Essentials course, trainer Jeremy Cioara covers what AWS is, how it works, and how you (and your organization) can get started using it. Related Area of Expertise:
  • Amazon Web Services

Delve into the world of Amazon Web Services (AWS) with trainer Jeremy Cioara. If you're trying to establish a cloud presence, AWS offers a cost-effective, scalable infrastructure.

This course is full of cool technology, but the biggest “way-cool” factor is the complete shift in the way we think about and handle Information Technology! With AWS, you no longer have to build your own world-wide IT enterprise solution to deliver amazing cloud-based services.

Jeremy walks you through how to sign up for an AWS account, create and use instances, Virtual Private Cloud (VPC), Simple Storage Service (S3), and more. You'll also see a real-life case study on a company called CBT Nuggets that migrated its services to AWS.

Find out how easy it is to use AWS, and how to make the powerful features of AWS work for you.

1. Amazon Web Services: AWS Foundations - Getting the Most from this Series (3 min)
2. AWS Foundations: How to Build a Cloud Presence (37 min)
3. AWS Foundations: Getting Started with AWS (34 min)
4. EC2: Creating an EC2 Instance - AMI Selection (24 min)
5. EC2: Creating an EC2 Instance - Pricing (30 min)
6. EC2: Creating an EC2 Instance - Instance Types (26 min)
7. EC2: Creating an EC2 Instance - Tags and Key Pairs (29 min)
8. EC2: Creating an EC2 Instance - Security Groups (33 min)
9. EC2: Creating an EC2 Instance - Elastic IPs and ELB (31 min)
10. VPC: It's MY Cloud Now! Understanding AWS Network Management (31 min)
11. VPC: It's MY Cloud Now! Understanding AWS Network Management, Part 2 (31 min)
12. VPC: It's MY Cloud Now! Understanding AWS Network Management, Part 3 (25 min)
13. S3 Foundations: Getting Started with S3 (26 min)
14. S3 Foundations: Working with S3 Storage (28 min)
15. Route 53: DNS Management Made Easy (33 min)
16. IAM: Creating and Managing User Access (28 min)
17. AWS Case Study: CBT Nuggets Move to the Cloud (21 min)
18. AWS: Series Wrap-up (9 min)

Amazon Web Services: AWS Foundations - Getting the Most from this Series

AWS Foundations: How to Build a Cloud Presence

AWS Foundations: Getting Started with AWS


Let's kick the tires and go for a ride. Getting started with Amazon Web Services. When I got started, many, many moons ago, it was from an email forward that somebody sent me. And they said, check it out. I went in, created an account and looked around. I go, wow, this is a lot of stuff.


And I closed it. You know, not even like, wow, that's a big something or another. But I didn't really explore and understand what it was. If somebody would have been there tell me, hey Jeremy, guess what you can do with this, and put all these pieces together.


There are so many decisions that I would have made differently in all the history leading up to where we are now. Wow I could have saved a fortune-- it's all those vision is 20-20 in hindsight, right-- that I would have said wow, there's so much more I could have done.


So that's what I want to do for you here. I want to talk about what you need to get started-- which is actually a little more than you may think. Understanding Amazon Web Services services-- what are the core services? And this is what I would really say is the meat of this Nugget, to say, here's what you can do with AWS.


And then I really want to answer the question, can I do all this for free? I mean, do I have to pay anything to get started, really? So the short answer to that is yes. You can do a lot of this stuff for free. You can sign up for an account for free. You can really step right into this.


But I'm going to talk a lot about what's available for free at the very end. Because I want you to understand the services before we say what's available for free. So number one when you get started with AWS, what you need is a purpose. Meaning, understanding AWS is one thing, which is great.


It's neat to be able to see the services that are there. But one of the things that I know-- let me give you this perspective. I have taught Cisco technology for years and years. And Microsoft technology, and Novell technology. I'm a technologist guy, I just love technology.


So I've taught all these things and I get people to learn Cisco. And I'm talking about, oh, this is what a router and a switch does. And a lot of times, I've talked to people who have gone out and bought all this lab equipment for their home to try this stuff out, to learn it but they buy it without a vision.


And they have piles of equipment sitting at their house to test it out, and they look at it every day just collecting dust, going I don't know what I want to do with that. And so it's a little more of a commitment to do that in the Cisco because you have to buy all the gear, but it's the same feeling with Amazon Web Services.


You can sign up for account and walk into it, and you'll stare at all the tabs and all of the capabilities, and you'll go, wow, here I am. So, throughout this series, please hang with me. I want to envision you with purposes. I'm going to create a series of case studies throughout this series of, OK, let's say you want to do this.


And somebody wants to create a website, or somebody wants a backup service off-site, and all these kind of scenarios. So I can get your mind going to go, oh OK, I can see why I would use that. Technology for the sake of technology is worthless. You have to have a purpose.


So what's your mission, what's your goal-- have a good definition before you start. Second off, you need to have some login information. So you're going to go website-- and this is what I want to just prepare you for. I mean, it's easy to do. You go, you say I want an account.


By the way the address is-- let me just bring it up. Shoot my browser over here. The address is just a And sure enough, right there, it's hey, this is AWS. Sign up now. This is where you go. Create an account for free, only pay for what you use.


And it comes in and this is where you go ahead and create your account. Now I've already created account. And what I did was take some snapshots as it was going through that. Because there's a couple things that may take you off guard if you're not ready for them.


So this is, when you sign up for an account, the first thing it's going to bounce off of you is hey, what kind of account information do you want. What's your name, what's your company about, the normal stuff that you would expect when you agree to an account.


The second thing-- and this is the big thing-- the second thing it's going to ask you for is your credit card number. This will cause a lot of people go whoa Nellie, whoa, hey. I'm careful, you're careful, everybody's careful with where they're putting their credit card online because they go, I don't want to get charged.


Well, if you think about it, Amazon is really thinking ahead when they're doing this. If they don't require you to put some-- and I'll say this loosely, but-- put some skin in the game, to where it's like, I'm putting something into this, Amazon would end up with billions of accounts of people just creating them on a whim.


Signing up for free services, or just hey, let's just create 50 accounts. That kind of thing. With no commitment at all. Amazon would just have a user database of billions of users, which I'm sure they already have enough of them already. So they do require you to put in a credit card number.


They're not going to charge it. I think they authorize-- I think they tell you, we're going to authorize a $1 charge. Meaning, not charge you, but just send through an authorization to make sure it's a valid credit card that can be used. And then this is the next thing that may surprise you.


That after you put in the credit card, they're going to verify your identity by phone. Now this is pretty sweet. When I did this, I was like hey, this is not too shabby. And I sorry, I love you, but I had to cross my telephone number out on there. Yeah. I don't give that out.


So I put my telephone number in there. You can even put in an extension number, which I did it because I have a certain extension at my office. And they dial you up and they say please type in the pin number that you see online. You type it in, they go OK we've now verified your account.


So think of this coming into it. There's really three verifications that are happening here. One, they're going to check your email address. They're going to send you verification email. Actually that comes at the end. But they will. They're going to ask for a credit card, and verify that the credit card is valid.


And they're going to ask for a phone number. And they're actually going to call you there and ask for the pin number. It's really cool, because you type in the pin number, and as you do your web page refreshes. They must be using some amazing technology, like Amazon Web Services or something to run that.


But they verify all three things. So I want you to go into that eyes wide open. It's free to create an account, but you can't just go in and make stuff up. You know, like we all do on all the websites. Like use some spam email address, no credit-- they do require some commitment even though they're not going to charge you.


So, what else do you need? You need an understanding of the services. Which that's going to be the bulk of it. That's where the next slide, I'm gonna spend most of my time here. And then you're going to need to start working in the AWS Management Console. That's what this looks like over here.


This is kind of your dashboard for managing every service in here. Like right up at the top, you can see some of the services that I have. There's Elastic Beanstalk, S3, EC2, Virtual Private Cloud, all these different services that we're going to be discussing in just a moment.


But this is how you access all of those services from a GUI. It's not the only way to access it, but I'll say initially this is your primary point of access. Are you ready? Let's get into the meat of this Nugget, which is the AWS services, or what I would call the core services.


Stuff that everybody needs to at least to know about and know of its existence to get started with AWS. I'm going to start in no particular order, other than this is where most people start first-- EC2. EC2-- and if you're a purist, you're going, they should have called it ECC2. Yeah, I thought that too.


But they called it EC2. Elastic Compute Cloud is where you generate your virtual servers in the cloud. So when I say, I want an Ubuntu server accessible from anywhere in the world, or a Windows 2008 R2 server, blah, blah, blah. I would go straight to EC2, and generate what Amazon calls an instance.


An actual virtual server running, accessible from anywhere in the world. That's all it is. Now, let's move into the next service, because the next logical question will be, well where does that server store its data? This is actually gets to a bigger discussion.


Amazon started everything with Simple Storage Service, or what they call it S3. S3 is a very redundant set of storage. Meaning, it's going to be replicated to at least two destinations. So when I store something-- let's say this is, you define what's called an S3 bucket. This is just a storage area that's dedicated to you.


And I start putting some files in there. I am guaranteed that that's going to be stored, not only on one set of hard drives-- one set of servers-- but at least two of them. As in, as I write data to the S3 bucket-- store data in the S3 bucket-- it's fantastic because it's actually writing it to at least two places at once.


So let's call this storage destination one and storage destination two. And it won't return a success on my storage request until it's written to both places. OK, so here's what that means. Let's say I've got an-- let's just go crazy-- an MP3 music collection that I want to put in the cloud.


So I'm going to copy it to S3. And I've got BonJovi.mp3. As I copy that file into the S3 bucket, it's actually saving that file in two separate locations, and the file is not considered a successful copy-- as in whatever utility I'm using to copy that file to the S3 bucket-- is not considered successful until both locations say, yup I've got it.


Oh, the amount of redundancy, the amount of warm fuzzy feeling that that should give you is massive. But, S3, because of that, is a little slow. At least when you compare that to modern hard drives and RAID technology, and all the kind of set. So let me show you how it all started.


With Amazon, originally they only had EC2 and S3 storage. So you would create what would be called your instance, or AMI. And that would be stored in your S3 bucket. That is the actual image that your server users. So let's say you've got a Windows 2008 R2 image which acts as a remote desktop server.


So somebody can remote desktop and get kind of a virtual desktop up there, or fill in whatever use that server is, right. So you store the actual images of it there, but it doesn't run from there. It doesn't run from the S3 bucket, because S3 is pretty slow when doing write operations and so on because of its amount of redundancy.


So when you would launch that image, Amazon would actually copy that instance from the S3 bucket to what they call ephemeral storage. That's right, not even listed on this page is ephemeral storage. Because in your mind, think of it as like, this doesn't really exist.


Well it does, kind of, but let me explain. See, when you've got this image sitting in S3 storage-- again very redundant, very stable storage, but slow when compared running a server off of it. They say, well we can't run a server from there. So let's actually copy it to the physical server that's running this virtual instance.


Whew, there's a lot of stuff that just came in there. So let me simplify. You've got the bucket, S3, right? That's where your actual image of your server is stored. But we can't run it from there, so it's really slow. So what I do is I copy it to the actual physical server-- or servers-- that are running my instance.


And they're going to store it locally on whatever their hard drives are. We'll just think of it as-- it could be a RAID 5, who knows what it is. It's something that's very fast. It's actually running straight on that server. But now here's the big thing to think about.


Ephemeral storage, while it's quick, it's ninja fast, it's not permanent. As soon-- hear me, let's put this in slow motion. I know some of you put this on like double or triple speed when you're listening to me. Pull back, stop, go slow motion for this, because we want slow motion.


If you store something in ephemeral storage and you shut down that machine, it's gone. As in, everything's gone That was in there. So let's say I created a Windows 2008 R2 RDS server, and I made that run. It's now running as an instance on my actual physical server over here.


People are remote desktoping in. Somebody goes in and opens a Microsoft Word doc, types hello world, and saves that to their desktop. Which is literally their desktop is stored on that server. And then all of the sudden I go, well you know what, I think I'm done.


I'm going to go in and shut this server down just for a couple days because I don't need that server. As soon as I shut that server down, bam, it is deleted from the ephemeral storage. And now it's back to its original image-- the AMI image that's stored-- I mean the original template that I created that from in the S3 bucket. Oh.


So there's no permanent storage in the ephemeral storage itself. And that's actually how Amazon started this whole thing. There was no alternative, which I'm going to talk about in just a second-- elastic blocks. Or there was no alternative storage location.


As in, you had to really think this through. When you're running a server up here in ephemeral storage, it better be storing anything useful back to S3. It better be writing stuff to S3, because otherwise when you shut that server down, it's gone. Let's go back to what I mentioned in the previous Nugget.


That horizontal scaling, right. Amazon really is all about creating these little workhorses which are disposable. Bring up instances as you need them, and then shut them down and they are no more. They don't exist, because they write all of their data to this more permanent storage.


Well you can imagine. This bring it up and then proof its gone idea just didn't work for a lot of people. They go, I need something a little more permanent. But I need something a little faster than S3. And that's where Amazon came up with Elastic Block Store.


OK, let me clear those notes off. Just getting a little too much there. So Elastic Block Store-- EBS-- is a more permanent storage location that operates faster than S3 for you to save your machine so when you shut them down not everything is lost. OK, so hang on.


Let's regroup. Let's put these-- because we've talk about three storage locations for your hard drives. Let's put it all together, right. You've got your instance-- your virtual machine that you want to run. S3 is used when you when initially you start that virtual machine.


That's where the image resides. The beauty of S3 is in its stability. It's extremely stable. 99.99999% redundancy. Like, you're not going to lose data out there. Well, excuse me. Let me back up. I'm not saying don't back up your data. I'm never saying that, so never misquote me on that.


But when you're in S3, there's a 0.00001% chance kind of thing that you would ever lose data from S3, because it's so stable, it's so redundant. But the sacrifice that you get when you use that is that it's slow. Just because of the way that it's designed.


But that's where it always starts from. You've got your image-- it's called your AMI-- stored on S3. That's the actual hard drive image for this. And when you boot up that machine, when you create a virtual machine from that AMI, from that image, you choose whether you want to store it in one of the other two locations.


Which is the ephemeral, E-P-H-E-M-E-R-A-L. So someday I'm going to write, and it's going to go bloop, squiggly red underline, you can't spell it that way. But I'm assuming, I think that's correct-- ephemeral storage. Which means it actually takes that AMI from S3-- slow storage-- and moves it to the physical server.


There's a physical server somewhere with very fast storage locally on that server. It copies it right into that server and runs it from there. Beautiful because this is ninja speed. It's super fast, but what's the problem? You shut but down that instance that's running, it's deleted.


Meaning lose data. See now my own spelling is haunting me. Is that loose? That's loose, right? Loose. L-O-S-E. Lose data when you shut down that machine from ephemeral storage, and it's gone. Or you could choose to run it in EBS. Elastic Block Storage, this guy right here.


Which is just a small group of servers that will give you-- and let me put that right here-- EBS gives you decent performance. Now, everything that I'm saying as I'm creating this in the middle of 2012. So there's always going to be performance improvements.


It's always going to get better, faster, cheaper, that kind of thing. But it's going to give you decent-- and when I mean decent, if I could quantify that-- it's like your home PC. You're running it storage on your home PC, which runs on a single hard drive, that kind of thing.


Now it's more redundant than a single hard drive. It's better. It is redundant. But it's not as redundant as S3. That's why it's not as slow. So, decent performance. And it's not lost-- let me put not lost-- when you shut down the machine. And you pay for it.


Ephemeral storage, oh yeah, by the way, it's free. Well, it's included with the cost of what you pay for that virtual machine per hour. Because it's running on that server. You're not paying extra for storage. When you store it on EBS, Amazon has to maintain that instance when you're done, when you shut down that machine.


So you're going to pay money for that storage. Just kind of like S3 storage. You pay money for how much you store in S3. Is this, is this all kind of-- do you see how storage differences work for this? Oh man, I should just stop right there. That's such a huge concept that I want you just pause and chew on that for a little while.


OK, did you chew on it? Good. So that's how all this fits together. Now, there's so much more I could say about S3. S3's huge. You can host websites from it. A lot more to talk about, but this is just an overview of the services. That's what it is-- just a big old redundant, stable, slow storage spot.


And again, everything's relative, right? It's not slow like, wow, that's slow. So let's move on, let's see, what's the next one. I would say next, let me go with CloudWatch. CloudWatch is a service allowing you to monitor all of this stuff. There's a lot of different free flavors of CloudWatch, to where I can say, once every five minutes I want to know how much storage is remaining, how much processor utilization I'm running, what's my memory usage.


All that kind of thing. It monitors all this for you. Now, a lot of companies, a lot of organizations, are going to say, well, I want a little more frequent monitoring. I want if my storage goes below x percentage for even a second, I want to know about that.


So they start tuning the timers down. The lower you tune your timers-- like how often it's checking for those values-- the more you're paying for CloudWatch. So again, there's a free tier, which is good monitoring. But if you want to start getting to aggressive monitoring to where its phenomenal monitoring, that's where you're going to pay a little bit more.


Let's talk about databases. Amazon includes database services. They have a simple database. Which, and I would say, this is my prediction-- maybe by the time you hear, this it doesn't exist anymore. Simple database services is designed to be relatively small.


Kind of a slower access. Meaning you're not really getting super fast access, you're not getting a lot of storage out of there, but it's very, very low cost, and very simple to set up. The reason I'm predicting that maybe it's not even there by the time you hear this, is because it seems like it's starting to disappear from a lot of the documentation.


That tells me, OK, writing's on the wall. Maybe Amazon is saying, I don't think we want that anymore. So DynamoDB is very scalable. I mean we can be huge. Doesn't have limits on the amount of data you can store in there. You can pay more to guarantee the performance.


So you can get ninja speed out there. It stores a lot of the storage on solid state disks. So when I say ninja speed, I'm talking really fast. It's a great database service. But again of course, any time you're talking super ninja speed, you're talking about paying a little bit more.


OK. Let me clear off my notes again, and I'd like to fill in what we've completed so far, just so I don't get redundant what I'm saying. We talked about CloudWatch, we talked about SimpleDB, DynamoDB, EC2, we talked about Simple Storage, Elastic Block Service.


Ephemeral storage, which I didn't list because it's not really a service, it just kind of happens. That's how the instance is run. So now let's talk about Route 53. What is Route 53? DNS. That's so you can create name records for your domain. So Amazon will host those and allow you.


So let's say I create That is a domain, and I can host that. I can point it to Route 53 to manage all of the DNS records for it. So that allows me to create, which goes to XYZ location. It allows me to create maybe S3.CBTNuggets that goes to another server, another location.


So I can create all these different DNS records. And there's a lot to DNS. But Route 53 is just straight on DNS. Virtual Private Cloud. Whew, this one's killer. Virtual Private Cloud allows you to control the networking very closely of how EC2 works. So when you create instances, Amazon is so brilliant in how they design it.


Because they configure all the networking for you. They set up a firewall, they give your server an IP address, they map it to a public IP address. I mean, there's usually a lot an administrator has to think about when they're doing that. Well Amazon does it all for you.


They set up the firewall, they set up the routing, they set up all the IP addressing. But for some admins, they might go ah, it's a little too auto magic for me. I want control. I want to control what IP addresses I use for my servers. I don't want Amazon to do that for me.


I want to control what public IP address is mapped to what private IP addresses. And then, the big one. I want to be able to create a site-to-site VPN to the servers operating in the cloud. This is huge. So this gives you control of the networking. But here's, I would say, the biggest piece of this all.


Up here is Amazon-- AWS-- services. Down here is your organization. You may say, I want a site-to-site VPN. A permanent connection that is private, encrypted from the servers and the clients running in my businesses. That they would be able to access those servers from behind the scenes.


And I mean, you've got the rest of the world coming in from up here, which is all firewalled off. This is my little world right here. The whole world is coming in from right here, all firewalled off and restricted and all that. You could create a site-to-site VPN from your business up to the servers at Amazon Web Services.


So you can have full private access to those servers. However much access you want to define. So you can host services that way. That really makes Amazon Web Services feel like you own it. This is mine. I have full access to it. I have full control over all of these services.


And is fully accessible to where my business literally merges with the servers that exist up here. That's what virtual private cloud is all about. Man, that's powerful. OK, Auto Scaling Auto Scaling is a service that allows Amazon to add instances for you and take them away as you need them.


So you can define certain thresholds. Maybe you've got a bunch of instances that are running a website- supporting a website. And I can say, OK, as the load increases to 80% CPU, or whatever threshold you want for five minutes straight, whew, we're maxing out.


Let's add another instance. Or add a couple instances. Or you could define time frames. Well, between this and this hour, I want to make sure I boot up these instances to be available. That's considered Auto Scaling. Allows you to grow. Allows the system to grow with you as needed.


CloudFormation. CloudFormation allows you to define templates of servers. Hm. It goes beyond the typical EC2 server. With EC2, I can define my templates. For instance, I can create what's called an AMI-- which is just an image of a virtual machine. I can create an AMI of my web server.


W-W-W. I can create an AMI of my database server. I could create an AMI of let's say my Windows Server. Again, I could create all these different templates. So when I need to create an instance-- maybe for Auto Scaling-- I need to add another web server.


It says I'm going to add it based on this template. I can create all kinds of templates in EC2. But with CloudFormation, I can create-- get this-- a template of templates. So maybe I know to run a site-- to run a full blown site for my business-- I need it two web servers, a Windows server, and a pair of database servers.


Well I can create that using CloudFormation. Remember I was saying Amazon is designed into regions with availability zones and all that? I could say, to bring up a full blown system that includes everything that I need to run my company in a different availability zone, or a different region in Amazon Web Services.


I've created this CloudFormation template. Now the cool thing is, all kinds of people have created CloudFormation templates that are publicly available. And some of them are free. Some of them you can pay for. You can say, hey, I want everything that I need to run a Wordpress site.


Or I want everything that I need to run an e-commerce store. Or I want everything-- and so you can go out there and people have pre-configured CloudFormation templates to say, OK, well then you need these three servers. Go in and click the button, and bam, immediately you've got an e-commerce site.


So very powerful stuff that you can do with CloudFormation. Identity and Access Management. IAM is the ability to create credentials. All kinds of different credentials that are used to access your systems. You can have I'll say a simpler style S3 bucket name and secret key.


Kind of like a username-password system. You can have a more advanced public key algorithm system. We're going to talk about these in the future extensively. You can have even token based, where somebody has a little keychain or an iPhone app that generates them a token that they can use the login for one time only, and then that token expires and can never be used again.


So all kinds of ways of managing access to your system. That's IAM. Last one-- Elastic Load Balancing. Whew. Are you feeling like you're drinking from a fire hose or what? I feel like I'm a fire hose right now. Because I'm giving you just like the tip of the iceberg.


There's so much more that we can talk about with these. But again, this is just an overview so you know what it's capable of doing. That's really the big picture. So Elastic Load Balancing is the ability to bring up these servers. Let's say I've got four web servers that I just brought up, and I want to load balance between all of them.


That's what a Elastic Load Balancing can do for you. So magically, Amazon can create an ELB that says, for incoming requests to your website-- and I'm using website as a generic. It could be to your remote desktop services, to your FTP site, to your bleh, fill in the blank.


For requests coming in from the world out here-- here's the internet-- it will hit this Elastic Load Balancer, which can send it to that server, and that server, and that server. Or maybe you do a round-robin to where that one, that one, that one. Or maybe you do a percentage, to where 50% of the requests go here, another 20% go here. You can define how it load balances.


But Amazon does that for you with Elastic Load Balancing. Oh. Want to collapse. Man, just that transition from the services-- that's just the core services that are available to you. I just want to kind of-- I just want to breathe. But oh, can you get the vision of why I wanted to cover those? Now you have enough knowledge to go, wow, that's what I can do with Amazon Web Services? And that's just the tip of the iceberg? Wow.


Now I can sit down and start planning, and really thinking through what's capable here. What I can design this to do for me. OK, now, the last thing I want to talk about here-- because again, we're going to spend the rest of the series really diving deep into each one of those and talking about what's possible.


Let's talk about how to do this for free. Really? For free? Yeah, for free. Now I put this-- I copied this straight from this URL here. Http:// Because I wanted to show you this is what's free as in mid 2012, because Amazon's always doing more.


As in, they didn't even used to allow you to run this for free for a year. But now they really do. So they may even be adding more and more and more and more that you're able to do for free. Amazon is so confident, that when you sign up and really start rolling this thing out, that you're going to like it so much you're going to stick with it.


So they give you the ability to do almost everything that I talked about on the last slide for free. As in, this so what you're able to do. You can run 750 hours of Amazon EC2 Micro Instances for a year. That's enough to run continuously each month. And they put a little star there.


It's just saying, hey, we're talking about running one instance at a micro level. Now a micro level, it's slow. I'm not saying that's a mean machine. But it's free. I mean you can kick the tires, you can do just about anything that you want with this thing for free for a full year.


You know, five gigabytes of storage. Again, is it a ton? No, it's not, but it's enough to get started. It's enough to run for free. You get Windows licenses for free. I mean, a Windows Server license-- if you were to go on and say, buy a Windows Server


license, I mean you're talking about thousands of dollars, that they're giving you for free to run this thing every single month. So this is powerful. You can go through and start exploring this. Right now. Go, sign up for an account and get going. But I want to answer this question.


What happens if I go into a paid tier? How does that work? So let's say I'm running my micro instance, and I'm like, OK, I want to make this a little more. I want to upgrade that to maybe a large instance. So a runs a little bit faster. A little bit, a lot faster, for me using a real server.


What happens? Well, immediately you now go into paid services. It's a paid tier to do this. And you're going to be charged hourly for that large instance. I'm not going to throw the rates up there because they-- literally, Amazon has lowered the rates. What is it, like nine times over the last couple of-- I mean just an insane amount of times.


So check the rates of what that large instance costs you. Maybe it's-- we'll just say $1 an hour, right. $1 an hour. So you convert that server to $1 an hour. You're going to be charged $1. So I go in and say run it as a large-- let's say I run it for 10 minutes. I'm going to be charged $1. Even though I didn't use the rest of the 50 minutes. Maybe I used 59 minutes. I'm going to be charged $1. As soon as I go to 61 minutes and I go into the next hour, I'm being charged $2. So the big warning I want to throw out there to you, is think this through and make sure that you shut down anything that you're not using.


It's very easy to say, OK well let's check this out. Let's run a large instance. And you keep it running, you forget about it because you test it, you're like, oh that's pretty awesome, I like it. You close it. You close down your browser window. That large instance is running behind the scenes.


You forget about it right? Days go by. Two days, three days. So you move from $1 an hour to now OK, you just ran that for a full day-- 24 hours-- that's $24. OK, two days. OK, that's $50. Wow, OK. If you're signing up on your personal credit card, and you forget about this, it's not good.


So you want to make sure that you remember that you are running this. As soon as you go beyond that free charge-- the free tier-- you are going we charged for this. And that that's something to be very aware of. So please heed my warning. That's why Amazon has you put in your credit card.


It's very easy for you to say, well let's try kicking the tires on a large instance, or an extra large instance just to see how this thing really performs. They want to give you that flexibility. But oh man, think that through. If your credit card is on there, and you just keep that instance running beyond your testing period, that could end you in a world of hurt.


So make sure that you-- we're going to be doing, as we go through the series, of lot of examples. A lot of what I would call labs to set this thing up. Definitely do them with me. Use the free tier as much as you can. But if you want to go beyond, be warned, don't keep it running.


So we have seen in this, what you need to get started with Amazon Web Services. Again, signing up for an account. Credit card, telephone number, verification calls, verification emails, all that kind of stuff. I went through the meat of this, which was the Amazon Web Services-- what I would say, core services-- to get you started.


Services that almost everybody would benefit from. But know that there are more of them out there. We'll talk about those, again, as we continue on through the series, I'll splice them in here and there. And then we talked about what can I do for free, really? I mean what.


And if you look at it, that last slide, there's a lot that you can do. They give you a ton that you're able to do for free without getting charged. Amazon is that confident in what they're able to provide for you, that they're saying, try it out for a year and see how it works.


So a lot that you're able to do. So I would say right now, that's enough for you to just sit back you go, OK, let me write this on paper. Let me make sure I really get what we're talking about here. Get into Amazon, get into the management console and see what that's all about.

EC2: Creating an EC2 Instance - AMI Selection

EC2: Creating an EC2 Instance - Pricing

EC2: Creating an EC2 Instance - Instance Types

EC2: Creating an EC2 Instance - Tags and Key Pairs

EC2: Creating an EC2 Instance - Security Groups

EC2: Creating an EC2 Instance - Elastic IPs and ELB

VPC: It's MY Cloud Now! Understanding AWS Network Management

VPC: It's MY Cloud Now! Understanding AWS Network Management, Part 2

VPC: It's MY Cloud Now! Understanding AWS Network Management, Part 3

S3 Foundations: Getting Started with S3

S3 Foundations: Working with S3 Storage

Route 53: DNS Management Made Easy

IAM: Creating and Managing User Access

AWS Case Study: CBT Nuggets Move to the Cloud

AWS: Series Wrap-up

Please help us improve by sharing your feedback on training courses and videos. For customer service questions, please contact our support team. The views expressed in comments reflect those of the author and not of CBT Nuggets. We reserve the right to remove comments that do not adhere to our community standards.

comments powered by Disqus
Entry 8 hrs 18 videos


Basic Plan Features

Speed Control
Included in this course
Play videos at a faster or slower pace.

Included in this course
Pick up where you left off watching a video.

Included in this course
Jot down information to refer back to at a later time.

Closed Captions
Included in this course
Follow what the trainers are saying with ease.

Files/materials that supplement the video training

Premium Plan Features

Practice Exams
These practice tests help you review your knowledge and prepare you for exams.

Virtual Lab
Use a virtual environment to reinforce what you are learning and get hands-on experience.

Offline Training
Included in this course
Our mobile apps offer the ability to download videos and train anytime, anywhere offline.

Accountability Coaching
Included in this course
Develop and maintain a study plan with assistance from coaches.
Jeremy Cioara
Nugget trainer since 2003