Amazon Cognito Reviews

I am using Amazon Cognito for single-tenant authentication. 

One of the key benefits of this software is its ease of integration with a wide range of applications, including mobile apps and web applications. This simplifies the process of integration, and it can be seamlessly incorporated with Azure, Kubernetes, and other software systems.

Amazon Cognito could improve by simplifying the configuration.

I have been using Amazon Cognito for approximately 6 months.

The solution is stable.

I rate the stability of Amazon Cognito a ten out of ten.

We have a couple of thousand of people using this solution.

Amazon Cognito is highly scalable.

I rate the scalability of Amazon Cognito a ten out of ten.

I did not contact the vendor for support.

The deployment is easy if it is configured correctly. The time of the deployment depends on the company using it and the options selected.

I did the implementation of the solution.

The price of the solution depends on the number of users using it.

The cost of the solution is reasonable with the pay-as-you-go model.

I rate the price of Amazon Cognito a five out of ten.

We chose this solution because of the pay-as-you-go pricing model.

The solution does not require maintenance.

I rate Amazon Cognito a nine out of ten.

Cognito is a user management solution that easily creates users and gives and assigns policies, access rights, permissions, and user groups. It's a user group and user management tool that is easily managed and integrated with our Lambda solutions. This product enables us to skip work on developing a user management module for creating user editing and deleting.

We all save in our project, which saves us time. It's an easily managed user management service with all the features of user management of policies and permissions groups.

The feature I liked most is the development of this product. The user management module that comes built-in to Cognito saves me time deleting and creating users. To launch the module, all I have to do is provide EVIs for creating and editing users and assigning privileges. The great thing about the module is that it is integrated with all other Amazon products. For example, when I'm using Lambda or EC2, I can direct the user who accessed these services to the Cognito user who also accesses these services. 

The solution is not hard to integrate. It provides me with a seamless integration to other AWS products. Cognito speeds up our development and saves us time. 

The user management module is also a major benefit of this product. It's easy to use and integrate and not hard to set up.

I believe this product could improve by enriching user profiles. I encountered this problem two years ago when it seemed like we needed to take care of our tracking permissions. 

We do sometimes run into issues with Cognito. For example, we have seen cases of the software not disabling certain users from certain permissions. When we looked deeper, we discovered that one particular user's permissions were reset following an update. My recommendation for preventing this from happening in the future is to enrich the module with tracking. This would also be better for statistical tracking, user action tracking, and user permission tracking. 

I have been using this solution for about three years.

I have not contacted their tech support.

Cognito gets configured once and it doesn't take very much time to set up. We have about 50 to 100 users currently using Cognito.

Based on my experience, I'd recommend this solution to anybody that needs only assembly user management. Also, if you need an easy product to handle your user management module in your solution, Cognito has a good use case.

Overall, I would rate Cognito as a solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.

We use Amazon Cognito when we need to write the last code and then we don't need to worry about user security and data.  Amazon Cognito handles all the security, such as OTP and email verification. It does not require a lot of code to do a lot of things. It only requires a click with the mouse, it is plug-and-play. Additionally, you can customize your design. The functionality you need is verifying emails, secure data passwords, and encrypted passwords. All of the user data is saved into the Cognito pool.

The secure authentication of Amazon Cognito has benefited our company. We were previously using legacy signup systems.

The most valuable features of Amazon Cognito are OTP validation and email validation.

Amazon Cognito can improve by having documentation verification.

I have used Amazon Cognito within one year.

When you integrate there can be some stability challenges. For example, if you use Amazon Cognito for the rest APIs you need to generate a token. 

I rate the stability of Amazon Cognito a seven out of ten.

There are many aspects of the solution that can improve.

Amazon Cognito is highly scalable.

I rate the scalability of Amazon Cognito a nine out of ten.

We did not use another solution prior to Amazon Cognito. We did coding manually.

When implementing Amazon Cognito it is always important to study the documentation.

You need to do some configuration in Amazon Cognito which will generate a form. You can customize the UI and it will generate a link so you can directly use it. Additionally, they provide a plug-and-play code that whenever you create a Cognito they guide you.

I rate the initial setup of Amazon Cognito an eight out of ten.

The price of Amazon Cognito is low. The pricing model is based on the users.

I rate the price of Amazon Cognito a five out of ten.

We use Amazon Cognito for implementing SSO for Azure ready, Okta, or Oczero.

Amazon Cognito has helped improve our organization by unifying a lot of cross-functional SSOs under one umbrella. It has helped us cover all the different use cases. Our customers are passing through an Amazon Cognito gateway rather than a different hybrid or isolated provider.

The most valuable features of Amazon Cognito are the pre and post-token generation, and the different Cognito triggers. It has lots of functionality and flexibility.

Cognito triggers can improve by providing more direct use cases rather than giving a white paper. A white paper is not at all interesting, it has too many details. It would be a benefit to provide a smaller document that is summarized. The smaller version would bring microdata, macro data is not helpful.

I have been using Amazon Cognito for approximately one year.

I rate the stability of Amazon Cognito a seven out of ten.

The scalability of Amazon Cognito is good.

We develop software for many customers and have many users who use this solution. There are approximately 5,000. We plan to increase our usage in the future.

I rate the scalability of Amazon Cognito a seven out of ten.

