We will choose that last option. Select the policy from the list. Lara casts. And then click next. Everything looks good. So we click on create user. Here AWS shows us the sign in URL, username and password. We will copy the sign in URL and store it somewhere. I'll do that behind the scenes. And then we copy the generated password.

But it won't allow us to launch the instances though. So yeah, it doesn't seem that this User is limited to perform only specific actions. But it actually is. Now, as we mentioned earlier, we can create user groups, attach policies to them, and add users to these user groups. And they will automatically get access to perform the actions listed in these policies. We can also create users that only have programmatic access, but cannot access the console interface. This is how a service like Laravel Forge operates. You generate an access key for a specific IAM user, share it with Forge, and Forge uses the key to perform certain actions on your behalf. And finally, we can create IAM rules, attach policies to them, and allow certain AWS services or third party services to perform certain actions in our AWS account when they assume these rules.