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.
At G2, we prefer fresh reviews and we like to follow up with reviewers. They may not have updated their review text, but have updated their review.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.
