# ElasticSearch creates an empty plugins folder, why?

**URL:** <https://discuss.elastic.co/t/elasticsearch-creates-an-empty-plugins-folder-why/154253>\
**Category:** Elasticsearch\
**Created:** [October 26, 2018, 8:51pm UTC](https://discuss.elastic.co/t/elasticsearch-creates-an-empty-plugins-folder-why/154253 "2018-10-26T20:51:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![shabtaisharon](https://avatars.discourse-cdn.com/v4/letter/s/b77776/32.png) [@shabtaisharon](https://discuss.elastic.co/u/shabtaisharon)\
**Post date:** [October 26, 2018, 8:51pm UTC](https://discuss.elastic.co/t/elasticsearch-creates-an-empty-plugins-folder-why/154253/1 "2018-10-26T20:51:30Z")

</div>

Hi,

I'm using elastic search 6.4.2 and i notised that when i run it without any plugins configuted elastic still creates an empty plugins folder and wonders why? and if that is something that can be removed?

Thanks,  
Sharon

---

<div class="post-metadata">

**Author:** ![s1monw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s1monw/32/3637_2.png) [@s1monw](https://discuss.elastic.co/u/s1monw)\
**Post date:** [November 5, 2018, 1:31pm UTC](https://discuss.elastic.co/t/elasticsearch-creates-an-empty-plugins-folder-why/154253/2 "2018-11-05T13:31:21Z")

</div>

the main reason is that we give elasticsearch security permissions on startup and require the folder to be present at this point. It's generally best practice to not make an exception here.

---

<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:** [December 3, 2018, 1:31pm UTC](https://discuss.elastic.co/t/elasticsearch-creates-an-empty-plugins-folder-why/154253/3 "2018-12-03T13:31:23Z")

</div>

Closed on December 3, 2018, 1:31pm UTC

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