# Logstash output to ES via ssl **URL:** \ **Category:** Logstash\ **Created:** [January 28, 2016, 6:16pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404 "2016-01-28T18:16:04Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mnhan](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mnhan](https://discuss.elastic.co/u/mnhan)\ **Post date:** [January 28, 2016, 6:16pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404/1 "2016-01-28T18:16:04Z")
Hi, Are there docs/example of using the ssl options in the es output plugin? I'm setting LS and ES on different hosts. I want to encrypt output from LS to ES. I can't seem to find an docs on using using ssl from LS to ES via the ES output plugin. Is there a better output plugin to use for ssl between LS and ES? thanks, MIke ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 29, 2016, 1:56am UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404/2 "2016-01-29T01:56:42Z")
The LS docs do go into setting up SSL certs - [https://www.elastic.co/guide/en/logstash/2.1/plugins-outputs-elasticsearch.html](https://www.elastic.co/guide/en/logstash/2.1/plugins-outputs-elasticsearch.html) What specifically are you missing there? ---
**Author:** ![mnhan](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mnhan](https://discuss.elastic.co/u/mnhan)\ **Post date:** [January 29, 2016, 2:27am UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404/3 "2016-01-29T02:27:51Z")
Maybe an example setup would help those of us new to ELKS on how its suppose to be set up. When I set ssl = true and cacert to a certificate file for the es output plugin. logstash get an error connecting to ES via https. straight http without ssl works fine on the es output plugin. Maybe I'm not understanding how the es output plugin works to communicate with ES via ssl. What am i mis-configuring or haven't configured on ES that needs to be there be to accept the https connection from logstash es output plugin. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 29, 2016, 2:56am UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404/4 "2016-01-29T02:56:29Z")
What's the error? How did you setup SSL on the ES end? ---
**Author:** ![mnhan](https://avatars.discourse-cdn.com/v4/letter/m/8baadc/32.png) [@mnhan](https://discuss.elastic.co/u/mnhan)\ **Post date:** [January 29, 2016, 3:24pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404/5 "2016-01-29T15:24:03Z")
I believe that is the crux of the issue. filebeat to logstash via ssl only needed certificates and the configuration was very straight forward. Logstash to ES on the other hand isn't as straight forward. If one does not use shield, what are the option to configure tls/ssl on ES for logstash to connect to ES via ssl? I think that's what I'm confuse at. I don't see any ssl configuration in the default ES yaml or any do doc to add ssl to that yaml unless I missed it. I see the tls/ssl guide, but it very shield centric. Searching the web gives me nginx/apache proxy option. Are there any ES option without shield not requiring web frontend proxies? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 29, 2016, 8:58pm UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404/6 "2016-01-29T20:58:36Z")
Without Shield for SSL, you need to roll your own. ---
**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, 5:13am UTC](https://discuss.elastic.co/t/logstash-output-to-es-via-ssl/40404/7 "2017-07-06T05:13:43Z")