AWS IAM Reviews

What do you like best about AWS Identity and Access Management (IAM)?I like that AWS Identity and Access Management (IAM) helps ensure our security and provides a good way to manage AWS, especially since we operate across several servers on the West Coast. I also appreciate that it gives us a way to log in and check our billing standpoint, which is crucial for managing our usage and funds, especially during times of company growth. This billing element of IAM has been particularly valuable for us.What do you dislike about AWS Identity and Access Management (IAM)?We had a significant issue with logging in for quite a while, and there was confusion between IAM root access and other types, which was causing us some consternation. Moreover, it was difficult to find the billing elements for us.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?I use AWS Identity and Access Management (IAM) to ensure security, manage AWS resources across servers, and oversee billing to optimize our costs during growth. IAM lets me view our AWS bills, usage, and identify areas to suspend services.

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. What do you dislike about AWS Identity and Access Management (IAM)? Recommendations to others considering AWS Identity and Access Management (IAM)?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. What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?

What do you like best about AWS Identity and Access Management (IAM)?What I like most about AWS IAM is how securely it lets me manage users, roles, and permissions through fine grained access control. It integrates smoothly with other AWS services, supports multi factor authentication (MFA), and aligns well with the principle of least privilege. Overall, it helps me maintain strong security without getting in the way of productivity.What do you dislike about AWS Identity and Access Management (IAM)?The policy syntax can be difficult to understand at first, and configuring permissions for complex environments can take time. Better visualization and easier policy management would make it more user friendly.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?AWS IAM helps us securely manage access to AWS resources by clearly controlling who can access what. It lets us assign the right permissions to users and applications, which strengthens security, reduces the risk of unauthorized access, and makes access management simpler across our AWS environment.

What do you like best about AWS Identity and Access Management (IAM)?What I like best about AWS Identity and Management is that it provides fine-grained access control and security across the AWS environment. What I like most is that it helps enforce least-privilege access to sensitive data, which is the part I value the most. It also supports role-based access for teams working in a shared cloud environment.What do you dislike about AWS Identity and Access Management (IAM)?I don’t have any major dislikes; it’s a good product overall.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?It mainly solves problems like securely managing acess to aws resources and control permissions. It basically ensures secure acess management for services like S3 and red shift.

What do you like best about AWS Identity and Access Management (IAM)?The granular, policy-based access control lets you enforce least-privilege permissions across every AWS service, making it easy to manage security at scale without compromising flexibility.What do you dislike about AWS Identity and Access Management (IAM)?The policy syntax can be complex and verbose, and debugging permission errors is frustrating — the error messages rarely tell you exactly which policy is blocking access.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?It centralizes user access control and eliminates the need for shared credentials, ensuring only the right people and services have access to the right resources — significantly reducing security risk.

What do you like best about AWS Identity and Access Management (IAM)?AWS IAM is the foundation for secure access control in AWS and one of the most critical services for managing permissions at scale. It provides fine-grained control over users, roles, groups, and policies, which helps enforce least-privilege access across teams and workloads. IAM roles are particularly powerful for granting services the access they need without hardcoding credentials. Integration across AWS services feels seamless, and capabilities such as MFA enforcement, access key management, and policy evaluation tools make it easier to maintain strong security practices in both small and enterprise environments.What do you dislike about AWS Identity and Access Management (IAM)?The biggest challenge I’ve had with IAM is its complexity. Policies can quickly become hard to manage and troubleshoot, especially in large environments with many accounts and services. Writing JSON policies is also error-prone; even small mistakes can cause unexpected access problems or result in configurations that are more permissive than intended. For new users, the learning curve is steep, and in my experience it takes strong internal standards, consistent naming conventions, and solid documentation to keep everything organized and maintainable over the long term.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?AWS IAM addresses the core challenge of controlling who and what can access AWS resources. It provides secure authentication and authorization across cloud environments by letting you define precise permissions for users, applications, and services. This helps reduce the risk of misconfigurations, supports compliance requirements, and makes it easier to manage access at scale across teams. By using IAM roles and policies, we can apply least-privilege security, avoid sharing credentials, and operate production workloads with confidence thanks to clear, well-defined access boundaries.

