AWS Identity & Access Management vs. Forefront Identity Manager (Discontinued)

AWS Identity & Access Management is well suited to managing AWS application access between services. Very helpful for both third-party products and in-house developed software. Very happy with how easy it is to create access keys and then share them in our environment. AWS IAM can also be used to manage individual users, but I highly recommend using AWS SSO for that purpose instead. Much easier to deploy for console access and from a security side easier to turn off in one click from your SSO provider.

Incentivized

I think that MIM is great for compliance since it reduces the number of logins that are required by users. Most offices have post-it notes with logins floating around because there are so many to remember or there are "shared" logins. This reduces the number of logins to 1 and you can easily revoke access in one fell swoop. This prevents gaps and holes with terminations and updates to select groups are super simple.

Incentivized

• Customized access per key to limit scope
• Safely distributes access keys
• Provides access audits

Incentivized

• Authentication
• Security
• Identity Management

Incentivized

• Better integration with roles and policies so you don't need three windows open to create a new IAM user
• Display recommended configurations based on services being used
• Easier options to base config on existing users

Incentivized

• For Windows Server 2008 R2 Servers is a great tool to set a codeless provisioning over new objects.
• Can easily integrate with Active Directory and Exchange Servers, improving the identity sync between the final user and the lifecycle management.
• Improvements in the areas of performance, simplified deployment easing the troubleshooting tasks, better documentation knowledge base, and more language support.
• The codeless provisioning provided in FIM can sustain a variety from high demand to mid-size scenarios for account lifecycle management.

Incentivized

We would be unable to manage the interconnected nature of our AWS services without AWS IAM.

Incentivized

While we do not use Microsoft Azure for our servers and other customer-facing services. If we did, we would have to use Microsoft Azure Active Directory to manage access to services appropriately. It's difficult to quantify the differences between the services as they are truly different. I would recommend choosing AWS or Azure, then using the identity management provided by the same vendor.

Incentivized

It is Microsoft. We are a Microsoft shop, primarily. It integrates deeply with Active Directory making it good for Microsoft Active Directory shops.

Incentivized

• Without IAM, it would be difficult to use AWS across services. Increased ROI

Incentivized

• We see a positive impact simply in the time savings alone. Chasing accounts around is time-consuming and prone to error.
• The cost to us is negligible to the value it provides.

Incentivized