Connect to your Microsoft AD directory - AWS Single Sign-On

Connect to your Microsoft AD directory

With AWS Single Sign-On, you can connect your self-managed directory in Active Directory (AD) or your AWS Managed Microsoft AD directory by using AWS Directory Service. This Microsoft AD directory defines the pool of identities that administrators can pull from when using the AWS SSO console to assign single sign-on (SSO) access. After connecting your corporate directory to AWS SSO, you can then grant your AD users or groups access to AWS accounts, cloud applications, or both.

AWS Directory Service helps you to set up and run a standalone AWS Managed Microsoft AD directory hosted in the AWS Cloud. You can also use AWS Directory Service to connect your AWS resources with an existing self-managed AD. To configure AWS Directory Service to work with your self-managed AD, you must first set up trust relationships to extend authentication to the cloud.

AWS SSO uses the connection provided by AWS Directory Service to perform pass-through authentication to the source AD instance, leveraging the Kerberos protocol. When you use AWS Managed Microsoft AD as your identity source, AWS SSO can work with users from AWS Managed Microsoft AD or from any domain connected through an AD trust. If you want to locate your users in four or more domains, users must use the DOMAIN\user syntax as their user name when performing sign-ins to AWS SSO.

Notes
  • As a prerequisite step, make sure your AD Connector or AWS Managed Microsoft AD directory in AWS Directory Service resides within your AWS Organizations management account. For more information, see AWS SSO prerequisites.

  • AWS SSO does not support SAMBA 4-based Simple AD as a connected directory.

Provisioning when users come from Active Directory

AWS SSO uses the connection provided by the AWS Directory Service to synchronize user, group, and membership information from your source directory in Active Directory to the AWS SSO identity store. No password information is synchronized to AWS SSO, since user authentication takes place directly from the source directory in Active Directory. This identity data is used by AWS SSO integrated applications to facilitate in-app lookup, authorization, and collaboration scenarios without passing LDAP activity back to the source directory in Active Directory.

For more information above provisioning, see User and group provisioning.