# Elastic TLS: "xpack.security.http.ssl.enabled: true" vs proxy

**URL:** <https://discuss.elastic.co/t/elastic-tls-xpack-security-http-ssl-enabled-true-vs-proxy/267197>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-security\
**Created:** [March 14, 2021, 4:39pm UTC](https://discuss.elastic.co/t/elastic-tls-xpack-security-http-ssl-enabled-true-vs-proxy/267197 "2021-03-14T16:39:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![raulk89](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@raulk89](https://discuss.elastic.co/u/raulk89)\
**Post date:** [March 14, 2021, 4:39pm UTC](https://discuss.elastic.co/t/elastic-tls-xpack-security-http-ssl-enabled-true-vs-proxy/267197/1 "2021-03-14T16:39:43Z")

</div>

Hi

Elastic 7.11.1

Planning on configuring TLS for elasticsearch port 9200  
I was wondering, is there a difference, whether I configure TLS with:

- elasticsearch.yml: xpack.security.http.ssl.enabled: true
- or via apache/nginx proxy (http:9200 -\> https:443)

Is there any downsides when doing it via proxy or vice versa..?

My goal would be that the authentication passwords and all the http requests must be encrypted \<-- In my opinion this can be achieved via proxy also.

Thanks.

Regards  
Raul

---

<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 11, 2021, 4:39pm UTC](https://discuss.elastic.co/t/elastic-tls-xpack-security-http-ssl-enabled-true-vs-proxy/267197/2 "2021-04-11T16:39:55Z")

</div>

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