I appreciate how AWS Identity and Access Management (IAM) allows me to create IAM users for team members with role-based access. I like that I can give the exact permissions to users or services using roles and policies, from the least to the highest privilege. It's great for ensuring fast onboarding with roles and groups for new users, providing strong security with least privilege, and there are no keys to handle. The easy auditing and permission management are big pluses. I also enjoy the smooth scaling as the team grows, quick access setup, and fewer permission issues. IAM's least privilege feature helps in preventing accidental deletion. Review collected by and hosted on G2.com.

Debugging access denied takes time and the user interface can be slightly better. I would like a one-click debugger to auto-trace since there are multiple layers at each level like group, role, and resources. I mean, clear visibility of the deny source. Review collected by and hosted on G2.com.

AWS IAM helps in managing users and permissions in a very secure way. I like how it allows fine-grained access control using roles and policies. It integrates well with other AWS Services and reduces the need to share credentials. Once you understand the basics, it becomes very reliable for managing access. Review collected by and hosted on G2.com.

The initial learning curve a bit high, especially for beginners. Understanding policies and permissions takes time and can be confusing at first. The interface could be simpler, as small mistakes in policies may cause access issues. Review collected by and hosted on G2.com.

AWS IAM offers strong security and granular control over access to AWS resources. Once configured, it is easy to manage users, roles, and permissions across services. It integrates seamlessly with other AWS tools, supports MFA, and is used frequently in day-to-day operations, making it a reliable solution for access management. Review collected by and hosted on G2.com.

The main challenge with AWS IAM is ease of use for beginners. The interface and policy syntax can be complex during initial setup, and troubleshooting permission issues can take time. While documentation is detailed, direct customer support is limited unless you have an AWS support plan. Review collected by and hosted on G2.com.

I think AWS Identity and Access Management (IAM) is great for learning about AWS. It helps me understand security, MFA services, and AWS policies, which enhances my knowledge of security technologies. I find it beneficial for enabling MFA, using IAM policies instead of inline policies, and performing regular audits to manage permissions and delete unused entities. I also find the initial setup of AWS IAM easy, making it a helpful tool for beginners to dive deep into learning about AWS. Review collected by and hosted on G2.com.

I find AWS Identity and Access Management (IAM) setups complex. It feels very large, and there's limited support for applications. There's also a lack of centralized visibility, which could be more streamlined. Review collected by and hosted on G2.com.

The level of control and flexibility it gives over access to AWS resources. You can define very granular permissions using policies, which makes it easier to follow the principle of least privilege and keep environments secure. Managing users, roles, and permissions in one central place is convenient, especially when working across multiple services and teams Review collected by and hosted on G2.com.

The UI is functional but not very intuitive, which makes managing permissions at scale harder Review collected by and hosted on G2.com.

What I like most about AWS IAM is its user-friendly, intuitive interface, which makes it easy to create and manage users, groups, and policies. Review collected by and hosted on G2.com.

What I don’t like is that you often have to create roles just to connect with another account, and it feels a bit heavy and cumbersome to me. Review collected by and hosted on G2.com.

I like the flexibility that AWS Identity and Access Management (IAM) has for creating detailed policies, which allows us to give each developer exactly the permissions they need for their work without giving them access to things they don't use. Additionally, it integrates well with all of AWS, making it easy to configure because it is already connected with S3, EC2, Lambda, and more. Review collected by and hosted on G2.com.

Sometimes the interface is a bit confusing, especially when you are creating new policies since you have to go back and forth between screens. It would also be good to have better documentation with more real examples. Review collected by and hosted on G2.com.

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.

I really like AWS Identity and Access Management (IAM) because it enables me to secure and control access to AWS services and resources by managing user permissions effectively. I appreciate that it acts as a gatekeeper, allowing me to grant different permissions to different people. I also like that it enforces multi-factor authentication, which is a significant security feature. The initial setup was very easy to do, and everything works great. I have never had any issues with it. Review collected by and hosted on G2.com.

Everything works great and no problems Review collected by and hosted on G2.com.

Use of security, sharing the access of that services of AWS only which is needed to the IAM User without sharing the root user access.

using IAM user AWS access is safe & organized. Review collected by and hosted on G2.com.

In case of many IAM user hard to track the data. debugging it takes alots of time. Review collected by and hosted on G2.com.