The usual use cases for Amazon Cognito that I have been working with mostly involve working for TLG Apps for three and a half years, where TLG Apps is a FinTech company in the UK. We were working for a few of the FinTech products, and inside that FinTech product, to make the authorization work, we handle how users will do the login, how to manage their identity, and how they can manage the logins and registration process. All those things are internally handled by Amazon Cognito. We use Amazon Cognito in multiple products inside TLG Apps. I do use Amazon Cognito's custom authentication workflows, and we have worked a lot on that custom authentication, specifically using the multi-authentication system. The custom authentication workflow's impact on my user management processes is significant, as I am working on a FinTech product that requires multi-level authentication. It does not just require a username and password, so in order to implement this, we had to include OTPs or one-time passwords sent to the user via mobile, email, and several other places as well. We can use an authenticator app as well, so we have multiple options available. We use this custom authentication flow to implement this feature specifically. I never use the UI components directly of Amazon Cognito; rather, I work under the hood. We will not directly use their UI components, but will use their API, as the frontend is not going to use any UI at all, basically. Since it's a product, we will do the branding ourselves, and all those things. Amazon Cognito is directly linked to our backend service, you can say, so it is not exposed directly to the frontend. The benefits I have experienced using Amazon Cognito's token-based authentication for OAuth 2.0, OpenID Connect, and SAML 2.0 protocols include my understanding that OAuth 2.0 is an open protocol widely used in all applications, and Amazon Cognito is the same as well. It has more compatibility in how we can implement it, as we have to do it in multiple places. If we need to build multiple applications based on a single Amazon Cognito instance, it is very good because we can create multiple apps on a single instance allowing one user to be shared across multiple applications, enabling single sign-on and so forth.
I used Amazon Cognito for access management for different applications, including websites and other web applications. Since we didn't need to create our own authentication methods for applications, we used it for our customers as an out-of-the-box solution. We only needed to integrate it with our application.
I use Amazon Cognito ( /products/amazon-cognito-reviews ) for single sign-on for our service. It is used to keep our customer credentials and authenticate the customer.
Cloud Software Engineer at a comms service provider with 51-200 employees
Real User
Top 5
Feb 1, 2025
The use case for Amazon Cognito is primarily for a single sign-on feature to manage user access. It is also associated with a project that involves education and entertainment.
We have used Cognito for our architecture model to handle user authentication and access control for our web and mobile applications. Additionally, we have incorporated Cognito not only for user authentication but also for social sign-in, SSO integration with our organization’s IDP, allowing us to onboard multiple customers with their own organization identity through SSO.
We use the solution for user management and authentication. Most of the time, when users are created on the core application, they are also created on Amazon Cognito. Then, we use policies to govern what resources they can and cannot access.
From an architectural perspective, we use Amazon Cognito for mobile application’s custom onboarding and SDKs to authenticate the users through the gateway.
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.
Distinguished Engineer & Senior Technical Architect at Pitney Bowes
Real User
Apr 29, 2022
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.
Amazon Cognito provides comprehensive user authentication and access control supporting OAuth 2.0, OpenID Connect, and SAML 2.0. Ideal for seamless integration and efficient user management tasks, enhancing security with features like password and group management.Amazon Cognito is an efficient tool for managing user authentication and implementing custom workflows. It offers features like token-based authentication and integrates seamlessly with AWS services. With capabilities in user...
The usual use cases for Amazon Cognito that I have been working with mostly involve working for TLG Apps for three and a half years, where TLG Apps is a FinTech company in the UK. We were working for a few of the FinTech products, and inside that FinTech product, to make the authorization work, we handle how users will do the login, how to manage their identity, and how they can manage the logins and registration process. All those things are internally handled by Amazon Cognito. We use Amazon Cognito in multiple products inside TLG Apps. I do use Amazon Cognito's custom authentication workflows, and we have worked a lot on that custom authentication, specifically using the multi-authentication system. The custom authentication workflow's impact on my user management processes is significant, as I am working on a FinTech product that requires multi-level authentication. It does not just require a username and password, so in order to implement this, we had to include OTPs or one-time passwords sent to the user via mobile, email, and several other places as well. We can use an authenticator app as well, so we have multiple options available. We use this custom authentication flow to implement this feature specifically. I never use the UI components directly of Amazon Cognito; rather, I work under the hood. We will not directly use their UI components, but will use their API, as the frontend is not going to use any UI at all, basically. Since it's a product, we will do the branding ourselves, and all those things. Amazon Cognito is directly linked to our backend service, you can say, so it is not exposed directly to the frontend. The benefits I have experienced using Amazon Cognito's token-based authentication for OAuth 2.0, OpenID Connect, and SAML 2.0 protocols include my understanding that OAuth 2.0 is an open protocol widely used in all applications, and Amazon Cognito is the same as well. It has more compatibility in how we can implement it, as we have to do it in multiple places. If we need to build multiple applications based on a single Amazon Cognito instance, it is very good because we can create multiple apps on a single instance allowing one user to be shared across multiple applications, enabling single sign-on and so forth.
I used Amazon Cognito for access management for different applications, including websites and other web applications. Since we didn't need to create our own authentication methods for applications, we used it for our customers as an out-of-the-box solution. We only needed to integrate it with our application.
I use Amazon Cognito ( /products/amazon-cognito-reviews ) for single sign-on for our service. It is used to keep our customer credentials and authenticate the customer.
The use case for Amazon Cognito is primarily for a single sign-on feature to manage user access. It is also associated with a project that involves education and entertainment.
We have used Cognito for our architecture model to handle user authentication and access control for our web and mobile applications. Additionally, we have incorporated Cognito not only for user authentication but also for social sign-in, SSO integration with our organization’s IDP, allowing us to onboard multiple customers with their own organization identity through SSO.
I use Amazon Cognito for managing user authentication and access control within my projects.
We use the solution for user management and authentication. Most of the time, when users are created on the core application, they are also created on Amazon Cognito. Then, we use policies to govern what resources they can and cannot access.
From an architectural perspective, we use Amazon Cognito for mobile application’s custom onboarding and SDKs to authenticate the users through the gateway.
I am using Amazon Cognito for single-tenant authentication.
We use Amazon Cognito for implementing SSO for Azure ready, Okta, or Oczero.
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.
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.