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

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 Key Pairs and Security Groups. Well, my friend, we are well on the way to getting our instance up and running and really understanding all the pieces around it. And I felt, as I went in to start this Nugget, I go, we got to just get our bearings. Because, even as I say that, we're well on our way to get our own instance running, I'm sure many of you have already gone out there and gone Next, Next, Finish.


And you're, like, well there it is. It's not that hard. I've got a running instance. Absolutely, you can have a running instance in a few minutes, if you just Next, Next, Finish it. But really kind of putting together all the pieces, so I want to make sure we don't get lost as to where we are on the concepts.


I'm going to bring over the EC2 Management console. And I'm in the Instances area. I've got, right here, just a little Linux instance I've got set up this morning, just to play around. But I wanted to bring up the instances-- let me just click on Launch, and this is just to get our bearings.


Now we went through. We talked about what it looks like to go through the wizard, going through the AMIs. What is an AMI? The frozen in time hard drive? Where do you get the AMIs? Creating your own AMIs, the community, the marketplace, all those kind of things.


We went through and figured out how to get an instance going. So I'm just going to grab, let's grab Windows 2008 R2. We talked about how many instances, the types of instances, the processor size, the memory, how you scale that. Not even shown here, the I/O that's included with each one of these instance sizes, and why that's impactful.


We talked about the availability zones, the regions and what that is. We looked at the pricing, all of the different pricing that we could do for on-demand versus reserved or versus spot. Whew. Even as I do this, man, we've talked about a lot. But it's so easy to just, Next, Next, OK.


I've got it. It's good. But now you really understand all these pieces. So let's see where we go from here. If we're going into the Advanced Instance options-- I'm going to put those to the end, right? Just because it will just make more sense if we talk about those at the very end.


I'll say, this is a great one, prevent against accidental termination, to where you have to come in and uncheck this box before you can terminate an instance. Because it's all too easy to blow one away accidentally. So, continuing from there, let's pick up here.


That was my bearing check. We know where our instance is. We know what kind it is. We know EBS storage. We know all that kind of stuff. So now we're into the tags. What are tags? Tags are just a way for you to identify your instance however you want. It is kind of a free format, think of it as a micro database that you can use for each instance to describe it.


So when you're looking for certain instances, you know what they are. And I would suggest, it's all too easy to just say, well, let's add my own tags and just make them up. But I would suggest sitting down with your IT group, unless you are a one-man show, or a one-woman show, then sit down and say, hey guys.


Let's agree on what tags we're going to use to describe each one of these. Let's come up with some common syntax. Because if you look, these keys, these tags, the key values, can only be 127 characters. And the value can only be 255. So it's not like we're having a big paragraph here on everything that this instance does.


So, for instance, this is-- I'm creating a Windows 2008 R2 instance-- Let's say the name of this is SDCORE-TS01. And I'm actually a naming convention that I use for my own data center. SDCORE, to me, says the name of my company that I work with, Core. Core is the data center.


TS stands for the function. I use, for instance, TS is terminal server. Or I might do a DC for Domain Controller or FS for a File Server. I've got my own key. And then 01, this is the first terminal server that I have at the data center. So if you never had a naming convention, Bam! There it is, in two seconds or less, a naming convention for you.


So that will be a name that can now appear-- you can see it, kind of behind the scenes here-- see this little name? I didn't put any tags in this one. So it's says, Empty. That's not very descriptive. But I don't have to just stop at the name. I can go in and say, well, let's add a description.


Description will be, and again, 255 characters. You don't have much. Let's just say, RDS Gateway to reach internal apps. I'll just say internal servers, how's that? And you can keep adding another tag and another tag, as many tags as you want. And let's just say, Creation Date.


It is, what's the day, 5/25/12. And go on. And you can see up to 10 individual tags that you can use. Now I'm going to show you this in a minute. I'll show it to you in a minute. I'm going to click on Continue. Save those tags. Because I want to now get into the key pairs.


So let me pause there and flip over to the concept. What most people do when they get to the key pairs on their EC2 instances, they kind of-- well, actually, let me show you-- they usually come into here and they go, OK. And by default there is no pair. This is just a pair that I created previously for my Linux instance.


They come in here and it says, create a new key pair or proceed without. And people go, let's not do that. And then it says, oh no. You can't connect to this instance unless you do that. You go, oh, OK. Then let's do this. OK, I'll type it in. Duh da duh. And they create download.


But they're just kind of going through, not really understanding the power of what they're doing and the power of what this really is. This goes back to public and private key cryptography. And I always, I could give you the, OK. Type this, and then go here and do that.


