G2

Kamesh G.

ATL

Mid-Market (51-1000 emp.)

4/30/2026

Business partner of the seller or seller's competitor, not included in G2 scores.

"Make it specific and descriptive, for example 'Game-changer for team collaboration"

5/5

What do you like best about AWS Identity and Access Management (IAM)?

The biggest strength is its fine-grained permission system. You can define policies that allow or deny very specific actions (down to a single API call on a single resource). That level of control is hard to match and becomes essential in production environments.

Another standout is centralized security management. Instead of scattering credentials everywhere, IAM lets you manage users, roles, and permissions in one place. This becomes especially powerful when combined with roles—services and users can temporarily assume permissions instead of relying on long-term credentials.

I also like its tight integration across AWS services. IAM is not an add-on; it’s deeply built into everything in AWS. Whether you're using EC2, S3, or Lambda, IAM policies consistently control access, which keeps your security model uniform. Review collected by and hosted on G2.com.

What do you dislike about AWS Identity and Access Management (IAM)?

IAM is extremely powerful, but that power comes with complexity, and managing it well takes experience and good practices. Review collected by and hosted on G2.com.

What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?

1. Problem: “Who should have access to what?”

In any system, not everyone should be able to do everything. IAM solves this by letting you define exact permissions for each user, role, or service.

Benefit: You can enforce least-privilege access, which reduces mistakes and security risks.

2. Problem: Managing credentials safely

Without IAM, you’d end up sharing passwords or embedding keys in code.

Benefit: IAM provides roles and temporary credentials, so you avoid hardcoding secrets and reduce the chance of leaks.

3. Problem: Scaling access as teams grow

Manually managing access for dozens or hundreds of users becomes chaotic.

Benefit: With IAM groups and roles, you can manage permissions centrally and apply them consistently across your organization.

4. Problem: Lack of accountability

If everyone shares credentials, you can’t track who did what.

Benefit: IAM integrates with logging (like CloudTrail), so you get clear audit trails—important for debugging and compliance. Review collected by and hosted on G2.com.