AWS IAM Identity Center Reviews

My main use case for AWS IAM Identity Center is hosting and redirecting web services that I want to use as localhost, but then I have to reroute it. What I did was create a permission set and use it for multiple collaborators on the same project.

The permission set assisted the workflow because it made it faster and easier for people to jump in on the project and also be able to fetch the code and review it. A quick example of how it was used is by setting up the permission set as the admin so that those other collaborators could view or access what I was doing as the admin, and I could also see what they are doing and monitor their work.

AWS IAM Identity Center makes the work faster and more transparent between the developers.

AWS IAM Identity Center has positively impacted us by making it seamless for developers to create temporary, secured credentials for them to join the workflow and also cut down costs. Initially, I used to pay for most cloud services, but now I have access to the temporary free access, and then when I exhaust that, I move to the paid system.

It has increased the workflow percentage by over 20 to 30%, making it very effective for us to actually achieve the work we're trying to do in a short amount of time. It has also given me, as the admin, the full governance to ensure that if someone is not doing the task they are supposed to be doing or if they are trying to act in an inappropriate manner, I can revoke their access. AWS IAM Identity Center has impacted us very positively.

One of the best features AWS IAM Identity Center offers is the permission set, which is one of the best. Then there are the temporary credentials via SSO, the multi-account governance, and the centralized identity management. Those are good features that I believe assist developers, and another feature I can say is one of the best is the improved security with temporary credentials.

The feature I find myself relying on the most day-to-day would be the centralized identity management and multi-account governance. It allows me to check what other developers are doing and since I am the admin, I can also revoke the access they have to the AWS accounts.

I think AWS IAM Identity Center can be improved by making it beginner-friendly. It was very hard for me to navigate initially because the UI was very complicated. I had to do a lot of research and watch a lot of videos, but I feel that if they can make it beginner-friendly, specifically the UI, it would help a lot.

I do not think there is anything else that needs to be improved besides the UI or onboarding experience. Everything else just automatically fell in place for me once I was past the beginner stage.

I have been using AWS IAM Identity Center for seven months plus.

The advice I will give to people who want to use AWS IAM Identity Center is to go ahead. It is a very great tool and very useful for big companies that actually require managing their staff's effectiveness. It is worth the money and the time, and it can actually save a lot of money and time as well.

I choose a rating of seven because many people actually want something that is free, even if it is not very useful to them. However, at least knowing that there is a free alternative out there puts their mind at ease. AWS, unless someone is creating a new account, does not offer free usage to their tools. I cannot blame them as they also need to make their own money, but I feel that if someone has something good, they can actually share without having to limit it to being paid completely. Perhaps they can release a tool or a tier that is free, apart from a new account, so that it is not as if every time someone needs AWS credits or wants to bypass their system, they have to create a new AWS account just to get access to those features.

I work as a DevOps engineer, leveraging AWS services extensively to manage cloud infrastructure. My primary use case revolves around securing and automating the deployment of applications within AWS. Specifically, I use AWS Elastic Kubernetes Service (EKS) for container orchestration, S3 buckets for data storage, and CloudFormation to implement Infrastructure as Code (IaC) for provisioning resources.

For monitoring and alerting, I rely on Amazon CloudWatch to gather logs and metrics, ensuring system performance and operational health. AWS IAM plays a crucial role in managing access and enforcing security policies, providing fine-grained access control for users and services.

Additionally, I use AWS Key Management Service (KMS) to handle encryption keys for sensitive data, ensuring compliance with security policies. My environment also includes EC2 instances for compute resources, Elastic Load Balancers (ELB) to distribute traffic efficiently, and RDS for database management.

AWS IAM Identity Center has significantly improved our organization by streamlining access management. It centralizes user identity and permissions across multiple AWS accounts, simplifying onboarding and offboarding processes. By enforcing role-based access control (RBAC), it ensures users have the minimum necessary permissions, which strengthens security and reduces the risk of over-provisioning. The seamless integration with our identity provider has enhanced user management efficiency, allowing for smooth synchronization of user roles and access across services. Overall, IAM Identity Center has played a crucial role in improving both security and administrative efficiency, helping us maintain a strong security posture while minimizing manual management efforts.