I mean, you can Google that and find it. But to really understand the why behind it all, it's just, that's satisfying. That's where you are, Oh, I get it. So understanding public and private key cryptography is huge. Because it's really how almost all the secure communication in the world works.


This all goes back to decades ago, when there was an instructor, a college professor, and his student named Whitfield Diffie, that was the student. And, I believe, was Martin Hellman, was the-- Martin? I think was Martin. Hellman was the college professor.


And so these guys were-- and this is decades ago-- they were sitting there, trying to figure out, how do you have secure, encrypted communication, across a public network. Think about it. You're right here, right? Sitting at your computer. And something that almost all of us do nowadays is do online banking, where we can go and transfer account balances, make payments, online bill pay.


So I don't have to mail it in the mail and all that. So it's very convenient. But in the middle of all of this communication is the public internet, with evil people, who are trying to steal your bank account balance, and trying to steal the ability to transfer information.


So I need to have some kind of secure, encrypted session between these guys. I have to have something that secures it. So these evil people in the middle of the cloud can't find it and see it, and be able to get to my bank account balance and all that. And they're going, OK.


Well, how-- think of this. I mean, college professor, student, sitting there looking at each other. OK, how do you do that? I mean, back then encryption keys were very common, to where you would have a key. And a key-- I'm visualizing it here as a key, but it's a mathematical formula that really scrambles data-- So let's say I want to transfer $150 from my checking to my savings account or something like that.


Before I send it, it runs it through this encryption key, which just is a big mathematical algorithm that goes bluh bluh bluh bluh and scrambles it all up, to where you can't understand it. Well, the person who has that key can also reverse that, to figure it out.


So to do encrypted communication, I would have the online bank have the key. And I have the key. And then we just kind of encrypt it between. It's like, oh, well, that's simple. But how do you get the key? Oh yeah. Forgot about that. How do you get the key? How do you get the same key that the bank has, so that you can encrypt it, without the guy in the middle getting it, too? I mean, you can't just have the bank send you the key.


Do you see this dilemma? So Martin and Whitfield were sitting there, they're like, how do we do this, how do we do this? And the way the story is told-- and you can go look this up in Wikipedia if you want. Actually, I don't know if it's there, maybe it's there--- the student, Whitfield Diffie, was at home asleep.


At 2:00 or 3:00 in the morning, wakes up in a cold sweat, and goes, I got it. I know it. I've got the-- he dreamed the algorithm for what we now know as the Diffie-Hellman public key encryption algorithm, to where you now have, instead of one key, two keys to start your communication , a public key and a private key.


So I'm going to show you how it works across the internet. And then I'm going to apply that same mindset. Well, it's actually much simpler when you look at it from an EC2 perspective. But understanding kind of the big picture, this is an impress your friends conversation, seriously.


They're going to go, wow. Really? So here's how it works. When my computer connects to the online bank-- let me flip colors here-- connects to the online bank. It says, OK, this is going to be identified as a secure channel. The way that works is the bank, their web server, says, I'm going to send you a security certificate.


Ah, certificate. Some of you may have seen that before when you're surfing the web and it comes up and says, hey, this certificate is not valid. Do you want to proceed? And everybody is like, eh, don't show this to me again. And hit yes. Well, it's not good to have an invalid certificate, because everybody should have a valid certificate saying, this is who I am.


And this certificate says, this is my identity. I am the Bank of Arizona. I have this level of encryption. This is the date and time I got this certificate. And I've got-- you might go, what's that little squid on there-- it's a stamp. There's actually something called a certificate authority out on the internet.


VeriSign is a big one. Many different certificate authorities that, before this bank goes into business online, they go to the security authority and says, here's all our information about our business-- not all of it, but the requested information-- so you know that we really are the bank.


Because it would be horrible if somebody pretended to be the Bank of Arizona. As a matter of fact, that's called a phishing attack, when you get those emails where it's somebody pretending to be eBay or Amazon or something like that. It's a phishing email, somebody trying to pull the wool over your eyes, to get you to type in values over there, so they can compromise your data.


So we need to have these certificate authorities on the internet that says, OK. This is really the real one. That's why it's so scary if somebody sees that message that says, this is an invalid certificate. Do you want to proceed? And people go, oh yeah. Because a lot of times people don't pay the money to have a certificate really validate their identity.


So you're playing the game, like, I really hope this is the real Amazon, the real eBay, the real Bank of Arizona. So if you have a certificate authority give one to you, then it's validated. The browsers won't pop up that security warning and that kind of thing.


