EC2 & Getting Setup

10. The AWS CLI - Using Credentials

So here I am in the AWS console, and I'm just going to go over to EC Two,and I've currently got an EC Two instance running. What I'm going to go in and do is just terminate that. Now just go ahead and hit Terminate because I want to start from scratch. And what I'm going to do now, I'm just going to go ahead and launch a new instance. Okay, so I'm in my terminal window right now, and what I'm going to do is just type in SSHEC Two user at, and then the IP address, thenminus I, and then my easytwokeepair PM, and it's going to give me this warning message. It's going to go ahead and hit "yes. And there we go. So now that we've connected to our ECTwo instance, please elevate my privileges to root. And now I'm just going to clear the screen.

So I'm in the EC two user directory. And what I want to do now is try and use the AWS command line. So we invoke the command line just by typing AWS, and then we select the service we want to use. So in this case, we're going to look at SThree, and then we're going to type in LS. So we want to see all our buckets. S Three, I'm going to hit Enter. But of course it says "Unable to locate credentials." You can configure credentials by running AWS configure. So that's exactly what we're going to do now. Our AWS configuration is going to ask us for our access key ID and our secret access key. So you need to go over that CSV file that you downloaded. Okay, so here I am in that CSV file. If we just go over, we can see that it says Access Key ID. So you just want to copy and paste that and put that back into your terminal window. So access the key ID. There we go. And our secret access key is the next one along. And just go ahead and copy and paste that into your clipboard and then put that back into your terminal and hit Enter. Now the next thing it's going to ask you for is your default region name. If you don't know which region you want,just type into Google something like "AWSRegion List" and select this link here. So, AWS regions and endpoints And of course, I'm in London right now, so I want to use the one for EC Two for London.

And you can just scroll down and grab it from here. So make sure you use regions. And you've got to copy and paste this specifically, so it's EU West Hyphen Two. You don't want to confuse it with things like availability zones, for example. And so just go back over to your terminal window, paste that in, and then just hit Enter again for the default output format. And then hopefully just go to clear the screen, but hopefully that will work. So if we type in AWS, S3, LS, we now have a list of all my buckets and I can see all my buckets from around the world because S3 is global. So I can see my buckets in London. I can see my bucket that sits in Sydney, that's hosting a cloud front site, etc. Now if you want to know what each command does,type in AWS the service and then you can just type in Help and it will give you a list of commands and you can scroll all the way down. My monitor is not very good in terms of being able to view right now because I make my text really, really big. So you guys can actually see what I'm doing. But if I scroll all the way down, it says available commands. So we've got CP, which is going to be copyLS, which is to list a directory, MB to make a bucket, MV to move things around, etc. Etc. So you can hit CTRL C to come out of that. Okay, so let's look at where these credentials are being stored. So what you do is type in CD space and then tilde and that will take you to the home directory. And then in here, if you just type LS, you'll see that there's no directories,but that's because there's a hidden directory. So type in CD AWS and then type in LSand. You'll see two files in here, config and credentials. So we type in our Nano credentials and hit enter. You'll be able to see your access keyID and your secret access key here.

Now it is being stored locally on your EC2 instance. So what does that actually mean? Well, I've got port 22 open to the world right now, and if somebody got a hold of my private key, they'd be able to SSH into my EC2 instance and then they'd be able to get mycredentials just by going to the home directory, going to AWS, and then opening up this file. And with these credentials, I can install the command line on my PC, laptop, or physical device anywhere in the world, and I can even access my AWS account. So if you lose these credentials or somebody steals them, they can go in and start provisioning hugeEC two instances to do things like bitcoin mining. And what a lot of developers make the mistake of doing is storing these credentials in their code and uploading their code to GitHub. And essentially, there's automated software out there that scansGitHub all the time looking for AWS credentials, because as soon as they've got them, they can go in and access your AWS account. For that reason, credentials are not all that secure. So if you are using EC2 and you want to be able to make command line calls using EC2, there's a more secure way to do it and that's called Roles, and we're going to go into that in the very next lab. So what I'm going to do now is just go out of this and go CTRL X. I'm going to clear the screen. Now what I'm going to do is make this EC Two instance self-destruct. So to do that, I need to get the instance ID. So type in AWS EC Two, then describe and then type in instances. And this will describe all my instances that are currently running within EC Two. It will also describe terminated instances. So if I scroll all the way up,you can see here it's in JSON format. So you can see that the first instance is terminated, and if I scroll down, I should be able to find my web server. Here we go. Just scroll up.

