In this video, we are going to create a user account under the root user account and configure this
user account for programmatic and console access.
So basically we can follow these steps which explained step by step in this user, you can click and
open the web page.
You can see that in this article step by step, explaining what we will do when we are creating a user
and I am user and give some access.
So I will also follow during this video.
Let me continue it together.
But before that, let's review what we have done so far.
Basically, we are going to create user specific account under the root user account, and we set that
when we after activating our Adobe account, we have got only the root user account.
And the first thing we should do creating a user under the root user account and use these user for
daily usage of a management console.
Even you have the only one user to use a second.
Creating a specific dedicating user account is one of the first thing we should do follow after activate
our account.
This is the security based practice that we should follow, so we should create user specific IAM user
account under the root user account that they have own login and password information because root user
account has powerful access that can change your payment information, password information, removing
users and lots of dangerous things.
So we also need to programmatic access.
We said that we need also programmatic access because programmatic access users in IAM is required if
you want to control or access your services from the command line or xkcd from the programmatic way
of interaction required to programmatic access into the IAM user definition, a programmatic access
users will be given, the users will be have given the access kid and a separate access key which your
sales tools will use to authenticate to a place and execute your commands.
So it is important to giving a programmatic access when creating an IAM user.
And when we are creating a user with the programmatic access, it will be given to us.
A The will is access key ID and a secret access key.
So these two case will be required when you are authenticated to a will via SLI in order to execute
our commands.
So let's log in to our root user and create our IAM user.
Be together for that purpose.
Please connect with the sign in page and log in with the root user account.
Signing with the root user account.
So we have look in the management console with our rotisserie account, which you already also created
before.
So in this second, I'm going to open the I am.
Identity and access management.
You can search in here and click this button.
So then we go to the place am page.
And in this page, as you can see that we can do some stuff regarding with the identity and access management.
We have users role policies and identity providers, so on.
So we basically follow the users, just click the user section.
And as you can see that I have already created my iam user account under ma under my root user account.
But also please you should create a new one in order to create any IAM user account, you should click
the add user button in here.
Just click add user button.
And enter the username what you would like to follow the course because during the course we will always
using these IAM users for that purpose.
Let me give the name the name user and this is the important part.
We are going to select a double access type and we should check the access key and password both these
checkbox, the access key programmatic access checkbox in access type section and the console access.
The important part is we should select both of them.
Okay.
So let me explain.
The first programmatic axis.
Programmatic axis gives you access key ID and secret access key ID in order to interact resources with
programmatically like a CLI SDK, cloud formation and CDK, we will use these tools during the course.
So that's why it is important to give programmatic access.
So during the course we will develop our microservice architecture via programmatically.
That's why we should give these programmatic access and also provide the console management access and
management console access.
It is also important, of course, because we will log in our management console with the user specific
account and follow the course with the specific user on the management console so you can give some
custom passwords and don't record for the renewal.
This is for the renewal and we can give some custom password account and it can give.
Okay.
You can click after you define a console password, you can click the next permission button.
So now it is important and we are going to set permissions since we will use this user for our Udemy
course.
I would like to give administrator access to this user, but if you create this user for someone else,
you should give more specific permissions by defining the policies.
So click the attach existing policies directly top.
You can click this one because we will attach the existing policies directly so you can see the administrator
access and you should check this box in order to give the administrator access to this on the checkbox
of access to policies that you want to assign to user.
But if you create for other users, for example, you can specify custom permissions like only lambda
execution or three, you can, for example, you can search for the lambda and you can give on lambda
full access or read on access or execution, basic execution role.
Or basically you can give only a three full access or three upload or read on the access to.
But since we are using the course with the one specific user specific dedicated account, it is good
to follow with the administrator access for our IAM user.
So after check selected this administrator access, click the next button.
And we don't define any tech and just click the next button and reveal your user.
The username is new user and you can specify what you want and we have defined the passwords and the
important part is the permission.
We give the permission with the manage policy, which is the administrator access.
And you can find that the created user see access case.
Let me click the create button and see what we are going to do.
After created, you will see the success message and also see this information is very important.
You can find your created user c access keys for the programmatic access.
We will use this access case when start to developing service applications and see the password secret
access case in here with clicking the show button.
So this is very important.
Please copy these to information into your textbox or somewhere else because we will follow these.
We will follow when authenticating to a double or account via a double click and cdcc.
So that's why it is important we have successfully created our user specific account.
So now you can also sign in with this account, right?
So before go to the signing page, don't forget to get this account ID and the secret access key you
can see on the right of this page.
And also you can define alias for the account.
I would like to show one more thing.
You can see the account I.D. in here and also you can define the alias for this account.
But these are the main information when you follow the during the course, the account ID, the access
case, your user and password and secret access case, we have created the sub user account.
It is very important.
So now I'm going to go to signing page again and provide the newly created user credentials.
Let me create a new a will start Amazon.com and see signing the console page.
And now I'm going to look at the root user account and I would like to sign in with the I am user,
so I am user is required to account ID.
I have short account ID in the previous section.
You can see in here, of course this is lost, but you can get the account ID from the right top of
the page from the previous root user account.
And after that you should define the account ID in here.
I have specified the alias so that's why I can give the.
The name of this alias of the account.
ID account.
Alias I have defined.
But you should put in here two digit number as a account number.
So after that, we should create a we should log in with the iam new user and I have a.
Username is a user and I'm specifying.
My password and click the sign up button.
Okay.
Very good.
We are on the management console and login with the created iam specific user and I would like to switch
the console home.
Okay.
Very good.
So we will follow the whole course with this newly created user.
So that's why please keep these account live and activate it.
It is important because we will follow the the whole course with newly created users.
I'm following with the Tosca, the the previous IAM account, but I will create this new user in order
to show the whole process to you.
And please keep this user account live and activated.
As you can see that we have followed the security best practices and create specific IAM user and configure
for the programmatic and management console access.
So we will follow the course with these users.
And in the next video I will explain what is the access types and what is the difference between programmatic
and management console access.