AWS Identity & Access Management vs. Tools4ever UMRA

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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

It is very well suited for tying multiple systems and services together, allowing for exchanges of information and account management. I'm not sure of instances that it is not well suited since solution was recommended by folks in education. With that being the case it suited our needs quite well.

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

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• Imports students and staff into our Active Directory and email system.
• It manages those same accounts, disabling accounts for folks who have left, and creating "Windows" when accounts should be enabled.
• It interacts with our Microsoft AD and our student management software seamlessly. Once accounts are in our AD environment, our student management and other systems create new email accounts automatically for us.

• 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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• We have been attempting to get single sign on for students, so they have the ability to change their passwords on their own. The documentation of this process is very dated, and often support isn't even aware that their site issues/ references those older documents.
• During the initial buildup of our server Tools4ever UMRA support was a bit hit and miss, but I will say our ongoing support has been very good.
• Some integration tools had to be custom created.

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

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

• We save considerable work hours by a multitude of staff having the system manage and generate accounts for us on a daily basis.
• We have some peace of mind knowing accounts for staff and students who leave our district can no longer gain access to our systems because it automatically disables those accounts.
• Because of the way the system interacts with input that is put in, it automatically creates logical positions which dictate different levels, meaning it automatically sets up when staff gain access and lose access depending on the position they are filling.