You can see it here. You can see it here under the state it's running. So this one is live and I've only got two EC2 instances running. And you can also see my public IP address here. So I'm just going to grab the instance ID, which is this one here. I'm going to go copy and then I'm going to clear the screen again to make it easier to see and I'm going to type AWSEC Two, terminate instances, and then instances. I think it's instance ID. It might be instances ID. Then paste it in here and hit Enter. And there we go. I've just terminated the EC2 instance that I was running the AWS command line from. So it has basically self-destructed my EC2 instance. So why don't you go back to the AWS console? OK, so I'm back in the AWS console. Just go over to EC Two and make sure I've definitely terminated that instance. And you can see it is shutting down. Now the very last thing you should probably do is just go back to IAM and delete thatuser because it's a massive security risk. I try not to use users for the command line wherever possible, but if you are using it on your laptop or on your desktop or anything outside of AWS,then you will need a user with programmatic access. So I'm going to click in here and I'm just going to go ahead and hit Delete users. And it will say the following user will be permanently deleted, including all user data. Hit Yes, Delete, and now that user no longer exists. And now my AWS account is secure again. So if you do ever accidentally upload your code to GitHub and it has your access key ID and secret access key, that's the best. The only way to really resolve the issue is to go ahead and delete the user and recreate a new one. Or you can go in and regenerate the access keyID and secret access key, but you should do it immediately because it is a big security risk. Okay, so that's it for this lecture, guys. In the next lecture, we're going to look at how we can get away from using user accesskeys and move over to using roles. So if you've got the time, join me in the next lecture. Thank you.

11. The AWS CLI - Using Roles

Okay, so I've logged into the AWS console and we just want to scroll down and go into IAM, which is under Security Identity and Compliance. So click in there and then we'll go over to Roles. Now you may remember in section three we created a role called "S Three Admin Hyphen Access." And if you haven't actually created that, don't worry, we'll go ahead and just recreate it now. So I'm just going to delete this. Go ahead and hit "create new role." You can see there are different types of roles. So we've got our AWS service roles. So for every AWS service, there's going to be different roles that you can add to it. Well, not for every single service,but for the services requiring roles. So we're going to be using Amazon EC2. Down here. We've got AWS service, linked roles.

So if we click in, this is a new, relatively new section which allows Amazon Lex to create and manage both voice bots and just normal bots on your behalf. So don't worry too much about that. It's very new. Here we've got roles for cross-account access. So basically, this allows you to access other resources in other AWS accounts that you may or may not have. Then here we have a role for identity provider access. So this is where you can authorisecognitoor users to access this AWS account using Amazon, Facebook, Google, or any other open ID Connect provider. A perfect example of that is, let's say you designed an app and this app is released on iOS and Android, and essentially it requires you to sign up using your Facebook credentials in order to access the app. Once you've signed in with your Facebook credentials,you can actually use those same Facebook credentials to grant access to your AWS resources. So maybe you want to allow your users to store data in a DynamoDB table. That is where you would basically go in and configure this. That's more of a developer topic, though. So let's go ahead and click on the AWS service role. And then here we're going to click on Amazon EC Two. And then in here, what we're going to do is we're just going to type in S Three because we want to filter out all our different policies and we want the S Three full access. So go ahead and click that and click Next. And again, I'm just going to call this Three Admin Hyphen Access, and I'm going to go ahead and create the role. So now that that's created, do note that up here it's global. So whenever you create roles, they're created globally; you can't change a specific region. It doesn't require it.