What do you like best about AWS Identity and Access Management (IAM)?What I value most about AWS IAM is the granularity of access control through policies. You can define permissions at the level of specific action, resource, and condition, which is essential in data architectures where multiple services (Glue, Athena, S3, Lambda, Step Functions) need to interact securely. IAM roles for services eliminate the need to manage static credentials, and integration with AWS Organizations allows for scaling permission management across multiple accounts without friction. The "least privilege" model is easy to implement with managed policies and inline policies.What do you dislike about AWS Identity and Access Management (IAM)?The learning curve for policies in JSON can be steep at first, especially when working with complex conditions or cross-resource permission models. Debugging access denied errors is not always intuitive: the Policy Simulator helps, but it doesn't cover all scenarios, and error messages in services are sometimes not very descriptive. Additionally, managing permissions at scale becomes difficult without a clear strategy from the start; it's easy to accumulate redundant roles and policies over time.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?IAM solves the central problem of controlling who can do what on which resources in AWS. In complex data architectures, this is critical: it allows services like Glue, Lambda, and Step Functions to operate with minimal and well-defined permissions, without sharing credentials. It also addresses the auditing and traceability of actions through CloudTrail, which is essential for compliance and troubleshooting. The direct benefit is being able to build secure data pipelines where each component has exactly the permissions it needs, without overexposing sensitive resources like S3 buckets or databases.

What do you like best about AWS Identity and Access Management (IAM)?What stands out about AWS Identity and Access Management is its precise control over permissions and consistent integration across all AWS services. What do you dislike about AWS Identity and Access Management (IAM)? Recommendations to others considering AWS Identity and Access Management (IAM)?You can enforce least-privilege access with detailed policies and use roles with temporary credentials for better security. What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?

What do you like best about AWS Identity and Access Management (IAM)?AWS IAM is very easy to use and configure. I’ve used IAM many times, whether we were integrating third-party applications or provisioning AWS access for users. What I appreciate most is how straightforward it is to work with, especially with the robust documentation and support that walk you through the full process of creating policies, roles, and users. Since IAM is a free service, there’s no added cost we need to worry about. It also runs smoothly and quickly, with virtually no delay. Amazon Q can also help by providing AI-based assistance to guide you through IAM tasks.What do you dislike about AWS Identity and Access Management (IAM)?What I dislike about IAM is the limited level of control. For example, the security controls for users and user groups could be more robust, as there’s still room for improvement in that area.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?Multiple needs such as role-based access control, creating policies to access specific AWS services, and setting granular permissions across AWS services can all be achieved using IAM. IAM is also crucial for integrating with third-party tools for log collection and for working with APIs.

What do you like best about AWS Identity and Access Management (IAM)?I like best about the AWS Identity and Access Management is its strong security, fine-grained access control, and easy integration with other AWS services, allowing administrators to manage users, roles, and permissions efficiently while ensuring least-privilege access, multi-factor authentication support, and centralized contol without additional cost since IAM included with AWS.What do you dislike about AWS Identity and Access Management (IAM)?I dislike about AWS Identity and Access Management is that its interface and permission policies can be complex for beginners, managing large numbers of roles and policies becomes difficult without proper structure, troubleshooting access issues can be time-consumin, and the documentation, while detailed, can feel overwhelming when trying to configure advanced permissions.What problems is AWS Identity and Access Management (IAM) solving and how is that benefiting you?AWS Identity and Access Management solves the problem of security managing access to AWS resources by allowing me to control who can access which services using roles, policies, and permissions, which benefits me by improving security, enabling least-privilege access, simplifying user management across multiple services, and reducing the risk of unauthorized access while keeping everything centrally controlled.