> For the complete documentation index, see [llms.txt](https://jembi.gitbook.io/openhim-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jembi.gitbook.io/openhim-platform/packages/analytics-datastore-elasticsearch/environment-variables.md).

# Environment Variables

<table><thead><tr><th width="170">Variable Name</th><th width="97">Type</th><th width="231">Relevance</th><th width="104">Required</th><th>Default</th></tr></thead><tbody><tr><td>ES_ELASTIC</td><td>String</td><td>Elasticsearch super-user password</td><td>Yes</td><td>dev_password_only</td></tr><tr><td>ES_KIBANA_SYSTEM</td><td>String</td><td>The password for the user Kibana used to connect and communicate with Elasticsearch</td><td>Yes</td><td>dev_password_only</td></tr><tr><td>ES_LOGSTASH_SYSTEM</td><td>String</td><td>The password for the user Logstash used to map and transform the data before storing it in Elasticsearch</td><td>Yes</td><td>dev_password_only</td></tr><tr><td>ES_BEATS_SYSTEM</td><td>String</td><td>The password for the user the Beats use when storing monitoring information in Elasticsearch</td><td>Yes</td><td>dev_password_only</td></tr><tr><td>ES_REMOTE_MONITORING_USER</td><td>String</td><td>The password for the user Metricbeat used when collecting and storing monitoring information in Elasticsearch. It has the remote_monitoring_agent and remote_monitoring_collector built-in roles</td><td>Yes</td><td>dev_password_only</td></tr><tr><td>ES_APM_SYSTEM</td><td>String</td><td>The password for the user of the APM server used when storing monitoring information in Elasticsearch</td><td>Yes</td><td>dev_password_only</td></tr><tr><td>ES_LEADER_NODE</td><td>String</td><td><p>Specify the leader service name (the service name in case single mode and the leader service name in case cluster mode)</p><p>This is used for the config importer. Specifying the service name to initialize the mapping inside Elasticsearch</p></td><td>Yes</td><td>analytics-datastore-elastic-search</td></tr><tr><td>ES_HEAP_SIZE</td><td>String</td><td><p>The heap size is the amount of RAM allocated to the Java Virtual Machine of a node in Elasticsearch</p><p>It should be set -Xms and -Xmx to the same value (50% of the total available RAM to a maximum of 31GB)</p></td><td>No</td><td>-Xms2048m -Xmx2048m</td></tr><tr><td>ES_SSL</td><td>Boolean</td><td>This variable is used only for the config importer of Elasticsearch (internal connection between docker services the elastic and the importer)</td><td>No</td><td>false</td></tr><tr><td>ES_MEMORY_LIMIT</td><td>String</td><td>RAM usage limit of Elasticsearch service</td><td>No</td><td>3G</td></tr><tr><td>ES_MEMORY_RESERVE</td><td>String</td><td>Reserved RAM for Elasticsearch service</td><td>No</td><td>500M</td></tr><tr><td>ES_PATH_REPO</td><td>String</td><td>The path to the repository in the container to store Elasticsearch backup snapshots</td><td>No</td><td>/backups/elasticsearch</td></tr></tbody></table>


---

# 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://jembi.gitbook.io/openhim-platform/packages/analytics-datastore-elasticsearch/environment-variables.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.