So that can be an important topic for an exam, a topic.When they're asking you if you have to create a new role in a new region, the answer is no, because all roles are global. Let's go over here and create two easy two instance.So I'm going to go ahead and launch an instance. I've already got one running for some reason, so I'm going to go ahead and hit select, and I'm just going to use all the basic default values. The only thing I'm going to change here is my three admin hyphen access. So I'm going to create it with this role. I'm going to go ahead and hit next, and I'm going to leave everything else as default. I'm going to launch it into my web DMZ security group,and I'm going to review and launch and just launch.And then I acknowledge that I've got access to that key pair. So that is now launching. And it might just take a little couple of minutes, but once it's ready, I'm going to go ahead and log into that instance. Okay? So my easy two instances are now being provisioned. Let's go ahead and click on it. Down here you can see the IAM role assigned. It has three admin hyphen access. You can click through that and actually click on the policy. Or you could click "Show policy" to just see the JSON policy. Or you can actually click here on the policy name and then go ahead and click on three, and you can see all the actions that you can actually go ahead and perform. Let's go back to the IAM. Let's go back to the EC two instances. We'll go back to the EC-2 dashboard. So click in here. And the other thing I wanted to show you is if we click in here, we can go to actions instance settings, and we can now attach and replace IAM roles to run EC two instances. Now, this is very, very new. Like, I'm so serious. This has only been a very recent change. But one of the problems you're going to find with some of the questions in the exam is that Amazon releases so much stuff so quickly that it's difficult for the AWS training team to keep the exams completely up to date.So you might see exam questions where it's asking whether or not it's possible to attach an arole to a running EC two instance. And it is now possible. But when the question was written,it might not have been possible. You just have to bear that in mind and you'll see it as well with some of the terminology.

So if we're talking about storage gateways, it might be using the old terminology that the product team used to use last year, but now it's completely different if you go and read the documentation. The same goes for DynamoDB. They will use old terminology to describe something,and the documentation will call it something else. So it can be a little bit frustrating. You just have to bear that in mind. I mean, I don't blame them. The AWS platform just changes so fast. It changes all the time. They're constantly pushing out new updates. So just bear that in mind going into your exam. So what I'm going to do now is just go ahead and SSH into my EC2 instance. Okay, so here I am in the AWS terminal. So I'm just going to type in okay. So here I am in my terminal window. So I'm just going to type in Hyphen SSH EC TwoHyphen user and then my public IP address, minus I, and then it's my EC Two keypad PEM. Go ahead and hit enter. I'm going to hit yes, and I'm going to update my privileges. And now I'm going to clear the screen. So I'm logged into my easy instance. Now the next thing I want to do is I want to access S Three. So let's type in AWS's three LS. And you can see it just works straight away. So these are all my S three buckets at the moment. Inside this particular account, I didn't need to go in and install credentials. I'm able to access S Three immediately, and I'll be able to list the contents of my different S Three buckets.

So this is why roles are really,really good because they're really, really secure. I don't need to store my credentials locally. If my credentials changed, I wouldn't need to login to my EC2 instances and update those credentials. And yeah, that's it. That's why roles are so powerful. Now let's just confirm that we have nocredentials being saved on this EC Two instance. Let's go ahead and go CD tilde. And so we're going into where we were in the last lecture. Do you remember there was a hidden directory called the AWS directory? But if we try and go into the AWS directory, it doesn't exist. If we actually type in AWS configure here, we can leave the access key ID, we can leave the secret access key, we can set our default region. So you might want to do that. So let's do an EU one. Go ahead and hit enter. And the default output format we'll just make as we just hit Enter. Now if we actually do CD AWS, it has created a new directory and in here it's got our config data and we can actually go in and have a look at our config data. And it's just defining our region here. But you can see that there are no stored credentials here. So if this EC Two instance got terminated, or if this EC Two instance got compromised, we wouldn't have to worry about deleting our access key IDand secret access key or changing it, and we wouldn't have to worry about updating it across a thousand different EC Two instances. So that's why roles are really, really powerful. So that's it for this lecture, guys. If you have any questions, please let me know. If not, feel free to move on to the next lecture. Thank you.

12. CLI Commands For The Developer Exam

