# Schedule Report - kibana.configuration trouble

**URL:** <https://discuss.elastic.co/t/schedule-report-kibana-configuration-trouble/383080>\
**Category:** Kibana\
**Created:** [October 29, 2025, 5:50pm UTC](https://discuss.elastic.co/t/schedule-report-kibana-configuration-trouble/383080 "2025-10-29T17:50:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cristina\_Marletta\_Li](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cristina_marletta_li/32/137793_2.png) [@Cristina\_Marletta\_Li](https://discuss.elastic.co/u/Cristina_Marletta_Li)\
**Post date:** [October 29, 2025, 5:50pm UTC](https://discuss.elastic.co/t/schedule-report-kibana-configuration-trouble/383080/1 "2025-10-29T17:50:50Z")

</div>

Hi all,

I have Elastic Stack version 8.19. Is it possible to schedule report sending without using watchers or URLs?  
We tried configuring this in kibana.yml:

# Kibana Email settings

xpack.actions.preconfigured:  
my-email:  
name: preconfigured-email-connector-type  
actionTypeId: .email  
config:  
service: ses  
from: xxxxx@aaaa.it  
host: [email-smtp.eu-west-1.amazonaws.com](http://email-smtp.eu-west-1.amazonaws.com)  
port: 587  
secure: true  
hasAuth: true  
secrets:  
user: \*\*\*\*\*\*\*\*\*\*\*\*\*\*  
password:\*\*\*\*\*\*\*\*\*\*\*\*\*

notifications.connectors.default.email: my-email

But kibana doesn't start and we can't find any relevant errors in kibana.log.

---

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [October 30, 2025, 3:23am UTC](https://discuss.elastic.co/t/schedule-report-kibana-configuration-trouble/383080/2 "2025-10-30T03:23:35Z")

</div>

Hello @Cristina_Marletta_Li

As per the below documentation it can be done via script as well :

> **[Automatically generate reports | Kibana Guide \[8.19\] | Elastic](https://www.elastic.co/guide/en/kibana/8.19/automating-report-generation.html)**

As per the information shared i see you are using service as ses :

> **[Preconfigured connectors | Kibana Guide \[8.19\] | Elastic](https://www.elastic.co/guide/en/kibana/8.19/pre-configured-connectors.html#preconfigured-email-configuration)**

Could you please review the configuration once, also if Kibana is not starting there should be some logs which could help to find the exact cause & correct the configuration in kibana.yml

Thanks!!

---

<div class="post-metadata">

**Author:** ![Cristina\_Marletta\_Li](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cristina_marletta_li/32/137793_2.png) [@Cristina\_Marletta\_Li](https://discuss.elastic.co/u/Cristina_Marletta_Li)\
**Post date:** [November 3, 2025, 3:50pm UTC](https://discuss.elastic.co/t/schedule-report-kibana-configuration-trouble/383080/3 "2025-11-03T15:50:29Z")

</div>

Hi Tortoise, thanks.

It works now (I'm copying the working configuration below, although the formatting has been lost in the copy). Oddly enough, however, for it to work, we had to set  
. service: other  
. hasAuth: true

even though the documentation states:  
. service: ses  
. hasAuth: false (if the password is stored in kibana.keystore)

```auto
xpack.actions.preconfigured:
my-email:
name: preconfigured-email-connector-type
actionTypeId: .email
config:
service: other
from: ********@********.it
host: email-smtp.eu-west-1.amazonaws.com
port: 465
secure: true
hasAuth: true
secrets:
user: ************

notifications.connectors.default.email: my-email

```

We can't explain this behavior.

---

<div class="post-metadata">

**Author:** ![JSkier](https://avatars.discourse-cdn.com/v4/letter/j/e47c2d/32.png) [@JSkier](https://discuss.elastic.co/u/JSkier)\
**Post date:** [January 13, 2026, 4:34pm UTC](https://discuss.elastic.co/t/schedule-report-kibana-configuration-trouble/383080/4 "2026-01-13T16:34:53Z")

</div>

Thank you for posting what worked for you; it really helped us out. We were having issues getting report e-mails to work, and calling out the connector in the config worked (the docs call it something else, but it causes Kibana to fail to load).

`notifications.connectors.default.email`