A solutions architect is configuring single sign-on access to a member account within AWS Organizations. The architect establishes a trust relationship with an external SAML 2.0 Identity Provider (IdP) by creating an IAM identity provider in the member account. However, when corporate directory users attempt to federate, the authentication flow fails when trying to assume the designated target role.
Which of the following represents the correct configuration required in the target IAM role's trust policy to resolve this issue?
- Configure the IAM role trust policy to define the SAML identity provider as the principal and allow the sts:AssumeRoleWithSAML action.Cevap
- BConfigure the IAM role trust policy to define the corporate user directory as the principal and allow the sts:AssumeRole action.
- CAttach a Service Control Policy to the organizational unit that explicitly allows the sts:AssumeRoleWithSAML action for external identity providers.
- DConfigure the IAM role trust policy to define the SAML identity provider as the principal and allow the sts:AssumeRoleWithWebIdentity action.
Cevap
Configure the IAM role trust policy to define the SAML identity provider as the principal and allow the sts:AssumeRoleWithSAML action.
The configuration that defines the SAML identity provider as the principal and allows the sts:AssumeRoleWithSAML action is correct. This is because AWS STS requires this specific API action to exchange a SAML assertion for temporary credentials, and the IAM role's trust policy must specify the IAM SAML identity provider as the trusted principal.
Adım Adım Çözüm
Anahtar Kavram
SAML 2.0 Federation Trust Policy Configuration