A company is configuring federated single sign-on (SSO) to multiple target AWS accounts using an on-premises SAML 2.0 Identity Provider (IdP). To enable corporate users to authenticate and access the target accounts, an administrator must create IAM roles in each target account. Which action must be included in the trust policy of these IAM roles to allow users to assume them via the SAML Identity Provider?
- ASpecify the sts:AssumeRole action, listing the corporate domain names as the trusted principals.
- BAttach a Service Control Policy (SCP) at the root of the AWS Organization to authorize the sts:AssumeRole action for the external corporate network.
- Specify the sts:AssumeRoleWithSAML action, listing the SAML provider as the trusted principal.Answer
- DSpecify the sts:AssumeRoleWithWebIdentity action, listing the corporate Active Directory domain controllers as the trusted web identity providers.
Answer
Specify the sts:AssumeRoleWithSAML action, listing the SAML provider as the trusted principal.
For SAML 2.0 federation, target IAM roles require a trust policy that permits the Security Token Service (STS) action sts:AssumeRoleWithSAML. The trust policy must specify the SAML Identity Provider as the principal to allow users authenticated by the IdP to obtain temporary AWS security credentials.
Step-by-Step Solution
Key Concept
SAML 2.0 Federation Trust Policy Action