Question

Difficulty: Very hardIdentity Federation and Directory Services

An enterprise is migrating its applications to a multi-account environment managed by AWS Organizations. The company's security policy requires corporate users to authenticate using their existing on-premises Active Directory credentials to access the AWS Management Console of various AWS accounts. The solution must enforce multi-factor authentication (MFA), minimize operational overhead, and avoid synchronizing passwords or user directory data to the cloud. Which two actions should a solutions architect take to implement this architecture? (Select two.)

  1. Enable AWS IAM Identity Center in the organization's management account and configure it to use Active Directory as the identity source.Answer
  2. Deploy an AWS Directory Service AD Connector in a VPC with VPN or Direct Connect connectivity to the on-premises domain controllers to proxy authentication requests.Answer
  3. C
    Provision individual IAM users in each member account for all Active Directory users, assigning long-term access keys and console passwords to each user.
  4. D
    Use the AWS account root user credentials of each AWS account to configure individual SAML 2.0 identity providers pointing to the on-premises Active Directory.

Answer

Enable AWS IAM Identity Center in the organization's management account and configure it to use Active Directory as the identity source, and deploy an AWS Directory Service AD Connector in a VPC with network connectivity to on-premises domain controllers to proxy authentication requests.
Centralizing access control through AWS IAM Identity Center enabled in the organization's management account satisfies the enterprise requirement to manage access across multiple accounts. Pairing it with AD Connector provides a secure authentication proxy that forwards requests directly to the on-premises domain controllers via VPN or Direct Connect, ensuring passwords and directory data are not synchronized or replicated to AWS.

Step-by-Step Solution

1
Select a centralized management solution for multi-account access control.
AWS IAM Identity Center is selected as it integrates with AWS Organizations and external directories.
This avoids having to manually configure federation or local users in each individual account.
2
Determine the directory integration method that avoids password synchronization and database replication.
AD Connector is selected because it acts as an active directory proxy redirecting authentication requests without synchronizing user database details to AWS.
This satisfies the constraint of avoiding password synchronization and minimizing operational overhead.
3
Ensure secure connectivity between AWS and on-premises network.
Deploy the AD Connector within a VPC that has a VPN or Direct Connect connection to the on-premises domain controllers.
The AD Connector needs local network routing to reach domain controllers on port 389/445/88/53.

Key Concept

Centralized multi-account federation using AWS IAM Identity Center coupled with AD Connector to leverage on-premises Active Directory without password synchronization.
Rate this question