# Curator - suppress urllib3 SSL warning

**URL:** https://discuss.elastic.co/t/curator-suppress-urllib3-ssl-warning/169239
**Category:** Elasticsearch
**Tags:** curator
**Created:** [February 20, 2019, 3:22pm UTC](https://discuss.elastic.co/t/curator-suppress-urllib3-ssl-warning/169239 "2019-02-20T15:22:47Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Jasper\_Nygaard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasper_nygaard/32/4238_2.png) [@Jasper\_Nygaard](https://discuss.elastic.co/u/Jasper_Nygaard)
#### Post date: [February 20, 2019, 3:22pm UTC](https://discuss.elastic.co/t/curator-suppress-urllib3-ssl-warning/169239/1 "2019-02-20T15:22:47Z")

</div>

Hi

Got an ES cluster with self signed certificates and using Curator to do maintenance. Can anyone either:

- tell me where I can suppress Unverified HTTPS request warning from urllib3 - I'm running Curator on Windows and haven't been able to figure out where to apply urllib3.disable\_warnings(). Not really a python dev.
- point me to an example on how to validate SSL with self signed certificate on Windows

Thanks

---

<div class="post-metadata">

### Author: ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)
#### Post date: [February 21, 2019, 3:47am UTC](https://discuss.elastic.co/t/curator-suppress-urllib3-ssl-warning/169239/2 "2019-02-21T03:47:18Z")

</div>

How are your nodes secured right now? If you’re connecting via SSL with self-signed certificates, how were they generated?

A full discussion of generating and using SSL/TLS certificates is beyond the scope of this topic. You would be well-served to follow the instructions in [this guide](https://www.elastic.co/guide/en/elasticsearch/reference/6.6/configuring-tls.html#tls-http) for securing Elasticsearch client traffic.

If you have `xpack.ssl.verification_mode` set to `full`, then Curator will require the [CA certificate](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.6/configfile.html#certificate), as well as its own [public](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.6/configfile.html#client_cert) and [private](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/configfile.html#client_key) keys. If you have `xpack.ssl.verification_mode` set to `certificate`, then Curator should only need the [CA certificate](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.6/configfile.html#certificate).

---

<div class="post-metadata">

### Author: ![Jasper\_Nygaard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasper_nygaard/32/4238_2.png) [@Jasper\_Nygaard](https://discuss.elastic.co/u/Jasper_Nygaard)
#### Post date: [February 21, 2019, 8:02am UTC](https://discuss.elastic.co/t/curator-suppress-urllib3-ssl-warning/169239/3 "2019-02-21T08:02:08Z")

</div>

Hi Aaron,

Thank you for your reply.  
The cluster is using SearchGuard with self issued SSL/TLS certificates. Managed to solve the issue, and route all requests from Curator by our NLB with a valid SSL certificate.

However, for future readers and users of Curator, it might be nice to know how either to disable the urllib3 warnings for the Windows binaries or how to setup Curator with a self issued ca root certificate with a Windows file system.

---

<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: [March 21, 2019, 8:02am UTC](https://discuss.elastic.co/t/curator-suppress-urllib3-ssl-warning/169239/4 "2019-03-21T08:02:20Z")

</div>

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