AWS Identity and Access Management (IAM) enables you to securely control access to AWS services and resources for your users. Using IAM, you can create and manage AWS users and groups, and use permissions to allow and deny their access to AWS resources.
To get started using IAM, click Create Free Account. Or, if you have already registered with AWS, sign in to the AWS Management Console and get started with these IAM Best Practices.
IAM is free, so start using it today!
Get Started with AWS for Free
Create a Free AccountOr Sign In to the Console
Receive twelve months of access to the AWS Free Usage Tier and enjoy AWS Basic Support features, including 24x7x365 customer service, support forums, and more.
How-To:
How to Manage Identities in Simple AD Directories
How-To:
How to Migrate Your Microsoft Active Directory Users to Simple AD
Announcement:
Register for and Attend This August 20 Webinar--Best Practices for DDoS Resiliency
Compliance:
New Whitepaper: CJIS Compliance on AWS
How-to Guide:
How to Implement a General Solution for Federated API/CLI Access Using SAML 2.0
AWS IAM allows you to:
Manage IAM users and their access – You can create users in IAM, assign them individual security credentials (in other words, 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.
Manage IAM roles and their permissions – You can create roles in IAM and manage permissions to control which operations can be performed by the entity, or AWS service, that assumes the role. You can also define which entity is allowed to assume the role.
Manage federated users and their permissions – You can enable identity federation to allow existing identities (e.g. users) in your enterprise to access the AWS Management Console, to call AWS APIs, and to access resources, without the need to create an IAM user for each identity.
Protect your AWS environment by using AWS Multi-Factor Authentication (MFA), a security feature available at no extra cost that augments user name and password credentials. MFA requires users to prove physical possession of a hardware or virtual MFA device by providing a valid MFA code.
IAM enables your users to control access to AWS service APIs and to specific resources. IAM also enables you to add specific conditions to control how a user can use AWS, such as time of day, their originating IP address, whether they are using SSL, or whether they have authenticated with a multi-factor authentication device.
You can enable your mobile and browser-based applications to securely access AWS resources by requesting temporary security credentials that grant access only to specific AWS resources for a configurable period of time.
IAM can be used to grant your employees and applications federated access to the AWS Management Console and AWS service APIs, using your existing identity systems such as Microsoft Active Directory. You can use any identity management solution that supports SAML 2.0, or feel free to use one of our federation samples (AWS Console SSO or API federation).
Protect your AWS environment by using AWS Multi-Factor Authentication (MFA), a security feature available at no extra cost that augments user name and password credentials. MFA requires users to prove physical possession of a hardware or virtual MFA device by providing a valid MFA code.
AWS has a list of best practices to help IT professionals and developers manage access control without losing flexibility or resiliency. To get a full explanation of IAM best practices, watch the recorded session from re:Invent 2014 (in the box to the right of this paragraph).
Users – Create individual users.
Groups – Manage permissions with groups.
Permissions – Grant least privilege.
Auditing – Turn on AWS CloudTrail.
Password – Configure a strong password policy.
MFA – Enable MFA for privileged users.
Roles – Use IAM roles for EC2 instances.
Sharing – Use IAM roles to share access.
Rotate – Rotate security credentials regularly.
Conditions – Restrict privileged access further with conditions.
Root – Reduce/remove use of root.
