In this video, we are going to click set up of our.
But let's remember what we have done in the last video.
In the last video we have downloaded to a silly version two and verify that it is installed successfully
in our local computer.
And we solve the the version number is starting with two and we run basically a double digit version
command.
Okay.
Now in this video, we are going to click set up or will see how we can set up the CLI.
As you can see in here, it says different commands.
But we will start with the configured command.
Is the fastest way to set up our cell installation.
I will show you how to quickly configure the basic settings that the command line uses to interact with
resources.
These include your security credentials, the default output format, and the default a reason.
Basically we will following the documentation is the same way.
So if we come to the our web application web site, which is the installation part, so as you can see
that we are a modern user guide for version two and we have installed successfully and it is time to
set up these obviously.
So for that purpose I'm also sharing the links, but you can come here and see that quick setup link
in the left hand side.
If you click this quick setup, you will see the whole instruction how we can set up our ACL.
And basically in most cases we are going to use a configure command is the fastest way to set up our
ACL installation.
When you enter this command, the CLI prompts you for pieces of information.
These are the for information.
When you run this command, it will ask to us a W's access key secret access key default region name
and the default output format.
So the aid will stores this information in a profile profile documentation which name default in the
credentials file.
This will be the a collection of settings of the profile file in your local computer.
You can change this profile and credentials with creating new profile or updating existing existing
credentials by choosing to add configure set commands.
It has also extended information link about this ad sales, sales profile and credentials.
I will also share this link individual resources.
So but in our case, we will follow the basics, right?
If you type the configured command to the command window, this will ask you for basic information that
we need to fill.
You can see example of configuration with sample values.
This is the example values and these are the values access.
Key secret access.
Key values comes from the our user definition of a blaze account.
We will grab those information from that.
And the configurations are options.
The other configuration, which means the region name and output format is optional.
You can skip as a blank and a blaze will get the default values.
But it's good to set explicitly your region name and output format to see data format when you hit some
commands.
So let me start with the how we can grab this access kid and secret key ID come to the Willis management
console, sign in with the user.
Let me see.
I'm not sure I can see with the sub user.
Open the IAM identity and access management.
Com to user section here my user and you also creating a new user.
You can open the user.
I am user and if you scroll down.
Yes I can see in the sub user now.
So that's why we should be looking with the root user in order to get these access and.
Secret access.
So for that purpose, I'm going to sign out.
Sign into the console.
And sign with the root username.
Okay.
It is really hard to feel this capture in either place.
Okay.
Very good.
Okay.
Now we are going to log in with our root user.
And by this way we can get the secret and access keys of our newly created IAM user.
Open the iam.
Go to the user section.
And click the new user, which you have defined in the previous sections.
If you open the users and the naive user, you can see the security credentials tab in here.
If you click this section, you can scroll down and see the access key.
What we created when we created this user.
So you can copy the access key in here, but there is no secret key because it is very important to
you.
This is also not showing us the secret key.
If you lose or forget your secret key, you cannot retrieve it.
Instead, create new access key and make the old key inactive.
This is the best practice.
So when I say that when we are creating this user, please note the access key and secret.
Okay.
If you didn't note that you should create new access by making inactive this one.
So let me show how we can do that.
Click the Create Access Key.
And as you can see that we have created a new access key and the security in here.
You can click the show button and copy the secret key.
And there is some warnings I would like to show also.
Never post your secret access key on public platforms like GitHub, so you should only store in this
access key and secret access in your local computer and you don't upload any other source control system.
It is very important so you can generate this access key from this location and you can inactive the
old one, which you forget the secret key.
Okay, so why we are grabbing this access key and secret access key?
Because the our main usage is the programmatic course.
We are going to go into course to a place with using the from the SLA, using the SDK and make the direct
API API calls.
This will be provided to make API calls to the resources we are using data with HCI and CDK.
Okay, very good.
I'm not going to remove access key enough.
I'm going to remove this unnecessary user.
I'm not using this user.
So that's why I would like to delete new user and I will continue it to my own user, which is the mammoth
here.
Okay.
So you understand how we can get the user role in our application.
So let me come back to our documentation and now we will basically run the configure command and we
provide this access key ID and secret access, key ID information in our configuration page.
Please open the command window and right to place configure.
So see that we it is expecting to us an access gate.
I'm not going to provide anything because I have already configured before you can set the access key
in here and after that click the enter and this will be asked to you.
Secret Access Key.
We can give the secret access key and after that the default login name.
You can give the default name or you can leave as it is.
That will be follow the basics.
And, and the last output is the output format we can give JSON or HTML format.
It's up to you or you can give the empty character and this will be get to default one.
Okay.
After you have entered these parameter values from your computer, you have successfully configured
our A list and it is ready to use now.
So that means we can able to interact our resources with the user what we have defined.
So that means we can do everything from the management console or using the SLA with this user because
we have an admin access and we have configured our user with putting the access key and secure access
key.
Let me come back in here.
Yes.
Now, after we have configured our user in the account, we can see your settings with this command.
Let me open the.
Yes, this is a configured list.
So if you hit the enter, you will see the configured user.
So as you can see that I have a default profile and this is the access key and security access key information.
This is the end of the characters and it is saving in shared credentials file and my region is us.
This is data.
This is very important.
Please really be careful about that because when we are interacting our resources with this user using
the SLA command, this will be create or update delete manage any resource into the the region of the
US is etc. So I chose the US is two and I am going to follow the rest of the course.
With this region and you make sure that your region is yes is true, or you can make sure that the major
console region will be the same one.
We will check twice.
So let me check in here.
I'm going to sign up and log in with my IM user.
Which will be the.
Okay.
I'm going to look in with I am user.
So now, yes, this is the wrong creation.
Right.
I would like to change this.
US is because the a management console and a CLI should be the same region and that in that way I can
see the same interactions in the resources.
So that means if I am creating a new lambda function, I can retrieve the lambda functions in here or
I am creating or managing any dynamo db api gateway from the CLI.
I can see the interactions from the management console.
Make sure that your configured SLA account region and your console region is the same.
Okay, now we are ready.
And also after this setting the complications, it is very easy to change this profile and credentials
with creating new profile or updating existing credentials with using the alias.
Configure set command can use a configure set command in order to set any value.
If you click the set command, you can see options how we can set our operations.
OC A has also extended information in the profile and credentials.
Let me open this.
Come or confiscation?
Yes.
You can follow the documentation and configure Sally.
And there is some configuration basics.
I have one link I would like to show in here.
Most of it is yes, configuration and credential settings.
You can follow this article, how to update the credentials in the settings file and how the managing
ID is configuring your settings in here.
For example, yes, we have some command a configure set re region and give us is too and profile is
intact.
So these kind of commands can be run with a CLI a configure set and get.
I would like to show one command to be together.
Let's see.
It is configured.
Least we already see that a table is configured.
If you run the place configure get region.
And give the profile.
Default.
You can see that our region is us, is too.
And these kind of commands can be run on the sly.
And at the same way we can set configure set region us is too and so on we can.
On the same command with the subversion, with giving the regime volume.
You understand what I am, meaning it is very useful.
We have already configured ah a user in the CLI and we see some other commands which configure, set
and get.
And I will also share these articles individual resources.
So that's not fond of as you can see that we have successfully installed and configured our a obviously
and now we are ready for to interact with the resources from the our local computer with using data
with SLA.
Let's see next prerequisites for our project.