AWS IAM is central to cloud security and resource management, providing robust features for managing access. Its granular access control allows precise management of who can access specific AWS resources and under what conditions through JSON-based policies. Additionally, attribute-based access control (ABAC) enhances flexibility by enforcing policies based on user attributes, reducing the need for constant policy updates. Multifactor authentication (MFA) strengthens security by requiring additional verification steps, protecting against unauthorized access. IAM roles enable temporary access to resources, ensuring secure cross-account access while maintaining the principle of least privilege. Other valuable features include service control policies (SCPs) for centralized governance across AWS accounts and IAM Access Analyzer for auditing and identifying any unintended access, ensuring ongoing security and compliance.

Managing IAM in complex environments can be challenging, and there are several areas for improvement. First, incorporating automation tools or a centralized dashboard for managing roles and policies across multiple accounts would simplify administration, especially for large organizations.

Additionally, policy debugging and validation could be more streamlined, as troubleshooting misconfigurations can be time-consuming and prone to errors. A more robust error messaging system or a dedicated debugging tool would be beneficial.

Another area for improvement is temporary access credentials. AWS documentation should offer more detailed guidance on edge cases and exceptions, along with clearer examples of how to handle various scenarios.

Lastly, enhanced session-level policies that are more context-sensitive and based on specific conditions (such as IP address, device, or time) would greatly increase flexibility and allow for more granular control over user sessions.

I've been using IAM solutions, particularly AWS IAM, for over three years as part of my DevOps work. During this time, I've managed access control, implemented least-privilege policies, and ensured secure authentication and authorization processes across cloud environments.

I find IAM to be very stable, offering high availability and robust security. AWS consistently provides updates and improvements, ensuring that IAM remains reliable and secure. While there may be occasional exceptions or edge cases, AWS generally addresses these promptly through patches or updates. Overall, IAM's stability is a strong point, and its performance in handling large-scale, mission-critical applications reinforces its reliability.

I find IAM to be highly scalable, supporting organizational growth and adapting well to increasing complexity in cloud environments. It efficiently handles a growing number of users, roles, and policies across multiple AWS accounts. The integration with AWS Organizations also makes it easy to scale access management in large, multi-account environments. Given its flexibility and ability to manage complex security requirements, I would rate its scalability nine out of ten.

We haven't had to contact AWS technical support directly, but we appreciate the range of support plans AWS offers. The Basic Support Plan provides access to essential resources, such as comprehensive documentation and tools like AWS Trusted Advisor, which helps with best practices and optimization recommendations. For more complex issues, higher-tier support plans are available, offering 24/7 access to AWS experts. While we’ve managed without escalating issues to AWS support, the resources available have been sufficient for most of our needs.

Neutral

Previously, we used Azure Active Directory for identity management, but we switched to AWS IAM due to its seamless integration with AWS services and its flexibility in managing access within AWS environments. IAM provides more granular control over resource permissions and better aligns with our cloud-native infrastructure. Additionally, we've also used Okta for enterprise identity management, which offers strong integration with various applications, but IAM remains our preferred choice for AWS-specific access management due to its native capabilities and deeper AWS ecosystem integration.

The initial setup of IAM is relatively straightforward for simpler environments, but it can become more complex as your infrastructure grows. For basic setups, it involves securing root accounts, creating users and groups, assigning roles, defining permissions with policies, implementing password policies, enabling MFA, and setting up monitoring with tools like CloudWatch. As the environment scales and becomes more complex, managing cross-account access, implementing service control policies, and ensuring proper integration with other AWS services can increase the complexity. However, with good planning and organization, these challenges can be effectively managed.

For small-scale deployments, the implementation typically involves one to two people from our in-house team, which can handle the setup and configuration efficiently. For medium-sized environments, a team of two to five people is usually required to manage roles, policies, and security configurations. In larger-scale deployments, tasks are often divided among multiple team members to address different aspects such as cross-account access, policy management, and monitoring setup. We handle most of the deployment in-house, and when necessary, we bring in external expertise for complex scenarios. The level of expertise required depends on the scale, but for larger implementations, a well-coordinated team approach is essential.

The return on investment (ROI) with AWS IAM is substantial. Key benefits include improved operational efficiency, as it streamlines access management and reduces administrative overhead. IAM also helps in reducing security risks by enforcing fine-grained access control and supporting multi-factor authentication (MFA), which strengthens overall security. Additionally, IAM aids in compliance with industry regulations by enabling detailed access auditing and reporting. It enhances user experience through seamless, centralized access management, and drives productivity by simplifying the onboarding and offboarding process. Overall, IAM significantly improves our security posture and reduces manual workload, providing a strong ROI when implemented correctly.

