# File permissions on ES certificate files in Docker

**URL:** <https://discuss.elastic.co/t/file-permissions-on-es-certificate-files-in-docker/279764>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [July 27, 2021, 5:31pm UTC](https://discuss.elastic.co/t/file-permissions-on-es-certificate-files-in-docker/279764 "2021-07-27T17:31:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![braddre](https://avatars.discourse-cdn.com/v4/letter/b/a5b964/32.png) [@braddre](https://discuss.elastic.co/u/braddre)\
**Post date:** [July 27, 2021, 5:31pm UTC](https://discuss.elastic.co/t/file-permissions-on-es-certificate-files-in-docker/279764/1 "2021-07-27T17:31:36Z")

</div>

I've set up a three node ES cluster under Docker using these instructions: [Encrypting communications in an Elasticsearch Docker Container | Elasticsearch Guide [7.13] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/configuring-tls-docker.html)

I'm using ES 7.6.2

In this set up, the certificate and key files reside on the host, and the container has access to them through a docker volume.

I noticed that the file permissions on the certificate and key are 664. In the interest of further securing our environment I changed the permissions to 660, but when I did the ES cluster would not form due to a file access error

Does ES depend on the file permissions being 664 for the certificate and key files? Is there a way to change the file bits to a less permissive setting?

---

<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:** [August 24, 2021, 5:31pm UTC](https://discuss.elastic.co/t/file-permissions-on-es-certificate-files-in-docker/279764/2 "2021-08-24T17:31:48Z")

</div>

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