AWS Organizations vs. Fischer Identity as a Service

AWS Organizations is well suited for centralized billing and user management of all of your AWS accounts when paired with AWS SSO and a SAML provider of your choice. AWS Organizations does not have an integration with IAM user accounts and this could be helpful for organizations without SAML capability.

Incentivized

Fischer is well suited for the use case scenarios where an institution has not previously used any identity management and needs to quickly provide services to meet regulatory or other deadlines. It also works well when you can implement in smaller batches of user accounts and grow over time. We have found it less appropriate for cases where we have needed to set up on-off temporary or special access. Fischer has worked with us on out-of-band provisioning but we had to pay for extra Fischer professional services to make that work.

Incentivized

• Brings all AWS organizations under one management structure for billing
• Simplified management of user access with AWS SSO
• Centralized reporting

Incentivized

• Integration with ERP
• Integration with Account Directory
• Integration with Office 365
• Password Reset Portal

Incentivized

• Could include cross organization IAM management
• Could allow quick login access to other organizations like the AWS SSO homepage

Incentivized

• Reducing the frequency (twice a month) of scheduled outages. But I believe they are making progress toward developing a more robust cloud infrastructure that will eliminate the need for such frequent downtimes.
• There are some less than intuitive administration tools, which could be improved. Fisher is always willing to help us when we don't understand the proper way to configure using the tools.
• I would like a streamlined way to move changes from our test environment into our production (live) environment instead of having to duplicate the effort.

Incentivized

Not applicable. AWS Organizations is unique in managing multiple AWS accounts.

Incentivized

It does deliver as advertised, provided you do your homework and understand the expected outcome before going live. Poor planning can turn the project into a nightmare. It can save the company a good deal of man hours and money by bringing about identity management automation, a self-service portal, and customizable email notifications for all of the identity owners and other stakeholders. For example, you can inform your HR team upon successful account creation and disablement. You can proactively reach out to users informing them about their account extirpation status, etc.

Incentivized

• AWS Organizations allow for quick user access when paired with AWS SSO and SAML groups.
• AWS Organizations does not use IAM users and there is an initial cost in time to set up AWS SSO.

Incentivized

• Fischer has had a positive impact by providing self-serve identity and password management tools that our constituents can use at their convience, not tied to our operational hours.
• Fisher Identity as a Service has been a significant cost, but it is anticipated that it saves our students significant time and effort that they can better dedicate to their academic pursuits.
• Negative initial reaction--as this was a new way of doing things, there was a period of confusion among our college constituent that required additional communication and instruction

Incentivized