But also on here and here's the key-- no pun intended-- the key of what I'm trying to say, is the bank's public key. That's why it has that name. A public key is available to anybody. And it is, you can think of it as a full encryption/decryption algorithm.


It can encrypt, it can decrypt data. However, it is only a one-way encryption. Let's start putting these pieces together here. If I encrypt something with that public key, that key cannot decrypt it. It must be decrypted with the private key, which is the reverse of the formula.


Let's talk more about that in a second. So let me finish the story here. You connect to the bank. They send you their certificate, which includes, this is who I am. I'm valid. I'm not a fake. And here's a public key, a mathematical algorithm, that we can use-- or I should say, that you, little computer-- can use for encryption.


Now, notice I said, encryption, not really decryption. But this computer, your browser, Internet Explorer, Firefox, Chrome, whatever browser you're using, built into it has a certain level of encryption. And based on where you are in the world, there are some governments that say, well, we want to be able to see what you're doing.


So they may block the ability to use really high encryption versions of this. They have very low encryption values and things like that, that they allow. So, based on the browser that you're using, let's just say you use 129-bit encryption. Lets just say, I'm using Chrome.


Chrome will then generate what's called, your session key, which is just a key. It's an encryption, it's the old school, the original. One key to rule them all. It is an encryption/decryption algorithm that you and the bank will use for your session. OK, whoa, whoa, whoa.


Wait a sec, Jeremy. This got weird. I thought you said, the public key did encryption? I did. But we don't want to use that for all of our communication. Because then I've only got half of a formula. I can encrypt stuff, but I can't decrypt stuff with it. So what my browser does is generate a one key to rule them all encryption session, encryption key, and encrypts the encryption key.


Really? Yeah. So it takes the public key from that certificate and encrypts this encryption key, which it then sends back to the bank. The bank gets it and says, OK. I'm now I'm going to use my private key, which it never, ever, ever sends to anyone. That thing is hid in a way.


It's the banks. It never sends that private key to anyone. Because if it did, oh my goodness, it would compromise the whole security. Because whoever got that, that evil person in the middle. If they got the private key, then they could decrypt all these session keys from the users coming back in.


So you never send the private key. So the bank gets that encrypted session key back, decrypts it, and now-- I got to use a new color for this. This is so cool-- and now, both sides have a session key that they can use for their communication. And that's what they actually use for all of the communication between those two for that session.


That's why they call it session key. As soon as you close your browser, it's done. The session key is deleted. The next time you connect, you get the public key. You regenerate a brand new session key for the session. Wow, isn't that a cool-- that's how it works.


That's how all the communication works on the internet. Now, I said-- I shouldn't say all the communication. All of the secure communication that works on the internet-- now, I said the EC2 side of things isn't that bad. Because we don't really need a session key.


They use the idea of public and private key cryptography in such a way that we can use it to retrieve our passwords or to log into a system. So let me explain. I'm going to hop back to the instance I was just creating, right here. So we got to the point, we went through and defined all the tags.


Great. Let's continue. Please. There we go. And it says, do you want to choose from your existing key pairs or proceed or create a new one? Now, normally if this is the first instance that you create, this will not be here. So I'm going to create a new one, as if I hadn't done that before.


So let's just call this CBTPair2. As just a simple identifier name, might name it after your organization or whatever the case may be. But that pair is being assigned to this virtual machine. So I'm going to click, Create and download the key pair. And what it's doing-- kind of happened down here below-- you can see it downloaded, CBTPair2.pem. I'm going to go-- well, and now we're into the security groups, the firewall, which we'll see in just a second-- but I'm going to show in folder.


Let me, wow. There's all my downloads. If you want to see what I've been downloading lately, you can check that. But right there is the CBTPair2. Now, if I right click on that and open it, edit it with Notepad-- where's Notepad? Let's try that again. Oh, there we go.


It was just taking its time-- so right here is the RSA private key. This, if you ever wonder, well what is that mathematical formula, that's it. Well, that's actually the key for the mathematical formula right there. That is the private key. So you have just been given-- with what you now know about how web security works, that's a big deal.


Amazon just gave you the private key for your system. Save it. You need it. They maintain the public key. So let me finish going through-- I'll do the security groups in just a second. Let me just go through and launch this machine. So it's going to just go through and start building that machine over there.


There we go. So it's loading up. I can already see my name right there. But I want to right click on this guy-- what was I thinking for a sec. There we go. I totally lost my train of thought for a second. I was thinking about what was in my download folder-- so we've got the two machines.


