> 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/prerequisites-and-installation-requirements/ssl-certificate-requirements.md).

# SSL Certificate Requirements

Eko AD Sync relies on Secure Sockets Layer (SSL) certificates to ensure that communication between components — especially the Eko Active Directory Connector (EkoADC) and the Eko — is encrypted via HTTPS. The requirements for certificates vary based on whether the standard Eko certificate is used or if the customer opts for their own.

## 1. Standard Eko SSL Certificate

In the majority of client deployments, Amity Solutions uses the Eko SSL certificate for the client's EkoADC.

* **Expiration**: These certificates are designed to last for 10 years, meaning they do not require frequent renewal

## 2. Customer-Provided SSL Certificates

Some clients may require their own SSL certificates in the EkoADC.

* **Expiration**: Unlike the standard Eko certificates, customer-provided certificates typically expire yearly, requiring routine renewal.

## 3. Customer Responsibilities for Renewal

If the customer chooses to use their own certificates, they are responsible for providing the necessary files and preparing the environment for renewal:

1. **Certificate Generation**: The customer must generate the new certificate files.
2. **File Placement**: The client must place the required files (.crt and .key) on the EkoADC server.
3. **Scheduling**: The customer must then schedule a meeting with the Eko operations team (EkoTier2 or DevOps) to remote into the server and install the new certificate

### 3.1 Eko Operations Renewal Process Overview

The Eko team handles the technical steps for installing the customer-provided certificate on the EkoADC server. This includes:

* **File Preparation**: Creating a new folder inside `/app` and placing the client's certificate files there.
* **Conversion to PEM**: Converting the provided key/certificate files into the required .pem format.
* **Configuration Update**: Updating the `docker-compose.yaml` file to use the new certificate path.


---

# 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/prerequisites-and-installation-requirements/ssl-certificate-requirements.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.