# Identity Federation

Identity federation allows one security domain to accept identities authenticated by a trusted identity provider instead of maintaining separate credentials for them.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/identity-federation

> Federation separates where an identity is authenticated from where that identity accesses resources, using established trust and verifiable identity assertions or tokens. It enables centralized sign-in for employees, customers, and workloads while letting each application or cloud account retain control over authorization.

Practice exams covering Identity Federation: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [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), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-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).

## 6 key aspects of Identity Federation

Federation combines trusted identity evidence, centralized authentication, and destination-controlled permissions to provide access without duplicating long-lived credentials.

1. **Trust across identity domains**: A relying party accepts identity evidence only from configured, trusted providers. Validate signatures, issuer, audience, expiration, and relevant claims rather than accepting a token merely because it is well formed.
2. **Centralized authentication with local authorization**: The identity provider authenticates the caller, while each destination controls access to its resources. Map trusted identities or groups to narrowly scoped roles and application permissions.
3. **Temporary sessions and credentials**: Federated access commonly produces application sessions or short-lived cloud credentials instead of permanent access keys. Set session lifetimes according to operational needs and account for sessions that can outlive a user's disablement at the identity provider.
4. **Human and workload identities**: Employees and customers can federate through interactive sign-in, while workloads can use trusted tokens or certificates. Choose authentication methods that fit the caller rather than embedding a human password in automation.
5. **Explicit permission and trust boundaries**: Permission to assume a role and permission to use resources are separate decisions. Review role trust policies, role permissions, resource policies, and organization-level controls together when diagnosing access.
6. **Authentication assurance and lifecycle management**: Enforce appropriate MFA at the authenticating provider and verify how its assurance reaches downstream systems. Manage provisioning, deprovisioning, signing-key rotation, and session revocation separately from the sign-in protocol.

## Cloud services for Identity Federation

For workforce access, IAM Identity Center connects centralized identities to AWS account assignments and permission sets. IAM supplies the roles, trust policies, and permissions that define account access, while AWS STS issues temporary credentials for supported federation and role-assumption flows. Amazon Cognito addresses customer-facing application sign-in and, through identity pools, can provide temporary AWS access. IAM Roles Anywhere supports certificate-authenticated workloads outside AWS. Applications can use Amazon Verified Permissions to evaluate their own authorization rules after authentication. These services serve distinct purposes: establishing identity, creating a cloud session, and deciding which actions that session or application user may perform.

- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: User pools support application sign-in and federation with supported external identity providers. Identity pools can provide temporary AWS credentials for supported identities; user-pool tokens are not themselves AWS API credentials.
- **[Amazon Verified Permissions](https://blowstack.com/tools/cloud-services-hub/amazon-verified-permissions)**: Evaluates application authorization policies using Cedar after an identity has been established. Supported identity-source integrations can map token claims into authorization context, but the service does not replace authentication or grant IAM permissions for AWS resources.

## Identity Federation exam questions

Real practice exam questions on Identity Federation, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A photo-sharing mobile application already authenticates customers through an OpenID Connect identity provider. After signing in, customers need temporary, limited AWS credentials to upload photos directly to Amazon S3. The company does not want to create IAM users for customers or build its own credential broker. Which solution best meets these requirements?

**Correct answer:** Configure an Amazon Cognito identity pool to trust the existing identity provider and assign an IAM role with the required S3 permissions.

**Explanation:** Amazon Cognito identity pools can exchange tokens from a supported identity provider for temporary AWS credentials. An associated IAM role defines the S3 permissions available to authenticated customers.

### Question 2 (SOA-C03)

**Question:**

Operations engineers access a single AWS account through a corporate SAML 2.0 identity provider (IdP) and an IAM role. The IdP authenticates engineers successfully, but AWS STS AssumeRoleWithSAML requests begin failing with an assertion signature validation error immediately after the IdP rotates its signing certificate. The IAM SAML provider still contains the metadata imported before the rotation. The role's trust policy and operational permissions have not changed.

A CloudOps engineer must restore access while continuing to validate assertions signed with the IdP's current certificate. Which action should the engineer take?

**Correct answer:** Update the existing IAM SAML provider with current IdP metadata that includes the new signing certificate.

**Explanation:** AWS uses the signing certificates in the IAM SAML provider's metadata to validate assertions from the IdP. Updating that provider with trusted, current metadata restores validation without changing the provider ARN referenced by the role's trust policy.

### Question 3 (SAP-C03)

**Question:**

A company acquires a business and moves its AWS accounts into the company's existing AWS organization. The company uses an organization instance of AWS IAM Identity Center connected directly to its on-premises Microsoft Active Directory. The acquired business manages its employees in an external identity provider (IdP) that supports SAML 2.0.

Both workforces must access AWS accounts through the organization's IAM Identity Center access portal, with centrally managed permission sets. Employees must continue authenticating against their existing identity systems without migrating passwords. The external IdP can broker authentication to the company's Active Directory and present identities from both workforces to downstream applications. The company must retain a single AWS organization.

Which solution meets these requirements?

**Correct answer:** Configure the external IdP to broker authentication to Active Directory. Change the organization's IAM Identity Center identity source to the external IdP and establish SAML 2.0 federation. Make both workforces' users and groups available in IAM Identity Center and assign the required permission sets.

**Explanation:** The external IdP becomes the organization's single IAM Identity Center identity source while brokering authentication for the Active Directory workforce. Both workforces can retain their existing upstream authentication systems and use the same AWS access portal and centrally managed permission sets. Users and groups must also be provisioned into IAM Identity Center for assignments.

### Question 4 (DVA-C02)

**Question:**

A company is developing a browser-based application for employees. Employees must sign in through the company's existing identity provider, which supports only SAML 2.0. Employee passwords must remain with that provider. The application needs JWTs from an AWS-managed authentication service to establish application sessions and authorize requests to its API. The browser does not need AWS credentials or direct access to AWS resources. Which solution meets these requirements with the least custom authentication code?

**Correct answer:** Create a Cognito user pool and configure the corporate provider as a SAML identity provider using its metadata. Map the required attributes, enable the provider for an app client, and use the authorization code flow through Cognito's managed sign-in endpoints.

**Explanation:** A Cognito user pool can federate authentication to a SAML identity provider and then issue its own ID and access tokens. The corporate provider retains responsibility for password authentication, while Cognito supplies application tokens without requiring AWS credentials in the browser.

### Question 5 (AIP-C01)

**Question:**

A company runs automated evaluation of an Amazon Bedrock application from an externally hosted CI platform. The platform issues signed OpenID Connect (OIDC) tokens from one issuer shared by many customers. Tokens for the company's approved production workflow contain aud=sts.amazonaws.com and sub=repo:contoso/genai-evals:environment:production. The platform guarantees that only jobs authorized for this protected environment receive that subject value.

The company has registered the platform's OIDC provider in IAM. A production evaluation role already permits only the required Bedrock invocation actions on an approved model. Jobs must obtain AWS credentials without storing AWS access keys. Jobs from other repositories or environments must not be able to obtain credentials for this role, even if they know its ARN and can request tokens from the same issuer.

Which implementation meets these requirements?

**Correct answer:** Allow sts:AssumeRoleWithWebIdentity in the role trust policy for the registered OIDC provider. Require exact matches for the provider-prefixed aud and sub condition keys using the specified values. Have the job exchange its OIDC token for temporary credentials and use them to sign Bedrock requests.

**Explanation:** AWS STS validates the OIDC token, and the trust policy restricts credential issuance to the intended audience and the exact protected production workload. AssumeRoleWithWebIdentity does not require preexisting AWS credentials. The role's existing permissions then restrict what the resulting session can invoke.

### Question 6 (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 7 (SCS-C03)

**Question:**

A company uses an external SAML 2.0 identity provider (IdP) with an organization instance of AWS IAM Identity Center. SCIM provisions users and groups from the same corporate directory. The CloudInvestigators group is assigned an Investigation permission set in six AWS accounts.

After an IdP provisioning change, newly added investigators can authenticate successfully to the AWS access portal but cannot see any AWS accounts. Existing investigators retain access. A security engineer verifies the following:
• Each affected investigator has exactly one active user record in the Identity Center identity store, and SAML sign-in resolves to that record.
• The existing CloudInvestigators group has the correct account assignments, and its permission set is successfully provisioned in all six accounts.
• The corporate directory lists the affected investigators as group members, and their signed SAML assertions include the CloudInvestigators group name.
• The affected users are missing from the group's membership in the Identity Center identity store because SCIM membership updates are failing.

The company requires access to remain controlled through the existing directory-managed group and account assignments, without individual user assignments or manually maintained IAM roles. Which change will restore access?

**Correct answer:** Repair the SCIM provisioning configuration and synchronize the affected users' membership into the existing CloudInvestigators group in the Identity Center identity store.

**Explanation:** SAML authenticates the users, but Identity Center evaluates the existing group assignments using membership in its identity store. A group name in a SAML assertion does not populate that membership. Repairing SCIM membership synchronization makes the affected users eligible for the existing account assignments without changing roles or assigning users individually.

### Question 8 (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.

### Question 9 (ANS-C01)

**Question:**

A company uses a corporate SAML identity provider to federate network engineers into a NetworkOperator role in a central tooling account. An existing command-line tool runs with this role's temporary credentials and calls AWS STS AssumeRole to obtain credentials for a RouteMaintenance role in each workload account. The tool then creates, replaces, or deletes routes in approved VPC route tables across two AWS Regions. Route table IDs are supplied to the tool.

The workload-account roles have not yet been configured. The NetworkOperator role currently has only read-only Amazon EC2 permissions. The company must preserve the existing federation and tool workflow, use no long-lived credentials, and grant only the required route-management access. No service control policies, permissions boundaries, or session policies restrict the required actions.

Which configuration meets these requirements?

**Correct answer:** Allow NetworkOperator to call sts:AssumeRole on the designated RouteMaintenance role ARNs. Configure each RouteMaintenance role's trust policy to trust NetworkOperator for sts:AssumeRole. Attach permissions to RouteMaintenance allowing ec2:CreateRoute, ec2:ReplaceRoute, and ec2:DeleteRoute on the approved route table ARNs, restricted to the required Regions.

**Explanation:** Cross-account role assumption requires authorization for the caller and an appropriate trust policy on the destination role. After assuming RouteMaintenance, the tool uses that role's permissions—not NetworkOperator's permissions—to change routes. Scoping the route actions to approved route table ARNs and the required Regions provides least-privilege access while preserving temporary credentials and the existing workflow.

## Practice Identity Federation in a full exam

Questions on Identity Federation in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 13 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): 8 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 5 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 3 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 2 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 1 question
- [AIP-C01](https://blowstack.com/practice-exams/aws-certified-generative-ai-developer-professional): 1 question
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is Identity Federation

Identity federation is a trust arrangement between an identity provider, which authenticates an identity, and a relying party, which accepts evidence of that authentication. Instead of creating a separate password for every cloud account or application, an organization can use its existing identity system. The relying party validates the evidence and maps the identity to a local account, application session, role, or set of permissions. Federation does not require copying the identity's password into the destination system.

A typical flow begins when an engineer opens a cloud access portal and is redirected to the corporate identity provider. After authentication, potentially including multi-factor authentication, the provider issues a signed assertion or token. The relying party checks the signature, issuer, intended audience, validity period, and other required claims before accepting it. SAML 2.0 and OpenID Connect are common federation protocols. OAuth 2.0 primarily addresses delegated authorization; OpenID Connect adds an identity layer, so an arbitrary OAuth access token should not be treated as proof of user identity.

For workforce access in AWS, IAM Identity Center can connect to an external identity provider and assign users or groups access to accounts through permission sets. Those assignments result in access through IAM roles rather than requiring an IAM user for every employee in every account. SAML handles sign-in federation, while SCIM can provision and synchronize users and groups; provisioning and authentication are different functions. Direct SAML federation to IAM roles is another option, with AWS Security Token Service issuing temporary credentials through AssumeRoleWithSAML.

Federation also applies to applications and systems. A deployment pipeline can present an OpenID Connect token to AWS STS using AssumeRoleWithWebIdentity, avoiding a stored, long-lived AWS access key. Its role trust policy should constrain the trusted provider, audience, and subject, such as a specific repository and deployment environment. Customer-facing applications can use Amazon Cognito user pools to federate sign-in from external providers. Cognito identity pools serve a different purpose: they can exchange supported identity tokens for temporary AWS credentials. For workloads outside AWS, IAM Roles Anywhere uses trusted X.509 certificates to obtain temporary role credentials rather than relying on an interactive human login.

Authentication establishes who the caller is; authorization determines what that caller may do. An IAM role trust policy controls which principals can assume the role and under what conditions. The role's permissions policies define allowed actions, subject to other applicable controls such as service control policies, permissions boundaries, session policies, and explicit denies. A successful federated login therefore does not guarantee access to a resource. Amazon Verified Permissions addresses application authorization using policies and identity context; it is not a replacement for an identity provider or IAM authorization of AWS API calls.

Cross-account role assumption is a related trust pattern, but not every cross-account request involves external identity federation. For a principal in one AWS account to assume a role in another, the caller needs permission to call AssumeRole and the destination role must trust the caller. Some services also support direct cross-account access through resource-based policies without assuming a destination role. Evaluate the actual principal and the applicable identity and resource policies. IAM paths help organize identities and roles, but do not create security boundaries by themselves.

MFA strengthens authentication but is not itself federation. With an external identity provider, enforce MFA there and verify how authentication assurance is represented and checked downstream. Do not assume that IAM MFA condition keys automatically reflect MFA performed by an external provider. Likewise, single sign-on is a user experience that federation can enable, not a synonym for every federation deployment.

Federation reduces password duplication and long-lived credential exposure, but concentrates risk and availability dependencies in the identity provider and trust configuration. Restrict accepted issuers and claims, protect signing keys, rotate certificates safely, use suitable session durations, and preserve attributable session identities in audit logs. Disabling a user at the provider does not necessarily invalidate already-issued application sessions or AWS temporary credentials immediately. Troubleshooting should distinguish failed authentication, invalid assertions, failed role assumption, and denied resource access; common causes include expired certificates, clock skew, audience mismatches, incorrect claim mappings, missing assignments, and restrictive policies.

## Learn Identity Federation in lessons

9 short lessons on Identity Federation in 7 certification courses.

- CLF-C02: Identity Federation: trusted sign-in to AWS (Premium), https://app.blowstack.com/lessons/identity-federation-trusted-sign-in-to-aws-clf-c02
- SOA-C03: Identity Federation: trusted access to AWS roles (Premium), https://app.blowstack.com/lessons/identity-federation-trusted-access-to-aws-roles-soa-c03
- SAP-C03: Identity Federation: trust and claim mapping (free), https://app.blowstack.com/lessons/identity-federation-trust-and-claim-mapping-sap-c03
- AIP-C01: Identity Federation: enterprise identities to AWS role sessions (Premium), https://app.blowstack.com/lessons/identity-federation-enterprise-identities-to-aws-role-sessions-aip-c01
- SAA-C03: Identity Federation: workforce access through trusted identity providers (Premium), https://app.blowstack.com/lessons/identity-federation-workforce-access-through-trusted-identity-providers-saa-c03
- SCS-C03: Cross-Account Access vs. Identity Federation (Premium), https://app.blowstack.com/lessons/cross-account-access-vs-identity-federation-scs-c03