We have a Linux instance right here. This is Ubuntu Linux. And then, right here, I have my Windows instance that I just created. It's actually generating. So it's going to take some time, usually about 10, 15 minutes before that thing is fully ready and ready to rock. So while we're waiting for that to load, let me jump right here to how the key pairs are used for Windows instances and for Linux instances.


What happens in the Windows world is we, as we generate the machine, get the private key. It's sent to us by Amazon. It's downloaded. And that is something you want to hang onto, you want to save. Because once that Windows instance is ready, you need that to get the default administrator password.


Meaning, let's flip back here. I have this instance that's currently initializing. If I right click on here, there's an option that says, get Windows password. Now it's going to give me an error saying, hey, you can't do it. Wait at least 15 minutes before you try to retrieve the generated password.


But once you do, you're going to see it bring up a window-- and, actually, let me, I'm just going to camp out and wait. I'm going to check my email and then come back-- I'm back. Checking email, bad idea. An hour later, here I am. So I've got the machine sitting right here.


It's generated. It's been running, waiting for me. So I now can right click on it, hit Get Windows Passwords. Now, when we're talking Windows systems-- let me get back to my slide here-- when I'm talking about Windows instances that are running, the key is definitely critical, but only really critical initially.


You need it to get the default administrator password. And then, once you get in, then you can change the password to whatever you want. For Linux, the private key is actually how you will authenticate from here on out, unless you start creating different user accounts and things like that within Linux.


So, I would say, of course you need it for both of them. But Linux, it's definitely got a more ongoing purpose. So right here is the encrypted version of my Windows password. It's saying, after I put it through the public key, I have this little blob. I believe that I can decrypt that using the private key called CBTPair2.pem. Do you have that? Now, there's a couple ways I could go about this.


I could either go in there and actually copy and paste this whole private key into this little box and tell it, this my private key. Or a little easier is just to go in and-- let me just find it, CBTPair2. Open-- and you can see, it puts the private key right in, just as if I would have copy and pasted it.


And I click Decrypt Password. And bam, there it is. I now have my decrypted administrator password. Now I can pull up Remote Desktop Connection. Let's go in and highlight this name. That is now my name that I can connect to. Paste that in here and connect.


Voila. It comes in, says, what username. Well, the user, it says, is administrator. And my password, vndzy!7avp It says, hey. well, talk about certificates. Even Remote Desktop uses a certificate. Look at this, Hey. This is just, what a great way to talk about what I just described on the public key.


It says, this Certificate is Not From a Trusted Certifying Authority. That's OK. Because if we had to go buy a CA certificate for every Remote Desktop Session we wanted. it would get a little costly. So I'm going to click on, Yes Accept that Certificate. And I am now in.


Now, the first thing that I'm going to do as an administrator is get into this Windows Server 2008 instance and go to my Windows Security and change my password. So I would type in the old password and then the new one. And then I'll say, not that I wouldn't care anymore, but I don't really need that private key anymore.


Because I already have the password changed at that point. So now let's talk about Linux. Linux has the ability to authenticate users based on solely the private key, a little different than what we just did with Windows. With Windows we went in and used that private key to figure out the password and then logged in with username and password.


With Linux, you can get in without a username and password at all. Just the private key can get you into Linux. Now, actually using the private key with Linux is a little bit more difficult than with Windows. Because Windows you don't really use it, at least not for Windows itself.


You just kind of use it to figure out the admin password. And then you chuck it. You never really use it again, after you change the admin password. But, on the Linux side, it's part of the authentication. When you get the PEM file, you didn't really get a private key.


You did, but it's like the meat-- you took off all the packaging-- there's the meat of the private key. I'll chew on it right there. But with Linux you actually have to take that and generate it into a full-blown private key. And to do most-- you can go on Google and find a million step by steps to do this.


I just grabbed one for OS X, if you're using a Macintosh. First thing that you want to do is get your EC2 command line tools. It's a little package of tools that will compress files, tools that you can download. Unzip those. And you use this command right here-- ec2-add-keypair-- and then you say, pstam.


This is just a name. Whatever you want to name the key pair, you put in there. So they have a great output right here, showing, I type that in. It says, OK, key pair such and such. And that's where, right here, you paste that private key, the meat I just showed you, into that, which ends the private key.


And now that generates a key that you're able to use to get into your Linux instance. So let me scroll down a little bit. This is, again, using OS X. They go in, and just it shows using some more of the EC2 command line tools to list the images that you have and see what images are in your account from the command line.


