# Configuring Watcher with basic-auth and Elastic Cloud

**URL:** <https://discuss.elastic.co/t/configuring-watcher-with-basic-auth-and-elastic-cloud/132189>\
**Category:** Elasticsearch\
**Created:** [May 16, 2018, 5:19pm UTC](https://discuss.elastic.co/t/configuring-watcher-with-basic-auth-and-elastic-cloud/132189 "2018-05-16T17:19:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [May 16, 2018, 5:19pm UTC](https://discuss.elastic.co/t/configuring-watcher-with-basic-auth-and-elastic-cloud/132189/1 "2018-05-16T17:19:35Z")

</div>

Working on an Elastic Cloud project that I did not set up myself. Configuring a watch using an HTTP input back to itself. I am missing something incredibly basic since I get 404s. Using the same 'elastic' user used for our HTTP calls and Kibana access.

PUT \_xpack/watcher/watch/\_execute

{

"watch": {

"trigger": {

"schedule": {

"interval": "60s"

}

},

"input": {

"http": {

"request": {

"scheme": "https",

"host": "[xxx.found.io](http://xxx.found.io)",

"port": 9243,

"path": "/\_node/stats",

"auth": {

"basic": {

"username": "elastic",

"password": "xxx"

}

}

}

}

}

}

}

A more complete 404 error: [https://gist.github.com/brusic/bcb54acef23ddec26149a381c1f1edec](https://gist.github.com/brusic/bcb54acef23ddec26149a381c1f1edec)

Also attempted to use a full url to no avail:

{

"request": {

"url": "[https://elastic:password@XXX.found.io:9243/\_node/stats](https://elastic:password@XXX.found.io:9243/_node/stats)",

}

}

Once again, obviously missing something basic, which I am assuming it on the admin side of things. HTTP calls work perfectly.

Cheers,

Ivan

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [May 17, 2018, 7:25am UTC](https://discuss.elastic.co/t/configuring-watcher-with-basic-auth-and-elastic-cloud/132189/2 "2018-05-17T07:25:14Z")

</div>

Please format the watch in markdown which makes it a hundred times easier to read the next time 🙂

The watch setup looks ok to me. One thing that stands out is the fact that you try to access elasticsearch node stats but the response in the gist is showing that you connected to kibana. Was that intentional?

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [May 17, 2018, 4:09pm UTC](https://discuss.elastic.co/t/configuring-watcher-with-basic-auth-and-elastic-cloud/132189/3 "2018-05-17T16:09:10Z")

</div>

As I said, I knew it was something incredibly basic. Wrong domain. Duh. Silly copy and paste error. Walks away in shame.

My email was properly formatted when sent, it is the mailing list software that might have stripped out characters. My email client does not support markdown. 🙂

Thanks,

Ivan

---

<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 14, 2018, 4:09pm UTC](https://discuss.elastic.co/t/configuring-watcher-with-basic-auth-and-elastic-cloud/132189/4 "2018-06-14T16:09:11Z")

</div>

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