

When you configure AD Connector, you provide it with service account credentials that are securely stored by AWS. AD Connector forwards sign-in requests to your Active Directory domain controllers for authentication and provides the ability for applications to query the directory for data. AD Connector – Under the HoodĪD Connector is a dual Availability Zone proxy service that connects AWS apps to your on-premises directory. This blog post will show you how AD Connector works as well as walk through how to enable federated console access, assign users to roles, and seamlessly join an EC2 instance to an Active Directory domain. In sum, AD Connector helps to foster a hybrid environment by allowing you to leverage your existing on-premises investments to control different facets of AWS. And because AD Connector doesn’t rely on complex directory synchronization technologies or Active Directory Federation Services (AD FS), you can forego the added cost and complexity of hosting a SAML-based federation infrastructure. Also, your users will no longer need to remember yet another user name and password combination. It also enables you to reuse your existing Active Directory security policies such as password expiration, password history, and account lockout policies. With AD Connector, you can streamline identity management by sourcing and managing all your user identities from Active Directory. Custom applications relying on your on-premises Active Directory should communicate with your domain controllers directly.
