Arkinu
AWS service comparison

Amazon Cognito vs AWS IAM Identity Center: differences and when to use each

Amazon Cognito
AWS IAM Identity Center

Often confused on the examQuestions tend to offer one as a distractor for the other: look for the phrase in the scenario that tips the balance.

Security, Identity, and Compliance

Amazon Cognito

On the radar· Amazon Cognito Sync no longer accepts new customers

Identity platform for web and mobile applications: user pools sign up and authenticate users (including through Google, Apple, or SAML and OIDC providers) and issue JWTs. Identity pools exchange those tokens for temporary AWS credentials to access services such as Amazon S3 or Amazon DynamoDB.

Exam phrases that point here

  • «user sign-up and sign-in for a web or mobile application»

    An Amazon Cognito user pool is a managed user directory: it handles sign-up, sign-in, email or phone verification, and MFA.

    When not: If the people signing in are employees accessing AWS accounts, the clue points to IAM Identity Center. Cognito is for an application's customers or end users.

  • «sign in with Google, Facebook, or Apple»

    Cognito supports social providers and SAML or OpenID Connect providers, so the application does not have to integrate each one on its own.

    When not: If sign-in with an IdP is for employees to access the AWS Management Console, the answer is IAM Identity Center or IAM federation, not Cognito.

  • «give mobile app users direct, temporary access to S3 or DynamoDB»

    An identity pool exchanges the user's identity (from a user pool, a social provider, or a guest) for temporary AWS credentials tied to an IAM role.

    When not: If the application only calls its own API and does not touch AWS services directly, the user pool token and an API Gateway authorizer are enough, with no identity pool.

  • «allow guest access without signing in»

    Identity pools can give credentials to unauthenticated users, with a different, more limited IAM role than the one for authenticated users.

    When not: Guest access is for using AWS resources from the app. If the goal is to serve public content, such as images or pages, Amazon S3 and Amazon CloudFront are usually enough.

  • «protect an API Gateway API so that only registered users can call it»

    API Gateway has a Cognito user pool authorizer: it checks the token the client sends and lets through only calls with a valid token.

    When not: If the caller is another AWS service or an application with IAM credentials, IAM authorization is used. If you need custom logic to validate a token from another provider, a Lambda authorizer is used.

Often paired with

  • Amazon API Gateway
  • Amazon DynamoDB
  • Amazon S3
Study Amazon Cognito →

Security, Identity, and Compliance

AWS IAM Identity Center

Service for giving an organization's users (workforce) centralized access to multiple AWS accounts and applications. You can connect your existing identity provider or create users in the service itself, and they sign in through a single access portal.

Exam phrases that point here

  • «single sign-on across multiple AWS accounts»

    IAM Identity Center gives employees a single sign-in and a portal from which they access all the AWS Organizations accounts assigned to them.

    When not: If the users are customers of a web or mobile application, not employees, the clue points to Amazon Cognito. If the access is by an application or a service, not a person, it is solved with IAM roles.

  • «use the existing corporate identities from the identity provider»

    Identity Center connects to an external SAML 2.0-compatible IdP (such as Okta or Microsoft Entra ID) or to Active Directory, and can sync users and groups with SCIM.

    When not: If the scenario is about Windows applications in a VPC that need an Active Directory domain (joining instances, Kerberos, LDAP), the clue points to AWS Directory Service, which can work alongside Identity Center.

  • «centrally manage employee access to all accounts in the organization»

    With permission sets you define once what a group can do and assign it to many accounts; Identity Center creates and maintains the roles in each one.

    When not: If the ask is to limit the most that any identity in a member account can do, including those that do not go through Identity Center, the answer is AWS Organizations SCPs.

  • «avoid creating IAM users in each account»

    Identity Center does not create IAM users: users live in its directory or in the external IdP and get temporary credentials when they sign in to each account.

    When not: For access between two specific accounts by an application or a service, with no people involved, a cross-account IAM role is usually enough.

  • «access SAML-compatible SaaS applications with the same identity»

    In addition to accounts, Identity Center offers single sign-on access to preintegrated business applications and to any application that supports SAML 2.0.

    When not: Applications that only support OpenID Connect cannot be connected this way, and single sign-on to business applications works in the browser, not in native mobile or desktop applications.

Often paired with

  • AWS Organizations
  • AWS Directory Service
Study AWS IAM Identity Center →