AWS Identity & Access Management vs. Tivoli Identity Manager (legacy)

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

It's probably really best suited if you have a business where you have disparate systems but need a way to synchronize the user account information including the passwords between them. If you just have a Windows Active Directory environment only, there probably is no real need for something like this, but if you do this will help manage them easily.

Incentivized

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

Incentivized

• Fully customizable
• Automate various portions of various applications
• Great at Access Management (but also Release, Change, Event, etc)

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

• Sometimes it feels unresponsive and we have to restart the services.

Incentivized

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

Incentivized

Besides the random issue where it gets unresponsive and we have to restart the services or reboot the server, it's been really solid. I've only had to contact support 1 time in the 15 years I've used it which is saying more than most other software. The cost of maintenance is also very cheap compared to some of the other software we use.

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

I haven't used anything but Tivoli in this space.

Incentivized

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

Incentivized

• Single sign on and web-threat protection
• Cutting down time to enter multiple usernames and passwords
• Cutting support call times across multi apps

Incentivized