AWS Identity and Access Management (IAM) enables you to manage access to AWS services and resources securely. Using IAM, you can create and manage AWS users and groups, and use permissions to allow and deny their access to AWS resources. IAM is a feature of your AWS account offered at no additional charge. You will be charged only for use of other AWS services by your users. IAM enables your users to control access to AWS service APIs and to specific resources. Protect your AWS environment by using AWS MFA, a security feature available at no extra cost that augments user name and password credentials. IAM helps you analyze access across your AWS environment. Your security teams and administrators can quickly validate that your policies only provide the intended public and cross-account access to your resources.
| Support | Online | Customer Type | Large Enterprises Medium Business Small Business |
| API | Location / Phone Number | Seattle, Washington | |
| Deployment | SaaS/Web/Cloud | Category | Identity and Access Management (IAM) Software |
Disclaimer: The pricing details were last updated on 31/01/2020 from the vendor website and may be different from actual. Please confirm with the vendor website before purchasing.
AWS IAM is Identity and Access Management (IAM) Software. AWS IAM offers the following functionalities:
Learn more about AWS IAM features.
Yes, AWS IAM provides API.
I like the level of control this gives me to my products in AWS. Giving me control to be as secure or open as I like. One of the best services out there and the fact you set it all up yourself means you know you are secure. Unlike other providers you just have to trust. they have great guides and support to help you and advice on the best configurations.
Can be repetitive to setup for each product but worth it as you know it is done correctly. I would not change this as I think it work great and once you learn the first time it take no time at all to set up multiple times.
As a web agency we host big complex platforms that need good security and this allows us to do that giving our clients more confidence that they are protected
The best parts are roles, federation, SSO capabilities.
Its moving in the right direction, nothing to dislike about the service.
Nothing at this moment. Its a great product with lot of features.
With Federation and SSO capabilities, we are able to provide access to AWS services for our end users by leveraging their existing credentials. This also helps when someone leaves the organization, for pulling out their access.
I like the ability to assume roles, grant temporary access keys, and the ability to grant or deny access at fine-grained and customizable levels.
There seems to still be some discontinuity in permissions (really talking CloudFormation) for various cloud resources. Some you need to specify names of resources, other complete ARNs, while others don't let you specify specific resources at all.
We've configured ourselves with temporary access keys for all employees, granted after 2-factor authentication, to minimize risk of stolen keys. Other apps and services assume roles with fine-grained permissions so that any intruders to such machines would have minimal rights to do harm or negligent behavior.
The level of granularity you can get on "MOST" resources is absolutely fantastic from a security standpoint.
Sometimes it's hard to troubleshoot what is blocking or not blocking what you think it should be.
Providing least privileged access to all users who enter our AWS environment.
Controlling how individual services within an environment can talk to each-other to the level of granularity as you can with AWS IAM is incredible.
Love everything about it. It ties to all of AWS's services and makes it easy to create highly secure applications.
I built applications and environments for some of the larges corporations in the US.
The separation of roles and policies allows you to create multiple configurations
the sheer number of provided aws policies can be daunting. an index of the policies and what they provide would be helpful
we use iam for authentication and for enabling/disabling access to sections/functions of AWS. We can create a role that is only allowed to do one specific function, which increases security
Extremely fine-grained controls to handle access at every level imagineable.
Right now a user can not add MFA without having access to IAM. This requires an admin to handle this in-person (or over a video call). Also physical access tokens are brand new to IAM and not fully implemented yet.
Controlling permissions for users and infrastructure.
Ability to manage users and groups within AWS.
Testing to make sure credentials are good to go, but once you have set them, it is very ease to manage.
Must have and used to for AWS services implementation.
Group and user access management is better managed.
Iam is the leader among access management services. Roles, Users, Groups are a must for any account, and it is fast!
There is nothing that I do not like from IAM
We use IAM to ensure that tenants are only able to access things that they should have access to.
I love the fine grain control of access. It makes my admin workflow very simple. It's a really simple feature, but when setting up an account, I love the check list on the home page of IAM that shows you some security best practices, like removing root.
I really can't think of anything I dislike about IAM. Sometimes I feel like I end up having to set up the same thing again and again when I'm creating a new account, but anytime I've had to do that I can automate it easily. I really wouldn't want AWS to change the set up process because I think it would make people create holes that shouldn't exist.
There is no reason (and frankly no way) not to do it. Its a simple tool that you can easily leverage to make your life easier.
Very specific access in a brain dead simple way. Let the people who need to access something access only that thing. If you don't know you need it, you don't have access. Best sort of security.