I recommend that others take advantage of AWS IAM's free tier for creating and managing users, groups, and roles, as it provides robust functionality without any additional cost. However, it's important to note that certain advanced features, like AWS IAM Access Analyzer and Multifactor Authentication (MFA), come with additional charges. While the basic IAM service is free, organizations should factor in the costs for these premium features when planning their budget. It's also important to consider the potential costs associated with cross-account access and identity federation, depending on the complexity of your IAM setup.

We evaluated other options, but since the majority of our cloud environment is based on AWS, IAM emerged as the most integrated and adaptable solution. We considered other identity management solutions like Azure Active Directory and Okta, but IAM’s seamless integration with AWS services, its fine-grained access control, and its native security features made it the best fit for our needs. The ability to manage access across a wide range of AWS services and resources with a consistent, unified approach was a key factor in our decision.

Overall, I would rate IAM Identity Center an eight out of ten. It provides solid functionality for managing user identities and access across AWS accounts, but there is room for improvement. Specifically, I would like to see better documentation, particularly around edge cases and security exceptions. Clearer guidance on handling complex access scenarios would make troubleshooting and implementation smoother. Additionally, more granular control over session management and enhanced support for cross-service integrations could further elevate the solution.

I am using AWS IAM Identity Center for two-factor authentication where we can set up the authentication protocols. We can set which services a particular user can use, how we can assign them to particular services, and establish trusted policies with specific access levels. This is where AWS IAM Identity Center helps.

When discussing role-based access control, I refer to AWS IAM Identity Center in relation to Amazon Q because when using Amazon Q, there is a subscription type according to the users. One user costs approximately $25 per month. AWS IAM Identity Center helps us manage users according to how many need access. If you give one user access to Amazon Q, it costs approximately $25 per month. This allows us to restrict users and revoke access anytime if someone is misusing it.

The features of AWS IAM Identity Center that I appreciate are single sign-on and multi-factor authentication. There is also password management capabilities, and we can manage all authentication aspects. We can also integrate it with third-party applications.

With AWS IAM Identity Center, I have minimized access policies and managed to maintain compliance and overall oversight.

The main benefits from AWS IAM Identity Center are single sign-on, multi-factor authentication, and integrating AWS services with our products. It provides a user-friendly interface that serves as a good resource.

The tech support for AWS is time-consuming, as we have experienced this issue. However, I am not aware of many other cases.

I have been working with AWS IAM Identity Center for six months. When using Amazon Q, I need to set up users, assign trusted policies, and restrict them with other services.

Regarding technical support for AWS IAM Identity Center, we haven't faced any issues currently. When we need assistance, we reach out to their support portal, and they resolve our issues.

Positive

The initial setup of AWS IAM Identity Center was straightforward. We had to sign up as a root user to AWS, then the root user creates additional users and provides access to the remaining users. It is not a difficult task to set up.

From my perspective, AWS IAM Identity Center is already enhanced and has many capabilities, covering numerous areas. I don't think they need any improvements currently. It works well for us. If users want single sign-on and multi-factor authentication, they can easily opt for AWS IAM Identity Center.

I recommend AWS IAM Identity Center as it is beneficial to use. It helps significantly in maintaining users within products.

I would rate AWS IAM Identity Center as nine out of ten because we use it as our main primary sign-on feature for our product. Sometimes it experiences lag, but there's always room for improvement, which is why I deducted one point.

The primary use case for AWS IAM Identity Center is setting up permissions, policies, and groups for different users or customers. For instance, the engineering team has different accounts and is provided different access levels through using AWS IAM Identity Center. Similarly, the DevOps team has access levels tailored to their specific requirements. It is mostly used for segregating the access for different teams according to their needs.

AWS IAM Identity Center has helped our organization by providing a unified dashboard to manage permissions and access controls. I can control and set up policies for least privilege, enhancing security by having a record of users and the accounts they have access to. This centralized management is quite helpful as it reduces the need to access each account individually, providing efficiency and security in managing access.

The most valuable feature of AWS IAM Identity Center is the ability to provide a structured approach to access management through a single dashboard. This single-pane management allows users to manage access control and permissions centrally. It provides the least privilege-based access control, which limits users to only the operations they need to perform without interfering with unrelated configurations.

