AWS Identity & Access Management vs One Identity Identity Manager

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.

Well-suited: Companies with .NET or windows technology as a core. Companies with AD as main Directory Services Less appropriate: Companies with lot UNIX boxes Companies looking to support applications with many different connectors.

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

• Audit Trace History: Out of the box enables important field to trace and give you flexibility to expand them thru configuration settings.
• Provisioning to Active Directory: Synchronization Editor gives you flexibility to define what and when needs to be on sync.
• Web Portal: Latest version is more user friendly and support mobile devices.

• 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

• Web Designer: Hard to implement a new form from scratch.
• Rest API: Make more methods available.
• Connector: More connectors required like SNOW, Workday,etc.

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

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.

Selected due windows base technology, easy to deploy and AD connector.

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

• Positive impact because we now disable users immediately from the authoritative source.
• Positive impact due our integration with EPIC.