Okay, so here I am in the AWS console and I'm just going to go over to Identity Access Management and in I am. What we want to do is create a new role. And this role essentially means we want our EC2 instances to be able to provision other EC2 instances. So I'm just going to call my EC Tworole and I'm going to go ahead and hit next. And so we now need to select our role type. We're going to use Amazon's and EC2's, and we'll go ahead and apply Administrator access. If you can't find administrator access, just type inadmin in the filter and then add inAdministrator Access and go ahead and hit Next. And we're going to create the role now. Now the next thing we want to do is to go in and create our EC2 instance. So I'm just going to go ahead back to the console and I'm going to go over to EC Two. And now inside EC2, what I want to do is provision a new instance. So we're going to use the Amazon Linux Am. I'm going to leave everything as default. I'm just going to attach my EC Two role in there. Go ahead and hit Next and leave everything else as default. And we'll just call this my EC TwoCLI, so go ahead and hit Next. And then we're going to let you use a new security group if you want. All you need is SSH access, so go ahead and hit Next, and go ahead and hit Launch and acknowledge that you've got access to your key pairs. OK, so that is now launching.

As soon as this is launched, I'm going to go into SSH via the public IP address and then we'll have a look at some commands that we can run. Okay, so I'm in my terminal window and I'm just going to SSH into my EC2 instance and there we go. So I'm in. I'm going to elevate my privileges to root and I'm going to clear the screen. Now, what we want to do is run some AWS commands in the command line to provision our own EC2 instances. But the very first thing we need to do is to configure our region. So we just type in AWS configure. We're going to just leave our access keyID and our secret access key because we're using a role, so we don't need them. And then here we need to configure our default region. So for me it's US West One because I'm in California right now and I'm going to leave everything else as default. And now I'm going to go ahead and clear the screen. Okay, so we're going to look at three specific commands for the Developer Associate Exam. But first I just want to show you if you go to Docs, AWS, Amazon.com,CLI, latest reference, thenec two, and index HTML. And I will put that in the resources section of the course. You'll see here all the available commands that you can use with the AWS EC Two command. And you don't need to memorise all of them, not even any of them to be honest.

But what would really help you in the exam is if you have an understanding of what language they use, so what language they use when you want to associate something, what language they use when you want to attach something, if you want to cancel something. And you'll see that they use the same words over and over again. And really, going into the exam, you want to have a firm understanding of three commands. So the first one is that we want to describe the instances that we currently have provisioned. So we'll go down and have a look at what's described, and then here we want to describe instances. The next one we want to remember is how do we describe the instances that are available to us, and that is how do we describe images. So we want to describe all the images that are available to us that we can provision instances from. Okay, and to create an instance,what do you think we use? Well, I would have thought to create it, but it's not there. And then what often trips students up in the exam is the Start Instances command. So that actually only starts a stopped instance,so it doesn't actually create a new instance. The command we actually use is called "run instances." And if you scroll down and have a look at the actual examples, you'll see that there are two classics, which are more or less obsolete. Now that's for really old accounts. That's for before VPCs came in.

But if we scroll all the way down, we can see So here we go. VPC execute this command to launch an instance in anEC Two. So AWS makes it easy to run instances. You just need to run it with your image ID, the number of instances that you want, the instance types, the key name, and then the security group. And if you read here, it says the key pair, the key pair named "my key pair," and the security group must exist. So in order for this command to work, we're going to need to make sure that we use the right key pair name and the right security group. So I'm actually just going to copy and paste this into my clipboard and I'm going to drop this into a text editor. Okay, so I'm in my favourite text editor,which is Text Wrangler on the Mac. So I've just pasted that in. Now what I'm going to go do is get my key pair name and the security group ID that I want to deploy this into. Okay, I'm in the AWS console. I'm just going to go sign into EC Two and we'll actually do this command at the very last part of the lab. But I'm just going to go over to how you can do it through the running instances or how you can go and click over on security groups. I'm going to do this in my web DMZ. So I'm going to grab that security groupID, just going to copy and paste that, go back over to text Wrangler. Okay, so I'm in here and I'm just going to change the security group name here. Just paste that in there. I'm just going to paste it in here. So there we go. Then I had my key pair, and the actual key for mine was, I believe, my Californian key. If you don't know, you can just double check in the AWS console and you can do that just by clicking down here, clicking on key pairs. And mine is called "mycalikey pair." And I'm just going to copy and paste that in here. It's called MyKeypair.It's called "mykalikey pair."