The configuration with other tools can be hard. Integrating AWS IAM Identity Center with other applications sometimes presents challenges. Specifically, when configuring it with third-party tools, like Active Directory, the naming convention of permission sets requires careful attention, which can be confusing.

I have been working with AWS IAM Identity Center for around two to three years.

I'm giving it an eight out of ten for stability. There can be issues if there is an outage on AWS's side, which could prevent logging in because your region might be down, affecting the Identity Center's availability.

I rate the scalability of AWS IAM Identity Center as seven out of ten. The syncing of user groups with naming conventions and integrating with third-party tools could be improved to enhance scalability.

I haven't asked for any technical support. I've rated the technical documentation as a seven out of ten. The documentation tends to be hard to understand due to its length and the lack of pictorial representations.

Neutral

I rate the initial setup process as seven out of ten. It's not simple, and requires knowledge of IAM and organizational structures to configure.

I am not sure about the pricing model. The expenses are believed to be based on users and permission sets. It is not that expensive, rated at three out of ten for costs.

AWS IAM Identity Center was compared with other solutions like Okta.

New users should ensure AWS IAM Identity Center is compatible with all applications they intend to integrate. It's beneficial as it provides CLI credentials and can reduce the need for other third-party tools like Okta or Single Login since it utilizes native AWS services.

I'd rate the solution eight out of ten.

I work as a consultant, setting up AWS accounts for clients. A significant requirement is creating IAM security profiles for all services and users. This involves creating specific sets of credentials with limited privileges for AWS developers during testing, deployment, and login, using scripts for automation to enhance security.

IAM Identity Center provides micro-level control over resources, services, and users, allowing organizations to grant specific access and privileges safely. The capability to create scripts for generating credentials enhances the security management compared to other services.

The two most valuable features of IAM Identity Center are the security policy generation and automation in creating credentials. Security policies can be created as JSON formats, allowing them to be easily edited and managed. These features allow for excellent micro-level control over resources, ensuring specific permissions are granted. 

Compared to other services, AWS IAM allows for a granular approach, preventing misuse by providing resource-based and service-based privileges.

Greater visualization for security policies would be beneficial. Although IAM has an integrated development environment called AWS Policy Generator, it is not integrated with IAM Identity Center. Integrating this directly could improve ease of use for generating security policies. 

Additionally, beginners might find IAM extensive due to its detailed nature, which could be mitigated by providing better presets and easier visualizations.

I have been working with IAM Identity Center for probably six to seven months, however, I learned the tech stack about a year ago.

IAM Identity Center is ten in stability. As a configuration service operating on AWS itself, it doesn't provide stability issues and works seamlessly.

IAM Identity Center is highly scalable, rated nine out of ten. It supports extensive automation and scripting, and roles can be easily managed. Users can be shifted among roles without much change needed from their end, simplifying changes in organizational structures.

I haven't had any issues with IAM Identity Center. AWS offers better assistance plans for their services, and issues related to security configurations are typically second priority, indicating good support.

Positive

The initial setup isn't very easy, around four on a scale of one to ten. It permits setting up policies that might not be entirely secure if improperly configured, which can lead to issues later. It's easy to start but can result in complications if not properly managed.

I advise new users to always use the AWS Policy Generator to generate policies rather than relying on generalized presets that provide access to all services. I rate IAM Identity Center as nine out of ten. Although it can improve, it is almost perfect.

The primary use case of AWS IAM Identity Center is primarily for identity management and for providing access to administer the actual console for user accounts. Additionally, it is used to manage multiple AWS accounts and create different companies within a particular account, allowing the management across companies.

The organizational value of AWS IAM Identity Center is definitely significant, as it helps ensure that the least required permissions are given to users, thus preventing unnecessary access and reducing the risk of accidental deletions or changes. The transition from previous solutions to AWS led to an evident decrease in issues, reflecting a positive impact on operations.

The most valuable features of AWS IAM Identity Center are role-based permissions and existing permissions templates. These features prevent reinventing the wheel by providing pre-existing templates that are easy to use, allowing the appropriate allocation of permissions without manual configuration.

There is a desire to see integration or adoption of time-based user creation features within AWS IAM Identity Center. This involves creating a user with necessary permissions valid for only a specific period and then automatically revoking access.

