# Encryption of logstash configuration files

**URL:** <https://discuss.elastic.co/t/encryption-of-logstash-configuration-files/70408>\
**Category:** Logstash\
**Created:** [January 3, 2017, 9:16am UTC](https://discuss.elastic.co/t/encryption-of-logstash-configuration-files/70408 "2017-01-03T09:16:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ruthvic](https://avatars.discourse-cdn.com/v4/letter/r/ce73a5/32.png) [@Ruthvic](https://discuss.elastic.co/u/Ruthvic)\
**Post date:** [January 3, 2017, 9:16am UTC](https://discuss.elastic.co/t/encryption-of-logstash-configuration-files/70408/1 "2017-01-03T09:16:37Z")

</div>

Hi. This is regarding the encryption of logstash config files. When we deploy the config files in the production environment, people should not be able to access the configuration files. So can we encrypt the config files and give it as an input to logstash or is there any efficient way to hide the config files?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [January 3, 2017, 9:24am UTC](https://discuss.elastic.co/t/encryption-of-logstash-configuration-files/70408/2 "2017-01-03T09:24:30Z")

</div>

The current best option is to limit file permissions, there is no way to encrypt things out of the box.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 31, 2017, 9:24am UTC](https://discuss.elastic.co/t/encryption-of-logstash-configuration-files/70408/3 "2017-01-31T09:24:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.