Granular control over access to AWS resources is made possible by the crucial service known as AWS IAM. The fact that it enables me to precisely regulate user access is what I value most. From developers who require complete access to particular services to auditors who require read-only permissions on a few S3 buckets, I've used it to set up varying access levels for different team members. The visual editor's ease of use in creating these policies is a major plus, and management is made simpler by the ability to quickly attach or detach policies to users and roles. Our security posture depends on this degree of secure access control. Review collected by and hosted on G2.com.

​Despite being a strong tool, IAM has several limitations that might be difficult to overcome, particularly for novice users. One important factor is the high learning curve. At first, it might be difficult to comprehend the distinctions between users, groups, roles, and policies, as well as how they all work together. The intricacy of permits is another source of contention. It might be challenging to create a very detailed policy since even a little setup error can result in lockout or unauthorized access. Troubleshooting permission issues has taken up a lot of my time, particularly when dealing with service-linked roles and cross-account access. It can also be annoying since there aren't any clear defaults; additional templated rules for typical use scenarios would be useful if AWS offered them. Review collected by and hosted on G2.com.

This tool enables you to set permissions with a very high level of detail and manage the identities of users, applications, and services across multiple AWS accounts. Features such as MFA and temporary credentials through roles enhance security and integrate smoothly with all AWS services, while also supporting advanced governance. Review collected by and hosted on G2.com.

Working with JSON policies can be quite tedious, especially since there is no built-in support for role inheritance or any kind of hierarchical structure. Review collected by and hosted on G2.com.

Centralized identity management and access control with a wide scope of use. It is also straightforward to use, with good documentation and easy implementation, and easy integration. Review collected by and hosted on G2.com.

Downsides of any amazon web service is the hidden cost it has. Review collected by and hosted on G2.com.

permissions across all AWS services—without sacrificing security or scalability. It serves as the core of AWS security, and its flexibility makes it an essential tool for managing infrastructure access in any size of organization. Review collected by and hosted on G2.com.

No, because this is actually very good for security. Review collected by and hosted on G2.com.

I like how AWS IAM lets me set fine-grained, role-based permissions to securely control access without sharing credentials. Review collected by and hosted on G2.com.

I dislike that IAM policies can get complex and hard to manage at scale, especially when troubleshooting permission issues. Review collected by and hosted on G2.com.

It is most secured way of controlling the access and scalable, fine grained approach to provide access and permissions Review collected by and hosted on G2.com.

It is best tool to control the permissions, there is nothing to dislike Review collected by and hosted on G2.com.

Ease to use, manage and understand.

IAM policy generator makes things super easy for granting granular level of access. Review collected by and hosted on G2.com.

I haven't seen any dislike yet but I have IAM service getting evolved over year with new features for reporting and simplied UI Review collected by and hosted on G2.com.

Aws cloud is top most used cloud provider in world with best security function and access control Review collected by and hosted on G2.com.

Some functionality is complex but its easy to understand Review collected by and hosted on G2.com.

IAM has roles, policies and users which we can manage all in one place, I can allow some resource to access read write another resource or I can allow one user access to something or not. It helps a lot with access management while using lambda functions. Not every lambda has to have access to everything. It is very frequently used to give access to lambda functions. The integration is very easy it is directly attached using the console and needs policy names on SAM templates to give access. Review collected by and hosted on G2.com.

It is a sopisticated program, works all of the time, but writing custom policies and attaching inline policies could have been made easier with policy builders but you can do that already upto some extent. Implementation on SAM templates could have been easier. Review collected by and hosted on G2.com.

IAM makes access management very easy and enable it pod level and as well as application level. It gives better security to avoid unauthorised access. Review collected by and hosted on G2.com.

Nothing as such about IAM, very useful feature. Review collected by and hosted on G2.com.