A company is designing a multi-account environment on AWS using AWS Organizations. The company has several business units, each requiring its own dedicated account under a specific OU. The security team requires centralized user authentication using the company's external identity provider. Additionally, the security team must prevent any member account from leaving the organization. Which of the following actions should the solutions architect take to meet these requirements? (Select TWO.)
- Configure AWS IAM Identity Center connected to the external identity provider to centrally manage user access across all accounts.Answer
- Apply a Service Control Policy (SCP) at the root level of the organization that denies the organizations:LeaveOrganization API action.Answer
- CCreate individual IAM users in each member account and configure SAML 2.0 federation mapping for each corporate user.
- DApply a Service Control Policy (SCP) to the organization's management account to restrict the administrative actions of its root user.
- ECreate IAM users in the management account with administrative permissions and configure cross-account roles to access each member account.
Answer
Configure AWS IAM Identity Center connected to the external identity provider, and apply a Service Control Policy (SCP) at the root level that denies the organizations:LeaveOrganization action.
Integrating AWS IAM Identity Center with the external identity provider is the native, scalable method to grant federated access to AWS accounts without manual credential configuration. Applying a Service Control Policy that denies the organizations:LeaveOrganization action at the root level ensures that no member account can detach itself from the organization's governance boundary.
Step-by-Step Solution
Key Concept
Centralized multi-account governance using AWS Organizations SCPs and AWS IAM Identity Center.