I have been working with AWS IAM Identity Center since 2018, which is approximately six or seven years.

The stability of AWS is very high. It offers 99.96% uptime, and I have not faced any downtimes or stability issues.

The scalability of AWS IAM Identity Center is excellent. It allows the creation of groups and role-based access, which can accommodate a large number of users without impacting performance.

Although I have not had to contact IAM support specifically for issues, my experiences with AWS premium support in other areas have been stellar. They are prompt, keep you updated, and provide excellent assistance.

Positive

Previously, if someone needed access, they were given administrator access without using specific identity management software. This approach was unstructured and prone to issues.

The initial setup process is relatively easy, rated at seven out of ten. The main challenge is the learning curve when transitioning from older systems like Microsoft Active Directory.

Organizationally, the ROI includes a significant reduction in issues compared to previous ad hoc solutions. While specific metrics are not provided, the transition to AWS has clearly reduced problems.

Pricing for AWS IAM Identity Center is very affordable, rated at two out of ten with one being cheap. It provides decent pricing for its features.

I did not evaluate other options; I went straight for AWS IAM Identity Center due to my preference and familiarity with AWS services.

No specific advice except that new users should give IAM Identity Center a try as they are likely to be satisfied with its performance and capabilities.

I'd rate the solution nine out of ten.

AWS IAM Identity Center is used primarily to centralize access across different departments within an enterprise. It allows users from various departments to manage their access seamlessly through a single portal, enhancing efficiency and security.

AWS IAM Identity Center offers a secure and centralized way to manage access and permissions. It simplifies access management by allowing users to manage multiple accounts from a single portal without remembering multiple credentials. 

The solution enhances security through features like multifactor authentication. Administrators can define precise permission policies in Identity Center, ensuring users have the correct access.

For AWS services in general, I had trouble creating an S3 bucket due to a repetitive error message regarding existing names. A direct chat option with technical support could also enhance the user experience.

I have been working with AWS IAM Identity Center for approximately two years.

AWS IAM Identity Center is very stable. There have been no significant performance issues. Occasionally, I face page refresh issues, which might be related to my browser or internet connection.

The scalability of AWS services, including Identity Center, is quite significant. The service is adaptable, and scaling is easy when properly configured, catering to enterprise needs. AWS Identity Center successfully supports scalable deployments, allowing additional resources as the company grows.

I have opened support tickets and received responses, although not always resolving my queries fully. I would appreciate a live chat option with technical support for quicker resolutions.

Positive

I did not have previous experience with other single sign-on solutions before using AWS IAM Identity Center.

The initial setup involved organizing users into groups based on departments within AWS Identity Center. After establishing AWS organization units, users were created and assigned to these groups with the necessary permissions.

The cost-saving aspect of using AWS IAM Identity Center is apparent. It provides enhanced security and simplifies resource management for users.

AWS IAM Identity Center is available as a free service by default. There is no pricing associated with its usage for my setup.

I definitely recommend AWS IAM Identity Center to others. It simplifies organization and access management. 

For the overall solution, I would rate it eight out of ten.

I am more of a developer and often test solutions by creating infrastructure while working with AWS services. Our main use case involves managing multiple AWS accounts through IAM Identity Center for roles and permissions, like creating users, providing access to specific AWS services, and managing connectivity between services with MFA and role creation.

The solution helps us manage access in a time-efficient manner and offers reliable integration for our services, avoiding security breaches and maintaining operational efficiency.

The security perspective, especially role-based access control, is a significant strength. It enhances infrastructure on the cloud. The service's security aspects, including the creation of policies and role-based access controls, are incredibly beneficial. The inline policies feature ensures that even new users can understand complex security configurations, ensuring smooth cloud operations.

I would like to see an increase in available resources and custom features, as these could enhance the current capacity of operations without removing existing accesses.

I have been using AWS IAM Identity Center for around three years, acting as an administrator while working with AWS Cloud.

The solution is stable, rated at nine, and it doesn't require much human intervention, allowing us to save resources.

Scalability is between eight and nine. Though handled by different teams, this aspect of AWS ensures that large-scale infrastructures are maintained efficiently.

Customer service is dependable with a rating of nine. AWS provides immediate solutions and assistance whenever needed, especially if issues arise that cannot be handled internally.

Positive

Previously, we used on-premises solutions managed manually through Linux infrastructure. Third-party tools were also involved, but AWS IAM Identity Center offered a more integrated and cloud-based approach.

