# SSL reverse proxy in front of api on a cluster

**URL:** <https://discuss.elastic.co/t/ssl-reverse-proxy-in-front-of-api-on-a-cluster/20415>\
**Category:** Elasticsearch\
**Created:** [October 24, 2014, 8:22am UTC](https://discuss.elastic.co/t/ssl-reverse-proxy-in-front-of-api-on-a-cluster/20415 "2014-10-24T08:22:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Bennet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_bennet/32/1162_2.png) [@James\_Bennet](https://discuss.elastic.co/u/James_Bennet)\
**Post date:** [October 24, 2014, 8:22am UTC](https://discuss.elastic.co/t/ssl-reverse-proxy-in-front-of-api-on-a-cluster/20415/1 "2014-10-24T08:22:32Z")

</div>

Hello.

Right now ive got an ES cluster, and I would like it to use SSL for  
security reasons (nodes located across the internet from one another,  
remote api requests) . I have considered using nginx as a reverse proxy (I  
would also like to do HTTP basic auth) - But im not quite sure how that  
would work. I think this may be nontrivial as I cant just set network.host  
to localhost and then put an ssl proxy from https:whatever:9200 to  
http:localhost:9200, can I? As I think that will break the clustering?

Has anyone done such a thing? I see its possible for single node instances,  
but what about clusters? - Or am I confused, and the 9200 is only the  
remote API and it only uses 9300-9400 for clustering?

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/cf5d4315-58e9-48cb-85f0-a8f2033e61cf%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/cf5d4315-58e9-48cb-85f0-a8f2033e61cf%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![James\_Bennet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james_bennet/32/1162_2.png) [@James\_Bennet](https://discuss.elastic.co/u/James_Bennet)\
**Post date:** [October 24, 2014, 8:23am UTC](https://discuss.elastic.co/t/ssl-reverse-proxy-in-front-of-api-on-a-cluster/20415/2 "2014-10-24T08:23:37Z")

</div>

The inter-cluster comms would still need secured too, I guess, though it is  
behind a firewall, so basic auth is less of an issue.

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/bf1f4b39-3906-4009-b282-011f73895f9d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/bf1f4b39-3906-4009-b282-011f73895f9d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:54am UTC](https://discuss.elastic.co/t/ssl-reverse-proxy-in-front-of-api-on-a-cluster/20415/3 "2017-07-06T00:54:01Z")

</div>