And then the actual AMI I'm going to change to be the same is I, that I'm musing with my current EC Two instance. So let's go back over to the AWSconsole and let's start running our commands. Okay, so I'm in the AWS console. What I want to do now is just see what EC2 instances I currently have running. So we just type in AWS EC2 and then describe and then hyphen instances. And then I'm going to go ahead and hit Enter. Now that's going to just basically return some JSON. So you can see, here's where I run the command. And here it's got my owner ID, my reservation ID, my instances, and then it gives me all the information about that particular instance. So when it was launched, the actual instance ID is the imageID that we use, and I'm just going to actually copy and paste that because we're going to need that for the next command and then scroll all the way down. Not the next command, but the one after this. So this basically just tells us everything there is to know about the EC2 instances that we have running. The next thing I'm going to do is I'm going to type in basically AWS EC Two describeimages and this will describe all the images that are available to me to provision. Now when you hit Enter on this, it's going to pause for a little while. It can actually take a couple of minutes, and then it's going to return basically all the images that are available to me to Provision.

Now this includes all the publicly available images as well as privately available images that I've created. Now if you can imagine, this is going to return thousands and thousands of results and it's all going to be in a JSON format. So I'm just going to wait for this. There we go. And you can sit here and it can take, you know, a long time to go through the entire thing. So to come out of this, we can just hit control C and that will cancel it returning and you can add in filters here, so you can just say,okay, I want to see Windows instances only. And so to find out how to do that, just go back to the command line, reference documentation, click and describe images, and you can actually see it over here, just move it into the centre of the screen. We can have if we scroll all the way down,we can have examples, so we could say, "Describe images where the ID is this AMI, for example," and that will return just a smaller amount of JSON. And here, this is the example that I was going to use to describe images. The owner is Amazon and then the filter or the name of the platform and the value is Windows. Let's just actually copy and paste that one into the command line. So back in the command line, I'm just going to paste that in and this will now tell me all basically the Windows images that are available to me that are owned by Amazon, and I'm going to get a much smaller result set. So there you go. It's not going to be endlessly scrolling down, returning results. So to recap what we've just run, the two commands that we've run so far are AWS EC to describe images. So we use that to describe all the images that are available to us and then EC to describe instances. We use that to describe all the instances that we currently have running.

I'm just going to run that again to get my image ID because I want to use that image ID to create my new instance. So just scroll down and there it is. The instance ID is here, and all I want is the image ID. So it is AMI, 16587, six, and copy that into my clipboard, and then I'm going to clear the screen. And so now I'm just going to copy that over here. So my AMI, I'm going to replace this ABC12345, and it's now AMI 16587, six, and hopefully this command is now all ready to run. We're just going to copy it and go back to the terminal. So I'm back in the terminal and I've cleared the screen and I'm going to paste that command in and let's see if I have been tripped up here. It says that the subnet doesn't exist. So that is a custom subnet. So I'm just going to go ahead and delete this particular part. I'm going to go back over to the console and I'm in the AWS console, and I just want to deploy this into the same subnet as my existing running instance. So I can just scroll down and scroll across and it's a bit hard to see, but it's over here. It says subnet ID. So it's this number here that I want. So I'm going to copy that into my clipboard, and now I'm going to go paste that into the command. So I'm back over here in the terminal and pasted that in, and hopefully this won't have any other errors. And there we go. It has now started to provision an instance. And if we go back over to the ECto console, and so now I'm back in the EC2 console, I'm just going to hit refresh. And there we go. We can see this new image is now being provisioned and we've managed to spin that up using the command line. The last thing we might want to do just for fun is go in and terminate both instances.

