# AWS IAM Identity Center (AWS Single Sign-On)

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-iam-identity-center-(aws-single-sign-on)

> AWS IAM Identity Center (formerly AWS Single Sign-On) is a cloud service that enables secure and unified authentication for users to access AWS accounts and business applications with a single set of credentials.

Practice exams covering AWS IAM Identity Center (AWS Single Sign-On): [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [AIP-C01 AWS Certified Generative AI Developer - Professional](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## Free AWS IAM Identity Center (AWS Single Sign-On) tools

- [AWS Credentials Chain Troubleshooter](https://blowstack.com/tools/aws-credentials-chain-troubleshooter): Check SSO profiles and sso-session sections in your ~/.aws/config for the AWS CLI and SDKs.

## 9 key features of AWS IAM Identity Center (AWS Single Sign-On)

AWS IAM Identity Center (AWS Single Sign-On) simplifies access management across AWS accounts and third-party applications by offering single sign-on capabilities, centralized user management, integration with corporate directories, customizable access policies, support for MFA, and pre-integrated applications.

1. **Single Sign-On to AWS Accounts and Business Applications**: AWS IAM Identity Center (AWS SSO) enables users to easily access multiple AWS accounts and business applications with a single set of credentials, streamlining the login process and improving user productivity.
2. **Centralized User Management**: Administrators can manage user access centrally, including creating users, assigning them to AWS accounts and groups, setting permissions, and enabling or disabling access, all from a single location.
3. **Pre-integrated Applications**: IAM Identity Center comes pre-integrated with commonly used business applications; the IAM Identity Center console provides the comprehensive list.
4. **Customizable Access and Authentication Policies**: Organizations can define granular access and authentication policies based on user roles, ensuring secure and appropriate access to resources across AWS and third-party applications.
5. **Multi-factor Authentication (MFA)**: AWS IAM Identity Center supports multi-factor authentication, reinforcing security by requiring users to provide multiple forms of verification before gaining access.
6. **Integration with Corporate Directories**: It seamlessly integrates with existing corporate directories like Microsoft Active Directory, allowing users to sign in using their corporate credentials, which simplifies the user experience and enhances security.
7. **Trusted Identity Propagation**: Trusted identity propagation lets AWS managed applications securely share a user's identity with other AWS managed applications and authorize resource access based on that identity. CloudTrail events record the user and the actions they initiated.
8. **Permission Sets**: Permission sets centrally define permissions for common job functions, provision them across AWS accounts, and assign them to users and groups.
9. **IAM Account Access Manager**: Teams can create IAM roles in AWS accounts and centrally manage assignments of those roles to IAM Identity Center users and groups through IAM account access manager.

## Where AWS IAM Identity Center (AWS Single Sign-On) is used

AWS IAM Identity Center (AWS Single Sign-On) enables centralized access control, streamlined user sign-on across AWS accounts and applications, seamless cross-account access management, Multi-Factor Authentication (MFA) enforcement, and enhances compliance and audit readiness through detailed access reporting.

1. **Centralized Access Control**: AWS IAM Identity Center allows organizations to centralize access control for AWS accounts and cloud applications, enabling administrators to manage user permissions across all AWS accounts from a single location. This streamlines the process of granting or revoking access, ensuring that only authorized users can access sensitive resources.
2. **Streamlined User Sign-On**: With AWS IAM Identity Center (AWS Single Sign-On), users can sign in once to access multiple AWS accounts and applications without the need to remember multiple passwords. This simplifies the user experience, increases security by reducing the likelihood of password reuse, and lowers the risk of credential phishing attacks.
3. **Cross-Account Access Management**: Organizations can use AWS IAM Identity Center to manage cross-account access seamlessly. Users or groups can be given permissions to access resources in other AWS accounts without having to create and manage individual IAM users in each account. This is particularly useful for large enterprises with multiple AWS accounts.
4. **Multi-Factor Authentication (MFA) Enforcement**: AWS IAM Identity Center supports multi-factor authentication, allowing organizations to enforce MFA at the login for added security. This helps in safeguarding access and ensures that sensitive data and applications are only accessible by users who are authenticated through multiple verification methods.
5. **Compliance and Audit Readiness**: Utilizing AWS IAM Identity Center aids in compliance and audit readiness by providing detailed access reports and activity logs. Organizations can easily monitor who has access to what resources and review historical access, making it easier to comply with regulatory requirements and conduct audits.

## How AWS IAM Identity Center (AWS Single Sign-On) is priced

AWS IAM Identity Center uses a monthly active user-based pricing model, with no charges for idle users and no additional costs for federated access, promoting a cost-efficient solution for varying business sizes.

- **No Additional Charge**: AWS IAM Identity Center is offered at no extra charge.

## Services AWS IAM Identity Center (AWS Single Sign-On) works with

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Provides secure, single sign-on access to Amazon EC2 instances using IAM roles.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Allows users to manage permissions and access to AWS S3 buckets and objects.
- **[AWS Management Console](https://blowstack.com/tools/cloud-services-hub/aws-management-console)**: Enables single sign-on access to the AWS Management Console, allowing users to manage AWS resources.
- **[Amazon RDS](https://blowstack.com/tools/cloud-services-hub/amazon-rds)**: Provides secure access to Amazon RDS databases via IAM roles.
- **[Amazon Redshift](https://blowstack.com/tools/cloud-services-hub/amazon-redshift)**: Enables single sign-on access to Amazon Redshift clusters and data warehouses.
- **[AWS Lambda](https://blowstack.com/tools/cloud-services-hub/aws-lambda)**: Allows users to manage and deploy AWS Lambda functions securely via IAM roles.
- **[Amazon DynamoDB](https://blowstack.com/tools/cloud-services-hub/amazon-dynamodb)**: Enables secure access management to Amazon DynamoDB tables and items.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: Allows users to manage AWS CloudFormation stacks and resources securely.
- **[AWS CodeCommit](https://blowstack.com/tools/cloud-services-hub/aws-codecommit)**: Provides single sign-on access to AWS CodeCommit repositories and version control.
- **[Amazon QuickSight](https://blowstack.com/tools/cloud-services-hub/amazon-quicksight)**: Enables single sign-on access to Amazon QuickSight for business intelligence and data analytics.
- **[AWS Glue](https://blowstack.com/tools/cloud-services-hub/aws-glue)**: Integrates with AWS Glue for secure access to ETL jobs and data cataloging.
- **[Amazon SageMaker](https://blowstack.com/tools/cloud-services-hub/amazon-sagemaker)**: Allows secure access to Amazon SageMaker for machine learning model training and deployment.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: Provides single sign-on access and secure management of AWS Systems Manager resources.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: IAM Identity Center enables Athena workgroups to use trusted identity propagation so queries run with the workforce user's identity. Lake Formation can use that identity and its group memberships to enforce access to the queried data.
- **[Amazon CodeWhisperer](https://blowstack.com/tools/cloud-services-hub/amazon-codewhisperer)**: IAM Identity Center authenticates workforce users of CodeWhisperer Professional and lets administrators assign access to users and groups. These capabilities continue through Amazon Q Developer, which incorporates CodeWhisperer.
- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: IAM Identity Center can act as a SAML identity provider for an Amazon Cognito user pool. Employees can then sign in to applications backed by that user pool using their workforce identities.
- **[Amazon Connect](https://blowstack.com/tools/cloud-services-hub/amazon-connect)**: IAM Identity Center can provide SAML-based single sign-on to an Amazon Connect instance. Assigned employees can open Connect without maintaining a separate Connect password.
- **[Amazon DataZone](https://blowstack.com/tools/cloud-services-hub/amazon-datazone)**: IAM Identity Center provides workforce authentication for the Amazon DataZone data portal. DataZone uses its users and groups to manage portal access and participation in projects.
- **[Amazon EMR](https://blowstack.com/tools/cloud-services-hub/amazon-emr)**: IAM Identity Center integrates with EMR through trusted identity propagation, allowing supported analytics workloads to retain the identity of the user submitting them. EMR can pass that identity to Lake Formation to enforce user- and group-based data permissions.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: IAM Identity Center API activity recorded by CloudTrail can be matched by EventBridge rules. For example, a rule can trigger a notification or remediation workflow when an account assignment or permission set is changed.
- **[Amazon Managed Grafana](https://blowstack.com/tools/cloud-services-hub/amazon-managed-grafana)**: IAM Identity Center provides single sign-on to Amazon Managed Grafana workspaces. Administrators assign users and groups to workspaces and give them Grafana administrator, editor, or viewer access.
- **[Amazon Monitron](https://blowstack.com/tools/cloud-services-hub/amazon-monitron)**: IAM Identity Center manages workforce identities used to access Amazon Monitron projects. Administrators assign users to projects so they can inspect equipment health and sensor findings in the Monitron applications.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: IAM Identity Center provides workforce authentication for Amazon OpenSearch Service's OpenSearch UI. Assigned users can access connected data sources through a centralized sign-in experience.
- **[Amazon Q](https://blowstack.com/tools/cloud-services-hub/amazon-q)**: IAM Identity Center manages workforce access to Amazon Q offerings, including organizational access to Amazon Q Developer. It supplies user identities for subscriptions and personalized experiences across supported Amazon Q interfaces.
- **[Amazon Q Business](https://blowstack.com/tools/cloud-services-hub/amazon-q-business)**: IAM Identity Center authenticates Amazon Q Business users and supplies user and group identities for application access. Q Business can use those identities when enforcing document access controls so responses respect the user's permissions.
- **[Amazon WorkSpaces](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces)**: IAM Identity Center can provide SAML-based authentication for supported Amazon WorkSpaces configurations. Employees use their workforce sign-in to access their assigned desktops.
- **[Amazon WorkSpaces Applications](https://blowstack.com/tools/cloud-services-hub/amazon-appstream-2)**: IAM Identity Center can provide SAML-based single sign-on to Amazon WorkSpaces Applications. Application assignments and SAML attributes determine which streaming resources employees can launch.
- **[Amazon WorkSpaces Secure Browser](https://blowstack.com/tools/cloud-services-hub/amazon-workspaces-web)**: IAM Identity Center can serve as the SAML identity provider for a WorkSpaces Secure Browser web portal. Assigned employees authenticate with their workforce identities before starting a secure browsing session.
- **[AWS Client VPN](https://blowstack.com/tools/cloud-services-hub/aws-client-vpn)**: IAM Identity Center can provide SAML-based federated authentication for AWS Client VPN endpoints. Group information in SAML assertions can also support authorization rules that control which networks employees can reach.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: IAM Identity Center integrates with CloudTrail to record administrative API activity and supported authentication events. These records help audit changes to permission sets, account assignments, applications, and workforce access.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: IAM Identity Center integrates with AWS Control Tower to provide centralized workforce access to landing-zone accounts. Control Tower can configure Identity Center access using predefined groups and permission sets for common administrative and audit responsibilities.
- **[AWS DevOps Agent](https://blowstack.com/tools/cloud-services-hub/aws-devops-agent)**: IAM Identity Center provides workforce authentication for the AWS DevOps Agent web application. Administrators can assign users and groups access to agent spaces where they investigate operational incidents.
- **[AWS Directory Service](https://blowstack.com/tools/cloud-services-hub/aws-directory-service)**: IAM Identity Center can use AWS Managed Microsoft AD as its identity source, including supported configurations that connect to an existing Active Directory through a trust. Directory users and groups can then receive access to AWS accounts and applications using their existing credentials.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: IAM Identity Center provisions IAM roles in assigned AWS accounts from permission sets and maintains the policies attached to those roles. Workforce users assume these roles to receive the permissions defined for their account assignments.
- **[AWS IoT Device Management](https://blowstack.com/tools/cloud-services-hub/aws-iot-device-management)**: IAM Identity Center supplies workforce authentication for Fleet Hub for AWS IoT Device Management. Assigned users can sign in to Fleet Hub applications to monitor device fleets without needing individual IAM users.
- **[AWS IoT SiteWise](https://blowstack.com/tools/cloud-services-hub/aws-iot-sitewise)**: IAM Identity Center provides workforce authentication for AWS IoT SiteWise Monitor portals. Portal administrators can assign users and groups access to projects containing industrial asset dashboards.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: IAM Identity Center uses AWS KMS to protect stored data and supports customer-managed keys for supported instance configurations. Key policies must permit Identity Center and relevant integrated applications to perform the required cryptographic operations.
- **[AWS Lake Formation](https://blowstack.com/tools/cloud-services-hub/aws-lake-formation)**: IAM Identity Center supplies workforce user and group identities that Lake Formation can use as principals in data permissions. With trusted identity propagation, supported query engines retain those identities so Lake Formation can enforce access to governed tables and columns.
- **[AWS Organizations](https://blowstack.com/tools/cloud-services-hub/aws-organizations)**: IAM Identity Center integrates with AWS Organizations to centrally assign workforce access across member accounts. An organization instance supports organization-wide application access and delegated administration from a member account.
- **[AWS PrivateLink](https://blowstack.com/tools/cloud-services-hub/aws-privatelink)**: IAM Identity Center supports private access to supported service API endpoints through AWS PrivateLink interface endpoints. This lets workloads call those endpoints from a VPC without routing requests over the public internet.
- **[AWS Security Agent](https://blowstack.com/tools/cloud-services-hub/aws-security-agent)**: IAM Identity Center provides workforce authentication for the AWS Security Agent web application. Administrators assign users and groups access to agent spaces for security reviews and testing.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: IAM Identity Center provides temporary AWS credentials for the IAM roles associated with a user's account assignments. AWS STS supplies the temporary role-session credentials used to access AWS resources without long-lived access keys.
- **[AWS Transfer Family](https://blowstack.com/tools/cloud-services-hub/aws-transfer-family)**: IAM Identity Center authenticates users of AWS Transfer Family web apps. Administrators assign workforce users and groups to a web app, where they can transfer files to and from authorized Amazon S3 locations.
- **[AWS Verified Access](https://blowstack.com/tools/cloud-services-hub/aws-verified-access)**: IAM Identity Center can serve as the user identity trust provider for AWS Verified Access. Verified Access evaluates workforce identity information alongside its access policies before allowing a user to reach a protected application.
- **[Kiro](https://blowstack.com/tools/cloud-services-hub/kiro)**: IAM Identity Center provides organizational sign-in and workforce access management for Kiro. Administrators assign users or groups access so employees can use Kiro with their enterprise identities.

## AWS IAM Identity Center (AWS Single Sign-On) exam questions

Real practice exam questions on AWS IAM Identity Center (AWS Single Sign-On), with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company uses AWS IAM Identity Center with an external identity provider for employee sign-in. Employees access their assigned AWS accounts through the AWS access portal. The company now requires employees to use their corporate password and a registered security key before entering the portal. The company must retain its existing identity provider. Which change meets this requirement?

**Correct answer:** Configure the external identity provider to require multi-factor authentication using the password and registered security key.

**Explanation:** When IAM Identity Center uses an external identity provider, that provider authenticates employees and must enforce MFA. Requiring a password and a registered security key combines knowledge and possession factors.

### Question 2 (SOA-C03)

**Question:**

A company uses an organization instance of AWS IAM Identity Center in its AWS Organizations management account. The instance manages workforce access to 35 member accounts. A dedicated security member account hosts the company's security operations team.

The company wants security operators to manage permission sets and workforce assignments for member accounts while signed in to the security account. Operators must not assume roles in the management account. The company must retain the existing Identity Center instance, identity source, and account assignments.

Which solution meets these requirements?

**Correct answer:** From the management account, register the security account as the delegated administrator for IAM Identity Center. Grant security operators the required IAM Identity Center administrative permissions in the security account.

**Explanation:** Delegated administration allows authorized operators in a member account to manage permission sets and assignments for member accounts through the existing organization instance. Registration establishes the account's administrative authority, while IAM policies authorize the operators. The existing identity source and assignments remain in place.

### Question 3 (SAP-C03)

**Question:**

A financial services company uses AWS IAM Identity Center with an external SAML 2.0 identity provider (IdP) for access to its AWS organization. Employees start AWS access either from an AWS access portal bookmark or from an AWS application tile in the corporate IdP dashboard. The tile currently performs IdP-initiated SAML sign-in.

During testing, employees whose IAM Identity Center sessions have expired can establish new sessions without an authentication prompt because their corporate IdP sessions are still valid. Compliance requires fresh authentication at the corporate IdP whenever employees establish a new AWS access portal session through either supported entry point. Existing AWS sessions can retain their current lifetimes, and sign-in behavior for unrelated corporate applications must not change. The company can modify the AWS tile and the IdP's AWS-specific SAML configuration.

Which solution meets these requirements?

**Correct answer:** Enable user re-authentication in IAM Identity Center. Change the AWS tile to open the AWS access portal and configure the IdP's AWS integration to honor ForceAuthn in incoming SAML authentication requests.

**Explanation:** Enabling user re-authentication makes IAM Identity Center send ForceAuthn="true" in its SAML AuthnRequest. The IdP must honor this flag to prompt the user. Making the tile link to the AWS access portal ensures that both supported entry points use the SP-initiated flow to which this option applies, without changing unrelated applications' sign-in behavior.

### Question 4 (DEA-C01)

**Question:**

A company creates an Amazon SageMaker Unified Studio domain for a confidential analytics initiative. The domain uses AWS IAM Identity Center and requires explicit assignment before users can access its application. A synchronized workforce group is already a contributor member of a project in the domain's Research domain unit. Members can authenticate with their corporate credentials, but they receive an application access error before entering the domain. An administrator confirms that the group has not been assigned access to the domain's application.

Only this group should gain access, and its members must not receive additional project permissions or governance responsibilities. Which solution meets these requirements?

**Correct answer:** Use the domain's user management configuration to assign the existing IAM Identity Center group access to the domain's application, retaining its current project membership.

**Explanation:** Application assignment permits the group to access the domain through IAM Identity Center. The existing contributor membership separately controls collaboration in the project, so no additional project permissions or governance responsibilities are needed.

### Question 5 (SAA-C03)

**Question:**

A company uses AWS IAM Identity Center with an external SAML 2.0 identity provider (IdP) that authenticates employees against the corporate directory. Directory groups are provisioned into AWS, and employees receive account access through permission set assignments. Employees currently sign in with only their corporate passwords.

The company must require MFA whenever employees establish a new workforce sign-in session for AWS access. The corporate IdP must remain responsible for authentication, and existing group assignments and role-based access must remain unchanged.

Which solution meets these requirements?

**Correct answer:** Configure the corporate IdP's access policy for the AWS federation application to require MFA before issuing a SAML assertion for each new workforce sign-in session.

**Explanation:** The external IdP authenticates employees in this federation design, so it must enforce MFA before issuing the sign-in assertion. IAM Identity Center can continue using the existing provisioned groups, account assignments, and permission sets to provide role-based access without changing the identity source.

### Question 6 (SCS-C03)

**Question:**

A company uses AWS IAM Identity Center with an external identity provider to give engineers access to a shared development AWS account. The company has 12 projects. Each engineer can belong to several projects, and directory-managed groups record the approved membership for each project.

Engineers must use the AWS access portal to select a project-specific access profile. Credentials obtained through that profile must allow secretsmanager:GetSecretValue only for secrets tagged with that project's Project value, even when the engineer belongs to other projects. A provisioning service controls secret tags. Engineers cannot modify tags, identity attributes, or IAM policies.

The company prohibits a credential broker, additional role-assumption steps, individual user assignments, and user-specific policies. The solution must use native Identity Center account assignments and must support every approved project membership. No other policies grant or restrict secret access.

Which authorization design meets these requirements?

**Correct answer:** Create one permission set for each project. In each permission set, allow secretsmanager:GetSecretValue on the account's secret ARNs only when aws:ResourceTag/Project equals that project's fixed identifier. Assign each directory-managed project group to its corresponding permission set in the development account.

**Explanation:** Each project permission set provisions a distinct access role that engineers can select through the access portal. Group assignments determine which project profiles each engineer can use, while the selected role's resource-tag condition restricts that session to one project's secrets. This combines group-based role assignments with resource-attribute conditions without requiring per-user policies or multivalued session attributes.

### Question 7 (DOP-C02)

**Question:**

A company uses an organization instance of AWS IAM Identity Center with a corporate identity provider (IdP) to provide engineers access to 100 AWS accounts. An engineering group is assigned a ReleaseOperator permission set in each account.

Engineers sign in through the AWS CLI and export temporary credentials for release tools that cannot refresh credentials during execution. Releases can take almost 4 hours. The exported credentials currently expire after 1 hour, even though the AWS access portal session lasts 8 hours and the generated IAM roles have a maximum session duration of 12 hours. The tools use the exported credentials directly and do not assume additional roles.

A security policy requires newly issued release credentials to have a 4-hour lifetime. A DevOps engineer must implement this centrally without changing group assignments or maintaining the generated IAM roles individually. The engineer uses the IAM Identity Center administrative APIs rather than the console.

Which solution meets these requirements?

**Correct answer:** Set the ReleaseOperator permission set's SessionDuration to PT4H by using UpdatePermissionSet. Call ProvisionPermissionSet with ALL_PROVISIONED_ACCOUNTS and wait for successful provisioning. Have engineers obtain and export new role credentials before starting releases.

**Explanation:** The permission set's session duration controls the lifetime of AWS account role credentials issued through IAM Identity Center. When changing a permission set through the API, the updated configuration must be provisioned to the accounts where it is used. Newly obtained credentials then use the 4-hour duration; credentials issued before the change are not extended.

## Practice AWS IAM Identity Center (AWS Single Sign-On) in a full exam

Questions on AWS IAM Identity Center (AWS Single Sign-On) in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 21 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 12 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 11 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 8 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 6 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 6 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 2 questions
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 1 question

## What is AWS IAM Identity Center (AWS Single Sign-On)

AWS IAM Identity Center, formerly known as AWS Single Sign-On (SSO), is a cloud-based service offered by Amazon Web Services (AWS) that simplifies the process of managing access to AWS accounts and business applications. With the ever-increasing complexity and demand for robust security measures in today's technological landscape, organizations are seeking solutions that not only enhance security but also improve the efficiency of access management across diverse resources. AWS IAM Identity Center serves this need by enabling users to access AWS accounts, business applications, and third-party services such as Office 365, Salesforce, and Google Workspace with a single set of credentials. This significantly reduces the hassle of managing multiple usernames and passwords, thus streamlining the user experience.

The service integrates seamlessly with existing identity systems including Microsoft Active Directory, enabling organizations to leverage their current investments in identity solutions and facilitating a smooth transition to the cloud. Users can sign in through a centralized sign-on portal using their existing corporate credentials, making the process intuitive and straightforward. This integration is crucial for maintaining a consistent security posture and enforcing access policies across an organizations' IT environment.

One of the key benefits of AWS IAM Identity Center is its ability to offer granular control over user access to AWS resources and applications. Administrators can define precise access policies, ensuring that users have access only to the resources necessary for their roles. This principle of least privilege is fundamental to maintaining a strong security stance, minimizing the risk of unauthorized access or data breaches.

IAM Identity Center grants users short-term credentials to access AWS resources.

Moreover, AWS IAM Identity Center simplifies the process of managing access for users across multiple AWS accounts. Organizations that operate multiple AWS accounts can centralize user access management in AWS IAM Identity Center, allowing users to access all their accounts through a single portal. This not only enhances user convenience but also improves visibility and control for administrators, facilitating easier auditing and compliance with regulatory requirements.

The default quota is 3,500 permission sets in IAM Identity Center per supported Region; this quota is adjustable.

The default quota per AWS account is 500 permission sets in each supported Region; this quota is adjustable.

IAM Identity Center supports multi-Region deployment by replicating an instance from its primary AWS Region to additional Regions. This enhances the resilience of AWS account access and allows AWS applications to be deployed in Regions aligned with application data residency and proximity requirements.

The default quota is six enabled Regions, including the primary Region; this quota is adjustable.

IAM Identity Center offers organization instances for organization-wide access management and account instances for supported AWS applications in a single AWS account. Account instances do not manage access to AWS accounts.

AWS IAM Identity Center also supports multi-factor authentication (MFA), adding an extra layer of security by requiring users to provide a second form of authentication in addition to their username and password. This feature is crucial in protecting sensitive data and resources from unauthorized access due to compromised credentials.

In conclusion, AWS IAM Identity Center offers a comprehensive solution for managing access to AWS services and business applications, combining convenience and security. By enabling single sign-on, integrating with existing identity systems, providing granular access controls, and supporting multi-factor authentication, it addresses the critical needs of modern organizations in managing their security and compliance requirements efficiently.

## Learn AWS IAM Identity Center (AWS Single Sign-On) in lessons

21 short lessons on AWS IAM Identity Center (AWS Single Sign-On) in 8 certification courses.

- CLF-C02: Amazon Cognito vs AWS IAM Identity Center (Premium), https://app.blowstack.com/lessons/amazon-cognito-vs-aws-iam-identity-center-clf-c02
- SOA-C03: AWS IAM Identity Center: multi-account access with permission sets (Premium), https://app.blowstack.com/lessons/aws-iam-identity-center-multi-account-access-with-permission-sets-soa-c03
- SAP-C03: AWS IAM Identity Center: SAML federation and identity provisioning (Premium), https://app.blowstack.com/lessons/aws-iam-identity-center-saml-federation-and-identity-provisioning-sap-c03
- DEA-C01: AWS IAM Identity Center: workforce sign-in for SageMaker Unified Studio (Premium), https://app.blowstack.com/lessons/aws-iam-identity-center-workforce-sign-in-for-sagemaker-unified-studio-dea-c01
- AIP-C01: AWS IAM Identity Center: Federated workforce access through permission sets (Premium), https://app.blowstack.com/lessons/aws-iam-identity-center-federated-workforce-access-through-permission-sets-aip-c01
- SAA-C03: AWS Directory Service vs AWS IAM Identity Center (Premium), https://app.blowstack.com/lessons/aws-directory-service-vs-aws-iam-identity-center-saa-c03