So, we haven't even gotten into the command line tool. We're doing everything through the AWS Management console right now. We'll get there. But this is just a sneak peek of what's to come. So they do some other things. But, by the time it's said and done, this is where the glory happens.


It says, I'm now going to SSH, into my instance. I'm identifying the key pair of RSA-- this is the key pair that we generated way up here with this pstam-keypair-- so I'm saying, use that key pair to access the root account of blah, blah, blah. And that's the actual name that Amazon would give you when you generated your instance, to access it.


And that's where you can now get in. You're now accessing your virtual machine, using SSH from a Linux prompt. And you can get in and-- if you want to, you can go into the SSH area and add user accounts, so you don't have to use that key pair every time. And maybe just use that for initial access, like we do with Windows.


So, now let me answer this last question. What if I lose my key? Well, let's talk through that. If you lose your key-- first off, on a Windows side, let's say, you generate the instance. You never change the admin password. You forget the admin password-- and I'm coming up with a hair brained scenario here-- you just always use that PEM key figure out what the password and paste it in to access it via RDP.


You lose the PEM file, so you can't get your password. Now, first and foremost, Amazon cannot get it for you. They do not keep the private key. They send it to you and they say, that is your responsibility. Hang onto that. So if you-- I'll say it in both. Windows and Linux.


If you don't have the admin password. And you haven't changed it from the original. And same thing with Linux, if you just lose that PEM file, that's the key to generating your private key to access it. You're locked out of the system. The short answer is, go in and terminate your instance.


And you'll create a new one. But maybe you're at the point where you've gone in, you've got-- let me bring my AWS Management console back up here-- you've gone in. You've got some actual data in SDCORE-TS01. And you're, like, Ah. I can't lose that. I don't just want to terminate the instance.


Well, the good news is this. I mean, it's either an ephemeral or it's an EBS storage. Most of the time, people run it from EBS. You can see right here, the root device. It's running off of EBS. So the hard disk, the contents are still there. What I would suggest is this.


Right click on this guy and create an AMI image. And by the way, this is great time to talk about this. If you haven't created your own AMI, this is how you do it. I can say, the image name is, let's just say, SACORE-TS01. Backup. I can't get in there. And you could put a description.


No Reboot. Select that. Hit Yes Create. And what it's doing is, it's now creating an AMI behind the scenes. Now, remember, when we go in and create a new instance, I can click on the instances and choose-- let me see if I can launch a new instance with this going.


See if it shows it there. Ah, no it doesn't. We've got to wait for it to finish-- so it's creating an AMI instance. So you see where I'm going with this? You're going to want to go and there and now generate a new instance from your frozen in time AMI. At that point, you'll be able to use a new private key, generate a new private key, and get into that system.


Now, a lot of times when you do this, to some services won't be started. You'll have to manually go in there and start the services. Some of your disks may not be mounted. You may get in there and go, oh, I only see the C drive. Did it lose everything? Go into the Disk Manager in Windows or use some mount points in Linux to mount the disks back in.


And all of your data should still be there. I shouldn't say should, it will still-- it's not like Amazon just loses data-- it will still be there. You just have to mount it all back up and get into. So, all is not lost if you lose your key. But it does definitely cause a hassle.


Well, that's enough fun for now. I want to put a dividing line there, so I really have the time to expound on security groups. There's a lot to think about when you're setting them up. So we talked about, in this Nugget, tags. And, actually, there's something I totally forgot to show you.


But I was going through defining the tags, and you're probably, like, OK. Well, that's great to see them. But where do you actually use them? Where can you find them? Well, you remember for this SDCORE-TS01 virtual machine right here, or instance, I actually defined the tag of, I think, the Creation Date and things like that.


You can go up here to the Show/Hide button. And that allows you to add your own tags to this list. Let's add them all in there. I click on All of them. And now I can see, if I expand this out-- now I'm obviously running a little out of room here-- but now I can see all of the custom tags that I've put in there.


And I have seen, sometimes when you put this, it shows all empty until you click the Refresh button. So if you do this yourself and nothing shows up. Click refresh. And it will show up for you. But that's your nice way of doing it. And now you can filter on them.


You can search for them. They're part of your image list here. So that's a really powerful tool. So we talked about tags and adding those to your instances that are running. We also talked about EC2 key pairs and all of their glory, to talk about what the key pairs are.


We even talked about public key/private key cryptography and the mindset behind it. And then how we applied it to Windows instances, to Linux instances, what happens if you forget your key, all those kind of things we went through. So, in the next Nugget, we will talk about security groups.

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