So I'm going to terminate the instance that I just created, and then I'm also going to terminate the actual instance that I'm on. So to terminate an instance, just use the Terminate instances command. And if you go down to the example, essentially all we need to do is run the AWSEasy to Terminate instances and then the instance ID. And you can also use a dry run operation. So if you use this switch here, it is just going to be a dry run. It won't actually terminate the instance. So if you just want to make sure that the command is working for test purposes, just do a dry run. So I'm going to copy and paste this into my clipboard and I'm going to go back to the terminal window and paste this in here. And now all I need to do is actually get the instance IDs that I want to terminate. So we get the instance ID of the one that we just created. We should be able to get that from here. And here it is, instance ID. So we'll just copy and paste that. So this is the newly created instance. I'm going to paste that in here and hit enter. And that will now terminate my EC Two instances. And you can see here it's returned JSON results saying "Terminating instances." And if I click back into the AWS Management console,we can now see that the instance is now shutting down. I'm going to do the same for the actual instance that I'm on, just to finish this lab. You can do the same. Do bear in mind that it will completely end your terminal session, but it is sometimes fun. I'm back in the console, and now I'm just going to delete that instance ID, and I'm going to package paste in my current instance ID and watch the console get sad. I'm going to lose my connection almost immediately. And there we go, because I've just concluded the instance that I was.

13. S3 CLI & Regions

Okay, so I'm in the AWS console. The very first thing I want to do is go in and provision a new EC2 instance. So go ahead and do a Linux AMI. We're going to keep all the default settings. Note that we're not attaching any roles to this EC Two instance just yet. I'm going to go ahead and hit Next. We're going to go and call this name. So I am EC for two instances, and I'm going to go ahead and hit next. I'm going to add this to my web DMZ security group, which just has ports 84, four, three, and 22 open to the world. I'm going to go ahead and hit Next. I'm going to go ahead and launch this instance. I'm going to use an existing key pair that I have. So while that instance is launching, we're going to go ahead and we're going to go and create some S three buckets. So let's go over to S Three, which is under storage. And then I'm going to create three buckets. So let's call this a cloud Guru and then we'll call this NV for North Virginia. Northern Virginia Go ahead and hit create.

And so here I'm going to create three buckets. So let's call this one A Cloud Guru and then Northern Virginia, and I'm going to change the region to make sure it is actually in Northern Virginia. So we have one. In fact, I might just make this easier for myself. So call this the East One. And I'm going to go ahead and hit "create." The next one I'm going to create is going to be a Cloud Guru and then we'll call this EU and then West and then Two. And I'm going to make sure that is in the EU West Two regions, so that's in London. Go ahead and hit create. And then the final bucket I'm going to create is going to be called A Cloud Guru and then AP Southeast Two. Make sure this is in Sydney, and where's Sydney gone? Here we go. Go ahead and hit create. So now I've got my three aCloud Guru buckets that I've created. One in Northern Virginia, one in London, and then one in Sydney. Let's go ahead and add some objects here. So I'm just going to add some random objects to it. So here is a picture of me and my mates at a rodeo in Austin, which we went to for several comps. So that is now up in our Sydney bucket. It does take a little bit of time, considering I'm in London, so it's going around the world. Let's go back over here. Let's go to EU West One and go ahead and upload here. So I'm going to add another picture. So this is my kid in the swimming pool. We just got back from a holiday in Portugal. It's really nice. And then the final one I'm going to do is over here, the academy aesthetic one. So I'm going to upload this. And again, we'll just probably do the Acar Guru team at serverless. Comp in Austin. I'm going to go ahead and upload that. So I've now got three objects in three different buckets around the world.

