# Watcher xpack settings when using elastic cloud

**URL:** <https://discuss.elastic.co/t/watcher-xpack-settings-when-using-elastic-cloud/173438>\
**Category:** Elasticsearch\
**Created:** [March 22, 2019, 7:19am UTC](https://discuss.elastic.co/t/watcher-xpack-settings-when-using-elastic-cloud/173438 "2019-03-22T07:19:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nzxtquad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nzxtquad/32/42564_2.png) [@nzxtquad](https://discuss.elastic.co/u/nzxtquad)\
**Post date:** [March 22, 2019, 7:19am UTC](https://discuss.elastic.co/t/watcher-xpack-settings-when-using-elastic-cloud/173438/1 "2019-03-22T07:19:36Z")

</div>

We are using elastic cloud as our elasticsearch/kibana environment and are using a local logstash instance for forwarding the logs. We are trying to setup a wachter alert (using the webhook functionality), we run into issues with our self-signed certificate, I found a way to work around this by using:

```
xpack.http.ssl.verification_mode: none

```

The issue is, as we are using the elastic cloud I have no way of editing the elasticsearch.yml, and i can't seem a way to do this otherwise.

---

<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:** [April 19, 2019, 7:19am UTC](https://discuss.elastic.co/t/watcher-xpack-settings-when-using-elastic-cloud/173438/2 "2019-04-19T07:19:53Z")

</div>

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