Cloud Course CLI
There is a cloud-course cli tool that you can use to assess your infrastructure and get feedback on what you've done. This will essentially check if you've followed the tutorials correctly.
step 1:
Download CLI Version 1.0.3
By downloading and using the Cloud Course CLI tool, you agree to our CLI Terms of Use, CLI Privacy Policy, and acknowledge the Security Guide.
step 2:
You can put this binary wherever you want, but if you put it in your PATH, or in a std bin directory on your machine, then you can run it from anywhere.
Here are the options you can use with the cli:
If no command is provided, the CLI will prompt you to select an assessment interactively.
step 3:
Now you can run the cli without any arguments to get a list of assessments.
step 4:
Show timestamps
00:00
This course has a companion CLI tool, the Cloud Course CLI,
00:04
that you use to check if you've set up your infrastructure correctly.
00:08
So after you deploy a bunch of things, you can use the CLI tool to check them and get
00:13
feedback on whether you've done it right or not. So I'm going to come in here and download it
00:17
for my machine. I'm using macOS ARM, and it's just going to download this binary. I'm going to
00:23
stick it into my Downloads folder for now. Then, on Mac and Linux, we need to modify the
00:28
permissions. So I'm just going to copy this command. And since I'm currently in my Downloads folder,
00:34
I should just be able to run this from there. So I'll go and download
00:38
Cloudcore, and yeah, that's just running as a binary application here. I can see it's giving me
00:44
all of the different deployments that it can assess for me, but I'm not going to leave this in my
00:48
Downloads folder, because I'm going to move this to .local/bin. I actually need to
00:54
specify what I'm moving, obviously. So that's going to be the Downloads Cloudcore binary, and I'm
01:00
going to move that to my local bin directory.
01:03
And that means that on my Mac, that's in my PATH. So anytime I want to run Cloudcore, I can just
01:10
use "cloudcore" and it will be able to pick that up. And here again, you can see all of the
01:13
different deployments we're running. So when you're going through the course, if I go back over
01:17
here, we can see a lot of these deployments. Like this section, where we set up our
01:22
accounts and set up Route 53, there's this little check here that's testing whether
01:27
we've done things correctly. And further on, I've done the static website one too. So these are
01:32
ones that I've already checked, and it's told me all the different points that I've gotten
01:35
correct. But if I go to one that I haven't done yet—so here's CloudFront static site—it tells me
01:40
that to check if I've done this all correctly, I can run "cloudcore run" and then this unique ID.
01:44
So if I were to copy and paste this in right now, it would run and tell me if I've done it
01:49
correctly, but I actually need to log in first because I just downloaded this. It needs to verify
01:54
my account in the CLI with the account I have on the website.
01:58
So here it's telling me I can just run "cloudcore login".
02:01
And this should open up a browser tab, and then I can verify that the code is correct. Yep, so
02:08
I'm going to authorize this and then head back over.
02:11
So if I run "cloudcore"—actually if I run "cloudcore help"—it will tell me all the different
02:17
commands I have. So I can log in, log out, I can run "cloudcore auth" to check my current account
02:21
details. And there are a few other commands in here that I could run. Uh, I
02:25
could run "billing" to see how much I'm spending in each of my accounts.
02:29
I can use "instances" to show which EC2 instances are set up in which regions, just to
02:33
verify that I don't have any running that I don't want. The "show" command will show me all the
02:37
infrastructure that I might have running from this course. It makes it really easy to delete it later on.
02:42
But mainly, this CLI tool is used to verify I've set up my infrastructure correctly, based on how
02:48
the course wants me to. So I'm going to go back to that other example. Let's say I had completed
02:53
this assessment—I can copy this and I can run it in here. It's going to ask me for my playground account
02:58
because this was supposed to be set up in Playground. And then, of course, I need to be logged in
03:02
to AWS. You're going to get used to this, because it logs me out of the CLI every twelve hours. If
03:08
it's been twelve hours, I'll need to re-login to AWS just from the CLI. So I'm already
03:13
logged in in the browser, so that's all good. Uh, so now let's try running this one more time. So
03:18
now it's going to ask me for my playground account and then it's going to
03:21
go into my AWS account and check if I've actually done it correctly.
03:25
And it looks like I already set one up. So yeah, this is going to allow me to check if I did that
03:29
all correctly. According to the assignment, it's checking all of the different details here, that
03:33
the permissions are correct—everything like that. And then it told me I have completed that
03:37
one hundred percent correctly—everything was done correctly for that one. So if I go back here, I can
03:41
see, yeah, that is in fact done. And this is just a way of tracking your progress through the
03:45
course but also verifying you've done things correctly, and it will give you feedback on that. So
03:49
if I'd set up my permissions incorrectly—if I'd made them too open or something—this would give me feedback and tell me what I need to change.