Easy ReviewDOP-C02
Configuration Management and IaC9

IAM Identity Center

Give workforce identities single sign-on access to AWS accounts and applications.

Identity sources, permission sets, and sessions

IAM Identity Center gives workforce users single sign-on access to assigned AWS accounts and applications. A single sign-on lets users sign in once and reach their assigned resources.

How it works

  1. Choose an identity sourceThe place where users and groups are managed. where users and groups are managed. The default is the Identity Center directory.
  2. With an external provider, Security Assertion Markup LanguageA standard for exchanging user information between an identity provider and a service provider. (SAML) handles sign-in. Provision users and groups before assigning access, either manually or automatically with System for Cross-domain Identity ManagementA protocol for synchronizing user and group information between identity systems. (SCIM).
  3. Assign a permission setA template of IAM policies used to assign access to AWS accounts., a template of IAM policies, to a user or group in each required account. Identity Center creates the account roles and updates them when the set changes. A permissions boundaryA managed policy that sets the maximum permissions an identity-based policy can grant to an IAM user or role. sets the maximum permissions an identity-based policy can grant a role.
  4. Users sign in to the access portal and choose an assigned account role or application. For attribute-based access controlAccess control that uses attributes such as department to determine access to resources. (ABAC), enable attributes for access control, select user attributes, and write a policy comparing session tagsAn attribute passed to an AWS session for use in access policies., attributes attached to a session, with resource tags.
Identity source Where identities are managed
Identity Center directory In Identity Center
Active Directory In an on-premises or AWS managed directory
External identity provider In the external provider

Exam cues

  • If the question says corporate users need access to many accounts, think permission sets and group assignments, because Identity Center creates roles in the assigned accounts.
  • If the question says synchronize users from an external provider, think SCIM, because SAML sign-in does not query the provider for users and groups.
  • If the question says department must match a resource tag, think attributes for access control and aws:PrincipalTag, because Identity Center passes selected attributes as session tags. Enable the feature and map the Department key to the populated ${path:enterprise.department} attribute from an external provider.
  • If the question says staff need a SAML business application, think application assignment, because no users are assigned by default.
  • If the question says multi-factor authentication (MFA) should prompt on changed sign-in context, think context-aware MFA, because a trusted device is checked against the sign-in context. With an external provider, configure MFA at that provider.

Remember

  • One identity source per organization. The Identity Center directory is the default.
  • Permission sets can use AWS managed, customer managed, or inline policies and a managed policy as a permissions boundary.
  • Account sessions default to one hour and can last up to 12 hours. Portal sessions default to eight hours and can last up to 90 days.
  • Always-on MFA is the default for users with a registered MFA device.

Trap: Signing out of the portal does not immediately end an existing account role session. It continues until its configured duration expires.

Sign in and access an account
12Workforce userIdentity CenterAccess portalAWS accountAssigned IAM role
  1. The user signs in to the access portal.

  2. Identity Center obtains a session for the assigned account role.

From the AWS docs (23)
  • An organization's identity source defines where users and groups are managed; one source can be an Identity Center directory, Active Directory, or an external identity provider.
  • The Identity Center directory is the default identity source unless another is selected.
  • An external identity provider uses SAML for authentication to the AWS access portal, and Identity Center grants access using its policies.
  • SCIM 2.0 automatically synchronizes user and group information from an external identity provider to Identity Center.
  • SAML cannot query an identity provider for users and groups; they must be provisioned before assignments.
  • A permission set is a template of IAM policies used to assign users or groups access to AWS accounts.
  • Assigning a permission set creates Identity Center controlled IAM roles in the accounts and attaches the specified policies; modifying the set updates the corresponding policies and roles.
  • Permission sets can contain AWS managed, customer managed, and inline policies, plus an AWS managed or customer managed permissions boundary.
  • A permissions boundary sets the maximum permissions an identity-based policy can grant to a role.
  • A user can have multiple permission sets and choose the least privileged role needed in the access portal.
  • The permission set session duration defaults to one hour and can be set to a maximum of 12 hours.
  • The access portal session defaults to eight hours and can be configured up to 90 days.
  • Existing IAM role sessions continue for their configured duration after the original sign-in session ends.
  • Identity Center assigns users or groups single sign-on access to configured applications; by default no users are assigned.
  • Identity Center provides single sign-on access to SAML 2.0 applications.
  • Identity Center can pass selected user attributes as session tags that IAM policies reference with aws:PrincipalTag to compare against resource tags.
  • Attributes for access control must be enabled to use attribute-based access control.
  • Identity Center maps an attribute key to a value from the identity source and passes it as a session tag; the key must match the key used in the policy.
  • The external identity provider attribute path ${path:enterprise.department} is supported for attributes for access control.
  • Identity Center supports always-on and context-aware MFA prompts; always-on is the default for users with a registered device.
  • Context-aware MFA prompts when the sign-in context changes after a user trusts a device.
  • An external identity provider manages MFA settings instead of Identity Center.
  • An organization instance of IAM Identity Center, enabled in the Organizations management account, supports all features and is recommended; an account instance is bound to one account and Region for simpler single-account application access.

Flashcards

tap to flip
Answer

·

All 9 cards as a list

How do IAM Identity Center permission sets grant access across AWS accounts?

A permission set is a policy template. Assigning it to a user or group creates an IAM role in each assigned account; changes to the set update the roles and policies.

A company wants employees to use an existing external identity provider to sign in to the AWS access portal. How does IAM Identity Center support this?

The external identity provider authenticates users through SAML. IAM Identity Center grants access using its policies.

A workforce needs console and CLI access across many AWS accounts using existing identities. What IAM Identity Center setup should be used?

Connect the identity source and assign permission sets to users or groups in the accounts. Identity Center creates the account roles.

An external identity provider signs users in to IAM Identity Center, but groups must synchronize automatically. Which protocols serve each purpose?

Use SAML for sign-in and SCIM to synchronize users and groups. SAML alone cannot query the provider for them.

A company wants IAM Identity Center access policies to match employees' departments to resource tags. What should it configure?

Enable attributes for access control, map Department to the populated department attribute, and use aws:PrincipalTag in a permission set policy to compare the session tag with the resource tag.

A company needs to assign consistent AWS account permissions to groups across multiple accounts. What does IAM Identity Center use?

Use permission sets. They define IAM policy templates, and assignments create IAM roles with those policies in the target accounts.

Who configures MFA when IAM Identity Center uses an external identity provider?

The external identity provider manages MFA.

A company wants IAM Identity Center users to access a SAML business application with single sign-on. What should an administrator do?

Configure the application and assign its users or groups. No users are assigned by default.

A company wants one place to give workforce users access to many AWS accounts. Which IAM Identity Center instance type fits?

An organization instance, enabled in the Organizations management account. Account instances cannot manage access to multiple AWS accounts.

You finished every topic of DOP-C02!

Your badge turned gold. Next step: book the exam on AWS. Once you pass, add yourself to Who passed.

Share

Share that you finished this certification

I finished every topic of AWS Certified DevOps Engineer - Professional (DOP-C02) on Easy Review. Come study too!