Directory Service offers different ways to use Active Directory features and existing credentials in AWS.
Managed AD, AD Connector, and Simple AD
AWS DirectoryA directory stores information about users, groups and devices for managing access. Service offers ways to use directories, which store users, groups and devices, with AWS applications. Choose between a managed directory and a gateway to an existing one.
How it works
- AWS Managed Microsoft AD runs Microsoft Active Directory in AWS with two managed domain controllersA domain controller is a server that handles Active Directory requests., servers that handle directory requests, in different Availability Zones.
- A trust allows users in an existing Active Directory to access resources in the managed directory with their existing credentials. Hybrid Edition extends an existing self-managed directory without synchronizing user identities.
- AD Connector is a proxy, or intermediary, that forwards requests to existing AD without caching directory information in AWS.
- Simple AD is a separate Samba-based directory with basic Active Directory features. As of November 2026, it is closed to new customers, but existing customers may create more directories.
IAM Identity Center can use an Active Directory identity sourceAn identity source defines where users and groups are managed for IAM Identity Center. to assign access to accounts and applications. It synchronizes users, groups and memberships to its identity store, but not passwords; sign-in authentication uses the source directory.
| Option | Choose it for | Important limit |
|---|---|---|
| AWS Managed Microsoft AD | Microsoft AD features, trusts and RDS for SQL Server | It creates a managed directory. |
| AD Connector | Existing AD credentials for compatible AWS applications | One connector per domain; no RDS for SQL Server. |
| Simple AD | Basic directory features for existing customers | No trusts, MFAMulti-factor authentication requires an additional factor, such as a code, alongside a password., IAM Identity Center or RDS for SQL Server. |
Exam cues
- If the question says use on-premises credentials without copying directory data, think AD Connector, because it forwards requests to the existing directory.
- If the question says RDS for SQL Server needs Active Directory, think AWS Managed Microsoft AD, because the other two options do not support that integration.
- If the question says connect an existing directory to IAM Identity Center, think Managed Microsoft AD or AD Connector, not Simple AD.
Remember
- AWS Managed Microsoft AD creates two domain controllers across Availability Zones.
- AD Connector requires one connector per domain. It can use an existing RADIUSRADIUS is a protocol for authentication, authorization and accounting for network services. authentication server for multi-factor authentication (MFA), an additional sign-in check, for AWS applications.
- Simple AD does not support trusts or MFA.
Trap: AD Connector is a proxy, not a new managed Microsoft Active Directory. Simple AD is not an IAM Identity Center identity source.
The AWS application sends a directory request to AD Connector.
AD Connector forwards the request to the existing directory.
From the AWS docs (15)
- Directories store information about users, groups and devices and help administrators manage access.
- AWS Managed Microsoft AD runs Microsoft Active Directory as an AWS managed service and creates two domain controllers across Availability Zones.
- AWS Managed Microsoft AD can establish a trust with existing Active Directory so users can access resources using their existing credentials.
- AWS Managed Microsoft AD supports RDS for SQL Server; AD Connector and Simple AD are not compatible with RDS for SQL Server.
- AD Connector redirects directory requests to an existing Active Directory without caching directory information in the cloud.
- Each on-premises domain that users authenticate against requires its own AD Connector; transitive trusts are not supported.
- AD Connector can integrate with an existing RADIUS-based MFA infrastructure for AWS applications.
- RADIUS is a protocol for authentication, authorization and accounting for network services.
- Simple AD is a standalone managed directory powered by Samba 4 and supports a subset of Active Directory features.
- Simple AD does not support MFA, domain trusts, schema extensions, IAM Identity Center or RDS for SQL Server.
- As of November 2026, Simple AD is closed to new customers; existing customers can continue to create directories.
- IAM Identity Center supports an Active Directory identity source but does not support Simple AD.
- IAM Identity Center synchronizes users, groups and memberships from Active Directory but not passwords; authentication occurs against the source directory.
- AWS Managed Microsoft AD Hybrid Edition extends an existing self-managed Active Directory to AWS without synchronizing user identities.
- AWS Managed Microsoft AD supports one-way and two-way external and forest trusts with self-managed on-premises Active Directory and with other AWS Managed Microsoft AD directories.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 8 cards as a list
An organization has on-premises Active Directory. How do AWS Managed Microsoft AD, AD Connector and Simple AD differ?
Managed Microsoft AD runs Microsoft AD in AWS and can establish a trust. AD Connector forwards requests to existing AD. Simple AD is a standalone Samba-based directory with fewer features.
Which AWS service provides managed Microsoft Active Directory or connects supported AWS applications to an existing directory?
AWS Directory Service. Choose AWS Managed Microsoft AD for a managed directory or AD Connector to forward requests to an existing directory.
A company wants IAM Identity Center users to sign in with their existing Active Directory credentials. Where does authentication occur?
Against the source Active Directory. IAM Identity Center synchronizes users, groups and memberships, but not passwords.
A company wants AWS applications to authenticate against its existing on-premises AD without caching directory data in AWS. What should it use?
AD Connector forwards directory requests to the existing AD without caching directory information in the cloud.
Can a new customer create Simple AD directories or use Simple AD as an IAM Identity Center identity source?
No. Simple AD is closed to new customers and is not supported as an IAM Identity Center identity source.
An organization needs users from two on-premises Active Directory domains to authenticate through AD Connector. How many connectors are required?
One connector per domain, so two. AD Connector does not support transitive trusts.
When IAM Identity Center uses Active Directory as its identity source, are Active Directory passwords synchronized to the IAM Identity Center identity store?
No. IAM Identity Center synchronizes users, groups and memberships, while authentication happens against the source directory.
Users in an on-premises Active Directory must reach AWS applications joined to AWS Managed Microsoft AD, and the AWS side must trust on-premises identities too. What links the directories?
A two-way forest (or external) trust between AWS Managed Microsoft AD and the on-premises AD.