A company is setting up federated single sign-on (SSO) using a SAML 2.0 compliant corporate identity provider (IdP). They have already created the SAML identity provider entity in AWS IAM. To allow corporate users to federate into the AWS account, they need to create an IAM role. What must be configured in the trust policy of this IAM role to allow successful federation?
- Specify the SAML identity provider as the principal and allow the sts:AssumeRoleWithSAML action.Answer
- BSpecify the SAML identity provider as the principal and allow the sts:AssumeRole action.
- CSpecify the SAML identity provider as the principal and allow the sts:AssumeRoleWithWebIdentity action.
- DConfigure an Organization-level Service Control Policy (SCP) to grant permission for the corporate directory to assume roles across all accounts.
Answer
Specify the SAML identity provider as the principal and allow the sts:AssumeRoleWithSAML action.
The correct answer specifies mapping the SAML identity provider as the principal and allowing the sts:AssumeRoleWithSAML action because the AWS Security Token Service (STS) requires this specific API action to handle assertions generated by a SAML 2.0-compliant Identity Provider (IdP).
Step-by-Step Solution
Key Concept
SAML 2.0 Identity Federation Trust Relationships
Estimated Time:45s