My main use case for IAM Health Cloud is managing identity and access management of the company in my day-to-day activities.

One specific example of how I use IAM Health Cloud to manage identity and access is by following the principle of least privileged access. One of the data and analytics team members needed data modeling access. They use SageMaker and an S3 bucket. So I created a custom role in IAM Identity Center because we use IAM SSO, single sign-on, and we manage 45 AWS accounts. I go to the master account and I create a custom role for this specific data and analytics user to have SageMaker, Bedrock, and S3 access. That's all I have to add about my main use case or any other ways my team relies on IAM Health Cloud.

In my opinion, the best features IAM Health Cloud offers are managing security by providing role-based access control, which really stands out for me.

The role-based access control makes things easier for me because we have DevOps engineers who need power user or privileged access, kind of admin access, to manage the entire company AWS accounts and infrastructure. There are some testers who don't require power user or admin roles, so they just get read-only access. Some business analysts require only Athena, Glue, and S3 read-only access, so those are some use cases I can describe for role-based access control.

IAM Health Cloud has positively impacted my organization by giving us all the required dashboards that we can manage everything from one place.

Having that centralized dashboard has helped us by allowing us to manage all access from IAM Identity Center where we create permission sets and roles. In other terms, it is a role that we can manage and assign to the respective account or respective group from IAM Identity Center. This means I don't have to go to each AWS account to create a role or create an access group. I manage everything from the master AWS account IAM Identity Center.

I faced challenges earlier when I selected a role; it wasn't showing in any account it was associated with. It wasn't listing the account it was associated with, but later that feature came through and I am able to see that. When I select the role, this role is part of these many accounts or this particular account.

I don't have anything else to add about the needed improvements at this point.

I choose an eight out of ten because I think this technology world is evolving very rapidly and AI is stepping into the technology. AI growth is so fast, and I would think there should be some AI capabilities within IAM Health Cloud so that it would better serve the customers.

I have been using IAM Health Cloud for four years.

IAM Health Cloud is stable; I think recently there was a couple of AWS downtimes. In November, there were a couple of incidents where AWS was down in mostly the US-East-1 region.

IAM Health Cloud's scalability is good; it handled my organization's growth well.

The customer support for IAM Health Cloud is good, and it is fast. We used it, not me personally, but my team used it.

I would rate the customer support an eight on a scale of one to ten.

Positive

I am not sure if I previously used a different solution before IAM Health Cloud because when I started working in this company, they implemented it.

I purchased IAM Health Cloud through the AWS Marketplace.

My company does not have a business relationship with this vendor other than being a customer. We are just a customer.

I have seen a return on investment with IAM Health Cloud in terms of time saving.

My experience with pricing, setup cost, and licensing for IAM Health Cloud is okay. Every buyer wants a cheaper price.

I don't know if my company evaluated other options before choosing IAM Health Cloud; by the time I joined this company, they were already using it.

My advice to others looking into using IAM Health Cloud is that it is very useful. It is one place to manage everything, and it's a time-saving solution. I give this product a rating of eight out of ten.