# Enterprise-search.yml is not a valid YAML file

**URL:** <https://discuss.elastic.co/t/enterprise-search-yml-is-not-a-valid-yaml-file/235589>\
**Category:** Elastic Search\
**Tags:** elastic-workplace-search\
**Created:** [June 3, 2020, 3:18pm UTC](https://discuss.elastic.co/t/enterprise-search-yml-is-not-a-valid-yaml-file/235589 "2020-06-03T15:18:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![schoffelman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/schoffelman/32/18461_2.png) [@schoffelman](https://discuss.elastic.co/u/schoffelman)\
**Post date:** [June 3, 2020, 3:18pm UTC](https://discuss.elastic.co/t/enterprise-search-yml-is-not-a-valid-yaml-file/235589/1 "2020-06-03T15:18:07Z")

</div>

When following the installer instructions for my localhost install, I'm getting a `Invalid config file (...): /Users/...enterprise-search.yml is not a valid YAML file`.

In my elasticsearch.yml file I have `xpack.security.enabled: true` set and I have confirmed my ES instance is running at 9200.

Here is my enterprise-search.yml file (I took out all the comments as well, thinking I had a miskey somewhere):

```auto
secret_management.encryption_keys: [{SECRET_KEY}]

allow_es_settings_modification: true
elasticsearch.username: elastic
elasticsearch.password: PASSWORD
ent_search.external_url: http://localhost:3002
ent_search.listen_host: 127.0.0.1
ent_search.auth.source: standard

```

---

<div class="post-metadata">

**Author:** ![MadsOhm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/madsohm/32/69154_2.png) [@MadsOhm](https://discuss.elastic.co/u/MadsOhm)\
**Post date:** [June 4, 2020, 6:05am UTC](https://discuss.elastic.co/t/enterprise-search-yml-is-not-a-valid-yaml-file/235589/2 "2020-06-04T06:05:27Z")

</div>

Hi Tim

Wow, that's a bit odd. I just tried copy-pasting your `enterprise-search.yml` file into my own. Of course, it complains about the `secret_management.encryption_keys` not being an array of strings. (It should be something like `secret_management.encryption_keys: ['abcd1234']`) However, other than that it seems to just work.

Can you post a more complete backtrace of the error?

---

<div class="post-metadata">

**Author:** ![schoffelman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/schoffelman/32/18461_2.png) [@schoffelman](https://discuss.elastic.co/u/schoffelman)\
**Post date:** [June 8, 2020, 3:19pm UTC](https://discuss.elastic.co/t/enterprise-search-yml-is-not-a-valid-yaml-file/235589/3 "2020-06-08T15:19:41Z")

</div>

Hey @MadsOhm - after looking closer, it looks like I was missing a single quote in my key array. Thanks for the feedback!

---

<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:** [June 22, 2020, 3:19pm UTC](https://discuss.elastic.co/t/enterprise-search-yml-is-not-a-valid-yaml-file/235589/4 "2020-06-22T15:19:47Z")

</div>

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