I've got an EC2 instance. The very next thing we need to do is just go over to IdentityAccess Management under Security, Identity, and Compliance. We're going to go ahead and create a new role. You probably already have this. We're going to call it the MYS Three Admin access role. So we just type in S Three here. We're going to go for the policy of Amazon S Three full access. And I'm going to call this my s.three admin access. Go ahead and create the role. And there we go. So we've got the role. Now the last thing we need to do is go in and assign this to EC Two. I'm not actually going to do this straight away. I just want to show you what would happen if we hadn't done this just yet. So let's grab the public IP address and go over to our terminal window. Okay, so I'm in my terminal window, just need to type SSH EC Two Hyphen user and then at the public IP address and then the name of mykey pair, which was my EC Two. Then key, and finally pair. Go ahead and hit enter. Go ahead, hit yes. I'm going to elevate my privileges to Root. I'm going to go ahead and clear the screen. Okay, so the first thing we want to do is just try and see our S three buckets. So we're going to type in AWS three LS. Now, of course, this isn't going to work because I haven't configured my secret access key or accesskey ID and I haven't configured any roles. So I could go ahead and try and store my secret accesskey and my access key ID on my easy instance. It's not very secure because if this got compromised, then I'd have some problems. So what I'm going to go do is attach my role to this EC Two instance. And this is very new, and in fact, it can come up in the exams and no one's quite sure whether or not they've actually updated the exam questions because it used to be a big exam topic about that you could only attach an EC Two instance, that you could only attach a roleto an EC Two instance upon creation. But that is no longer the case.

You can actually do it now using the command line or using the AWS console. So I'm in the AWS console right now. The way we attach our roles, we just go to Actions and we go to InstanceSettings and we go to Attach and replace IAM role. We select the role that we just created, hit apply, and there you go. That operation has succeeded. If you do get an error message, When you're trying to do this, it means you've created your role and then you're immediately trying to attach it to an EC2 instance. If you do that within like a five second or ten second window, you can get an error message. You just need to wait a few more seconds and then it should work. And if we go back over to our terminal window again,if you get an error message when you type in AWSS Three LS, it just means that you have to wait a few more seconds, but it should work almost immediately. And there we go. I can see all my S-three buckets, so I'm going to go ahead and clear the screen. Now, The next thing I'm going to do is copy the files, and let's just start with our Northern Virginia region. First, I'm going to type in AWS S three, then copy, and then the name of my bucket. So it's three. Then it was a cloud guru, and then it was us. east one. And I want to copy. I probably should have put Recursive. I'm going to copy the whole contents of the bucket. So I'll put recursive in east one. And And then I want to copy this over to my home directory. So Home and then EC Two users go ahead and hit Enter. And so this has now copied that file. So I copied ACG Austin.jpg to my home directory. My EC two-user directory I'm in. And you can see it here. Now, if I was to do exactly the same command, but we changed the bucket from US East One over to, let's say, EU West, and it was EU West Two.

So, London, go ahead and hit enter. You're going to get this error message,and it says it's an invalid request. Well, why? And if you actually read it, it says that you need to use the region argument. So I'm going to go ahead and hit up. I'm going to go and add a region, and then I'm going to type in my region. So it's EU, then West, and then Hyphen, and then two. And then that will copy the file down to my bucket. You can see it's downloaded the pool one. So if I type in LS, I've now got two files. Now, if I was to do this again for Sydney, but if I take this out, so take out the region and we change, instead of it being EU West Two, we change it to Asia Pacific Southeast, and then it's two and hit Enter. And it can take a little bit of time because it is going all the way around the world. There we go. I've downloaded it. So it really depends on which region your bucket is based on whether or not you need to use the region flag. So if I was you, I would get into the habit of using the region flag when using the AWScommand line for S3, because then it doesn't matter where your buckets are based or where your EC2 instance is based, it is always going to work. So that is it for this lecture, guys. Feel free to go ahead and delete that EC instance, and if you want to delete those test buckets. But it's like I said, always a good habit to get into using this flag when you use Three for the rest of this course, particularly if you're operating out of newer regions. So if you've got any questions, please let me know. If not, feel free to move on to the next lecture. Thank you.

Study with ExamSnap to prepare for Amazon AWS Certified Developer - Associate Practice Test Questions and Answers, Study Guide, and a comprehensive Video Training Course. Powered by the popular VCE format, Amazon AWS Certified Developer - Associate Certification Exam Dumps compiled by the industry experts to make sure that you get verified answers. Our Product team ensures that our exams provide Amazon AWS Certified Developer - Associate Practice Test Questions & Exam Dumps that are up-to-date.