# Encryption In Elasticsearch

**URL:** https://discuss.elastic.co/t/encryption-in-elasticsearch/360778
**Category:** Elasticsearch
**Created:** [June 4, 2024, 11:26am UTC](https://discuss.elastic.co/t/encryption-in-elasticsearch/360778 "2024-06-04T11:26:40Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [June 4, 2024, 11:40am UTC](https://discuss.elastic.co/t/encryption-in-elasticsearch/360778/2 "2024-06-04T11:40:56Z")

</div>

Encryption in Transit is done by configuring Elasticsearch to use TLS on both the transport and http endpoints.

The documentation for it starts [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/manually-configure-security.html) and there are also plenty of posts already on the forum about it.

Encryption at REST is not done by Elasticsearch, but by the operating system as explained in this [post](https://discuss.elastic.co/t/how-should-i-encrypt-data-at-rest-with-elasticsearch/96), for linux normally you just enable _dm-crypt_ on your server.

---

_[View the full topic](https://discuss.elastic.co/t/encryption-in-elasticsearch/360778)._