> For the complete documentation index, see [llms.txt](https://docs.amitysolutions.com/ekoai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amitysolutions.com/ekoai/getting-started/eko/eko-ad-sync/introduction-to-eko-ad-sync/why-is-eko-adc-required-on-premises.md).

# Why is Eko ADC required On-Premises?

The need for the Eko Active Directory Connector (EkoADC) to be installed directly on your premises stems from the fundamental architecture separating Eko’s cloud environment from your organization's internal infrastructure.

## 1. The Problem of Communication

The Eko application is a Software as a Service (SaaS) product hosted entirely on the cloud. However, your organization's sensitive user information, credentials, and user profiles are stored within your own Local Active Directory (AD), located securely inside your Customer Data center.

Because the Local Active Directory is not typically exposed directly to the public internet, communication with Local AD cannot be established from the Eko side directly.

## 2. EkoADC as the Necessary Bridge

The Eko Active Directory Connector (EkoADC) is Amity Solutions’ proprietary software designed to bridge this security gap.

1. On-Premises Deployment: EkoADC must be deployed directly to the customer infrastructure (on-premises) to establish a secure, localized connection with your Active Directory.
2. Local Connectivity: Once installed locally, EkoADC can perform the necessary functions - such as LDAP binding for authentication and LDAP search for querying users - within your internal network.
3. Secure Environment: EkoADC runs on a securely hardened Ubuntu image, provided and configured to operate adjacent to your directory services.

Deploying EkoADC at the customer side is a required use case for user provisioning and AD authentication.

## 3. Eko AD Sync System Architecture Overview

The following table summarises how the EkoADC operates as the required component within your network boundary to facilitate user integration:

| Microsoft AD        | Customer Data center (On-Premises) | Stores user profiles and user credentials.                               |
| ------------------- | ---------------------------------- | ------------------------------------------------------------------------ |
| EkoADC              | Customer Data center (On-Premises) | Connects to AD via LDAP/LDAPS; handles sync and authentication requests. |
| Eko IDMAPI / Eko DB | Eko Cloud                          | Eko custom API and database hosting the application and user data.       |

The EkoADC mediates communication between the two separate environments using HTTPS for cloud communication and LDAP/LDAPS for internal communication with your Active Directory.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.amitysolutions.com/ekoai/getting-started/eko/eko-ad-sync/introduction-to-eko-ad-sync/why-is-eko-adc-required-on-premises.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.