Here, once you type in a configure,
it shows the AWS access key ID prompt and ask you to copy and paste into it.
The second entry is AWS secret key,
and yeah, we also do copy and paste.
The region here, because we are closer to Ohio,
so we enter O,
the region has a name, short name.
Their short name represent by typically the US or Europe, EU.
In Ohio, is us-east-2, all right?
So US is a region,
east or west we have here,
and then dash two is the second one.
Dash one is what your name.
You can actually go to AW website to find out all these short name for the region.
You can also run the AWS EC2,
this describe region to get a whole list,
and the last one is alpha format for the command,
can be output, can be [inaudible].
Here we show the AWS CLI command.
AWS EC2 describe region,
and it is very old available region name and their URL.
Those URL can be used in to set environment variable so that
other applications like ECI programming interface,
if you're using that can't automatically route the request
to the region based on that environment variable setup.
To shut down an instance or a set of instance,
what we need to do is to find out the instance ID from
the AWS EC2 Management Council or from some data file or database we have written down,
save these and the instance ID.
We have one instance in us-east-2, Ohio location.
It has the ID ending with 723 here.
So let us run the command aws ec2 stop-instance, this command.
It has one option --instantance-ids,
and look carefully here,
they use ID with s. So within the same command you can enter
multiple instance ID and they will be
with a single command that can be shut down together.
It looked nice to allow.
It start to say shut down,
stop the instance when this command is executed.
All of a sudden, I find out I forgot.
I just started my only single instance,
and by shutting it down,
I now cannot run and demonstrate the AWS command.
So to demonstrate how to start and stop.
So inside the EC2 Management Council,
I will show one trick.
Basically, we are trying to save the instance as the image and then allow it to commit.
So after these shut down,
we go to the EC2 Management Council.
We can confirm the instance is actually shutting down,
and at the beginning it will say stopping as the status.
After a while, maybe one minute typically,
the instance state will be changing from stopping to stopped.
To restart the instance,
we need to start our instance from the AWS CLI.
We need to have a machines that already installed with AWS.
So we've got a chicken and egg problem here.
So one way to do it is,
we would like to clone our current instance and the best way
to clone that is not to start configuring from scratch, right?
So in the AWS,
they allow you this future creating image,
and by making our instance image are performing, okay?