# Setting Alerting configuration on Kibana 7.9

**URL:** <https://discuss.elastic.co/t/setting-alerting-configuration-on-kibana-7-9/250530>\
**Category:** Kibana\
**Tags:** elastic-stack-alerting\
**Created:** [September 30, 2020, 3:07pm UTC](https://discuss.elastic.co/t/setting-alerting-configuration-on-kibana-7-9/250530 "2020-09-30T15:07:14Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![Patrick\_Mueller](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick_mueller/32/109425_2.png) [@Patrick\_Mueller](https://discuss.elastic.co/u/Patrick_Mueller)\
**Post date:** [October 1, 2020, 9:12pm UTC](https://discuss.elastic.co/t/setting-alerting-configuration-on-kibana-7-9/250530/10 "2020-10-01T21:12:41Z")

</div>

Yes, alerting should work without security. It sounds like the encryption key is not being set; we'll need to see the log messages from kibana. Given the message you see in the browser, I'd expect you'll see the following message in the logs:

```auto
APIs are disabled due to the Encrypted Saved Objects plugin using an ephemeral encryption key. 
Please set xpack.encryptedSavedObjects.encryptionKey in kibana.yml.

```

Can you paste the line in your `kibana.yml` with the `xpack.encryptedSavedObjects.encryptionKey` setting? You can replace the values in the key with X's if you want.

One note - the documentation notes the key should be 32 characters or longer. I'm not sure what happens if it's shorter, but it certainly won't used, and I would expect a separate log message about that.

---

_[View the full topic](https://discuss.elastic.co/t/setting-alerting-configuration-on-kibana-7-9/250530)._