The initial setup took about seven to eight days, and although the process was complex due to on-premises infrastructure, assistance from team members made the transition to the cloud smooth and efficient.

Our implementation team consisted of about five to six people who addressed different cloud components to ensure proper configuration and prevention of service disruption.

We have achieved significant time efficiencies with AWS IAM Identity Center. The solution enables operations to run smoothly and reliably without direct cost benefits.

In the project, our customer heavily relies on AWS Cloud for most services, limiting the need for other solution evaluations or vendor options.

Anyone looking to use this solution should have a basic understanding of JSON and technology to comprehend the policies associated with AWS IAM Identity Center. Familiarity with firewalls and integration capabilities is crucial. Additionally, I rate this product at nine out of ten.

I am an integrator for IAM Identity Center. I use it for different services, providing AWS to my customers. My role involves creating solutions that cater to client requirements, such as managing permissions and privileges across various AWS services.

AWS IAM is essential because it manages service access and permissions. This management is crucial to any AWS account, allowing us to access the services and perform various tasks seamlessly. 

I consider IAM service to be the heart of AWS, as every solution architect needs to know about it. We efficiently use AWS to create multiple user privileges and permissions, making it very scalable and supportive of our clients' operations.

There are new AI features coming to AWS that are easy and simple to use. However, focusing on further allowing customization and flexibility in developing solutions as a solution architect or developer would enhance user experience.

I have been working with AWS IAM Identity Center for one and a half years.

I haven't faced any issues with AWS in the one and a half years I have been using it. It's very stable and reliable.

AWS IAM Identity Center has very high scalability and efficiency, which impacts our clients positively by providing them smooth solutions and seamless product management.

AWS customer support is quick, fast, responsive, and cooperative.

Neutral

The initial setup is easy to execute. If you read AWS documentation and newsletters, setting up IAM Identity Center is straightforward.

AWS provides the lowest pricing among other service providers like Azure, Google, Oracle. It is cost-effective, and they use a pay-as-you-go model.

I highly recommend AWS IAM Identity Center to new users, especially for storage and deployment services like EC2, which are cost-efficient and scalable. I encourage evaluating solutions based on specific requirements like storage, scalability, and balancing. 

The overall product rating is ten out of ten.

I usually use IAM Identity Center with EC2, where EC2 is the part where I configure the computation or making instances and servers that I need. IAM is generally used for the security part, where I configure the user and security groups that can access and configure the EC2 networks.

IAM Identity Center has made managing the budgeting aspects of AWS much easier. It provides a dashboard where the billing is all there, and we can predict and have a threshold for the budget, which makes the budgeting part really easy to manage and note.

The most valuable feature is the security configuration ease, which is great for me, especially as a beginner. It makes it easy to learn and understand how IAM works and to configure the security part for AWS services.

I would like to see more flexibility in the features as sometimes it doesn't meet my expectations. I want to be able to manage a lot of users easily. Having a lot of users on one instance is hard to configure, so I hope for more flexibility and ease in configuration.

I have been using IAM Identity Center for about two months.

Stability-wise, it is functioning well without any outages or crashes. I would rate it as a ten for stability.

Scalability is really beneficial. It can handle both a small number of users and a bigger number of users efficiently.

I have not interacted with technical support from AWS for IAM Identity Center yet.

Positive

I have not used a different solution for these use cases before. IAM is usually the most used for security with AWS services, and I haven't evaluated other solutions.

I would rate the initial setup a seven, as there are repetitive tasks that need to be done if there are a lot of accounts to set up. It would be beneficial to have automation or a technique to configure multiple users at once.

For deployment, I worked alone. Currently, I handle it by myself, even for maintenance, as I am not using the solution for a large project.

I've never made a comparison with on-premises servers, but IAM makes budgeting easy with tracking and managing costs. It's not easy to do so without a direct organizational comparison, but IAM provides insightful budgeting facilities.

I don't really focus on pricing much since the month budget is not high, and it is quite worthwhile for the price IAM offers. I consider it affordable.

I haven't really evaluated any other options. Based on the other AWS products available, IAM is the most suited for these use cases.

Overall, IAM Identity Center is a great service, currently rated at nine out of ten. There is room for improvement, especially in making it more user-friendly for newcomers or those new to AWS services.

I'd rate the solution nine out of ten.