Manage IAM users and their access—You can create users in IAM, assign them individual security credentials (such as access keys, passwords, and multi-factor authentication devices) or request temporary security credentials to provide users access to AWS services and resources. You can manage permissions in order to control which operations a user can perform. IAM users can be:

  1. Privileged administrators who need console access to manage your AWS resources.
  2. End users who need access to content in AWS.
  3. Systems that need privileges to programmatically access your data in AWS.

 

General Use Cases for Creating IAM Users

  • It is security best practice to not use root account. The root account grants access to all services and resources, and users can perform any action on those services. Grant users the minimum amount of privilege necessary.
  • You have other people in your group who have varied access and authorization permissions. IAM users make it easy to assign policies to specific users accessing specific services and associated resources.
  • If you want to use the AWS CLI, you will need an IAM user.
  • If you want to use a role, you will need an IAM user.
  • If you want to federate access to the IAM console or to an AWS service API, you will need an IAM user.
  • If you want to leverage web identity federation, you will need an IAM user.

 

The following diagram describes the canonical use case for creating an IAM user:

Get Started with AWS for Free

Create a Free Account
Or Sign In to the Console

AWS Free Tier includes 750hrs of Micro Cache Node with Amazon ElastiCache.

View AWS Free Tier Details »

Follow @AWSIdentity on Twitter
Create_User

Using Groups for Easy Administration

A group is a collection of IAM users. Groups let you assign permissions to a collection of users, which can make it easier to manage the permissions for those users. For example, you could have a group called Admins and give that group the types of permissions that administrators typically need. Any user in that group automatically has the permissions that are assigned to the group. If a new user joins your organization and should have administrator privileges, you can assign the appropriate permissions by adding the user to that group. Similarly, if a person changes jobs in your organization, instead of editing that user's permissions, you can remove him or her from the old group and add him or her to the new group.