Okay, so here is the summary section for IAM.
So we've seen about IAM users,
and they will be mapped to
an actual physical user within your company.
And users will have passwords for the AWS Console.
Then it is best practice to group these users together,
and so the groups can only contain users,
they cannot contain other groups.
Then to give permission to either the users
or the groups,
we're going to create IAM policies,
which are JSON documents,
that will outline the permissions,
that a user or a group can do.
Then if we are within AWS,
we are using roles.
So if we create an EC2 instance
we'll see in the next section,
or if we want to give permissions,
to an AWS service to do something else,
on another AWS service,
then we have to create IAM roles.
For security and making sure,
our users are completely safe,
we must enable multi-factor authentication,
to have a second device to login,
and then also have a strong password policy in place.
If you want to access AWS using the CLI,
so the command line interface,
or the SDK because you are programming some code,
then you must generate some access keys.
Which is the access key ID,
and the secret access keys.
Together they will give you programmatic access to AWS.
If you wanted to audit your IAM dashboard,
you could create a credential report,
to get some information about all your users,
or if you wanted to audit a specific user in IAM,
then you would use the IAM Access Advisor,
to see if a user has been using their permissions recently.
So does it for this section.
I hope you liked it,
and I will see you in the next section.