Amazon Cognito vs. Tivoli Identity Manager (legacy)

Well Suited

1. B2C mobile and web apps with a high number of users.
2. Cheaper and cost-effective.
3. If the other pieces of the infra are already using AWS services like Lambda, S3, Pinpoint, etc.

Not Suited For:

1. Advanced use-cases (Biometrics based authentication) Email, and other MFA channels.
2. For any use-cases needing SCIM.
3. Customized flows of SSO, and MFA will need a layer on Lambda and other AWS services.

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

• Strong integration with React.js and client-side applications
• Easy to bridge Cognito identities with the rest of the AWS ecosystem
• Easy to store user profile data directly in Cognito rather than having to build additional services/endpoints
• Easy integration with AWS Lambda to extend and add sophistication to the service

Incentivized

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

Incentivized

• SCIM implementation is not present.
• B2B SaaS use-cases are very hard to configure. More suitable or B2C use-cases.
• Needs more recipes, plugins, SDK's.
• 2FA with Email as an OTP channel is not supported.
• 2 FA using biometrics is not available; can be customised using lambda.

Incentivized

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

Incentivized

All the features AWS Cognito offers gives the user the options they need without making it too complicated. Your customers will be happy. On the administration site usability is also great. After a small learning curve, you can setup Cognito for your usage

Incentivized

AWS Support overall is poor. Your main resources are trainings and the docs, and the docs can be very confusing. Using Cognito well involves having a developer learn it deeply and help support your team in understanding it. That said, Cognito's competitors also have dismal support and even worse documentation, so while this isn't a strength for Cognito it may still be the frontrunner here.

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

They are ideal tools to create a secure and unique login experience for our applications. Thanks to its API authorization, Amazon Cognito ensures connections to applications that are secure.It is easy to use and provides easy access to files and applications that you need to complete your goal.

Incentivized

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

Incentivized

• Amazon Cognito has had a positive impact on our business by allowing us to develop services that require user sign-up and sign-in more rapidly. Not only do we not need to build or maintain these features, but Cognito's implementation is also better than what we would be justified in building ourselves.
• Amazon Cognito makes user management easy. This reduces the time we have to spend supporting users. Non-technical product managers can even use the AWS Console to manage users without requiring support from developers.
• Amazon Cognito is likely more secure than what would be built in-house; a portion of our attack surface is now managed by Amazon.

Incentivized

• It has helped us all these years to not have to waste time managing users on multiple systems.
• It controls our password policy for our domain.

Incentivized