Arkinu
AWS service comparison

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

IAM
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

IAM

Service that securely controls access to AWS resources: who is authenticated (signed in) and what permissions they have to use each resource. With it, you create identities, such as users and roles, and grant them permissions through policies.

Exam phrases that point here

  • «avoid storing access keys on the EC2 instance»

    An IAM role attached to the instance (through an instance profile) delivers temporary credentials that renew themselves, so the application does not need keys stored in code or files.

    When not: If the one who needs access is someone at the company who signs in to several accounts, the clue points to IAM Identity Center. And if the secret belongs to another system (for example, a database password), think of AWS Secrets Manager.

  • «grant access to resources in another AWS account»

    The account that owns the resources creates a role with a trust policy that trusts the other account; users or roles in that other account assume it and get temporary credentials.

    When not: For some resources (S3 buckets, SQS queues, KMS keys), a resource-based policy is enough, with no role to assume. If the goal is to use the same network or infrastructure resource from several accounts (subnets, transit gateways), it is usually AWS RAM.

  • «principle of least privilege»

    IAM lets you limit each permission to specific actions, resources, and conditions, and offers tools (IAM Access Analyzer, last accessed information) to trim what is left over.

    When not: Least privilege is a principle that shows up across many services. If the scenario is about putting a permissions ceiling on entire accounts in an organization, the answer is AWS Organizations SCPs, which do not grant permissions by themselves.

  • «identify resources shared with entities outside the account»

    IAM Access Analyzer reviews policies and flags which resources are accessible from outside the account or organization, in addition to permissions that nobody uses.

    When not: If what you are looking for is who made a specific call and when, the clue points to AWS CloudTrail. If the ask is to evaluate resource configuration against rules over time, to AWS Config.

  • «grant permissions based on tags as resources grow»

    With ABAC, permissions depend on the role's or session's tags matching the resource's tags, so new resources are covered without rewriting policies.

    When not: If permissions depend on the job function and the environment is stable, the usual approach is RBAC with roles per function. ABAC depends on tags: a resource without the right tag is not covered.

Study IAM →

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 →