# Encryption at rest support

**URL:** <https://discuss.elastic.co/t/encryption-at-rest-support/113537>\
**Category:** Elasticsearch\
**Created:** [December 29, 2017, 6:24am UTC](https://discuss.elastic.co/t/encryption-at-rest-support/113537 "2017-12-29T06:24:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Magnus\_Kessler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnus_kessler/32/42001_2.png) [@Magnus\_Kessler](https://discuss.elastic.co/u/Magnus_Kessler)\
**Post date:** [December 29, 2017, 6:51am UTC](https://discuss.elastic.co/t/encryption-at-rest-support/113537/2 "2017-12-29T06:51:00Z")

</div>

Jiali,

This question was previously answered [here](https://discuss.elastic.co/t/encryption-at-rest-support-in-x-pack-platinum/100111). It's option 2 on your list.

An encrypted file system has to be set up on each node. The overhead of encryption depends on how well your CPUs support the additional mathematical operations required to encrypt the data, and any overhead incurred by the FS stack. Maximum throughput and duration of individual queries are generally influenced by latencies in the FS.

---

_[View the full topic](https://discuss.elastic.co/t/encryption-at-rest-support/113537)._