I have not used the support for Amazon Cognito. However, I heard they are good.

We have not used another solution prior to Amazon Cognito.

We use Terraform for the deployment and it takes approximately 15 to 30 minutes for a typical deployment.

There are a lot of different steps that need to be taken for the implementation, there are other dependencies. At the beginning levels, it takes anywhere from 15 to 30 minutes. In a more complex environment, it takes more than an hour to two hours if you try to have a one-nightly build and everything bypassing through automated test assets and the different syntax. If you have many different elements involved it takes longer than two hours.

I rate the initial setup of Amazon Cognito a seven out of ten.

We have two people that do the deployment of the solution.

The return on investment we have received has been good. The solution has saved us a lot of time.

The price of Amazon Cognito is expensive. We are on an annual subscription.

I rate the price of Amazon Cognito a two out of ten.

We evaluated Keycloak and we found Amazon Cognito was a better option in terms of changes.

We use one developer for the maintenance of the solution.

I rate Amazon Cognito a seven out of ten.

Our company has been using the solution to determine proof of concept for a project that is large-scale with over one million users. Through experimentation, we have found that some things work well and some things have issues.  

We have 300 engineers using the solution but have determined our project cannot go to production because there are unresolved issues with B2C multifactor authentication. 

The solution is proto-connective and integrates well with other AWS services. 

The solution can be useful for small-scale, machine-machine projects. It can provide one kind of language that is the same for all connection partners. 

The developer experience for mobile apps is terrible. Documentation is very poor and it is difficult to read the documents available to put things into practice. Our team has issues finding information related to using the solution. 

SDK and libraries available for mobile apps are terrible. For example, if you use MFA to migrate one user from your database to the pool, you need to use Lambda functions or other methods in AWS to get the solution enabled. 

It is extremely difficult to put a very, very scalable project into practice. Our team doesn't think you can use the solution for B2C on a large scale. We thought the solution would provide an agile experience but it does not. 

The solution needs to keep a history of passwords. For example, you should be able to check if customers used the same password in the past when connecting to a company by username and password. This type of feature is a must for our project. 

The MFA related to the solution's side is nonexistent. MFA should occur on the Facebook or Google side and also on the solution's side. This is a big problem because we have wallets, credit cards, and sensitive data stored for each customer. One layer of security is totally missing. 

I have been using the solution for three months. 

The solution does not seem stable because it performs and behaves differently for native and iOS apps. I cannot say the solution is stable for any one application. 

Scalability is not so good so it is difficult to scale to future users. The solution works for some custom development but the backend needs to be more scalable. It does not seem that the solution is scalable in terms of features from both the backend and production sides. 

Technical support is good so I rate it a five out of ten. 

Neutral

The setup is pretty easy but production is difficult. 

Our team implemented the solution in-house. We have many teams so once we implement, other teams can do orchestration because we have a DDG domain-driven approach. You can see a vertical deployment in production even if teams are working independently. 

Ongoing management is handled by five engineers. 

The pricing is not so bad, so I rate it a two out of ten. 

The solution works pretty well for some parts of our project but not well for parts related to our customer. For example, we need B2C to connect a mobile app experience but have a lot of problems with multifactor authentication so we cannot put the solution to production. 

You can use the solution for proof of concept or starting projects that do not have a lot of users. 

The solution will not work well for web apps or native applications that connect consumers in the end. It is not good for custom flows or the in-app experience. MFAs and social logins are not feasible with the solution. 

I rate the solution a five out of ten. 

We use this solution in integrate with different partners and financial services. It is a good solution but we need more training help us to discover and explore all of its features. 

We have 500 users making use of it. 

The cost of this solution is high when used by many people in an organization. In a future release, we would like to have different methods to validate the characteristic of a user. For example, we would like to use biometric data to analyze the behavior of users.

I have been using this solution for three months. 

This is a stable solution.

This is a scalable solution. If our app or general usage increases, this solution can support it. My main concern with this kind of scaling is that the cost increases significantly on a monthly basis. 

The initial setup is straightforward. It is easy review the documentation and complete the implementation. We needed three engineers for this setup.

We pay $600 monthly per user for licences and there are no other additional costs. 

My advice to others would be to review the business model and the cost, and understand the different products in the lifecycle of transactions end to end. This will assist in calculating the cost of the platform over time. It's very important to understand the business model, the different tools that can be used and to analyze the transactions end to end.

I would rate this solution an eight out of ten. The main reason for this rating is that I am not familiar with all of its components and features. 

We use AWS Cognito for authentication and authorization of our system. We use Cognito alongside Okta. Because of the high cost of Okta, we have a hybrid model of both solutions. 

The federation is one of the most efficient features as the pricing is competitive.

The ease and simplicity of integration could be improved when using this solution. When using Okta, scope is a single endpoint with a parameter as a scope. In the Cognito for each scope, there is a separate endpoint.

This is a stable solution.

This is a scalable solution. 

We are premium customers of AWS, so we get support in a very efficient way.

Positive

The initial setup is straightforward. 

The pricing of this solution is good compared to other solutions on the market. 

I would recommend Cognito for users who are already AWS customers. Cognito will provide inbuilt authentication on operation for those services and capabilities in a cost-efficient manner.

I would rate this solution an eight out of ten.