# Inconsistent elasticsearch input vs output plugin settings

**URL:** <https://discuss.elastic.co/t/inconsistent-elasticsearch-input-vs-output-plugin-settings/260586>\
**Category:** Logstash\
**Created:** [January 8, 2021, 10:58pm UTC](https://discuss.elastic.co/t/inconsistent-elasticsearch-input-vs-output-plugin-settings/260586 "2021-01-08T22:58:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GuillaumeN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guillaumen/32/81960_2.png) [@GuillaumeN](https://discuss.elastic.co/u/GuillaumeN)\
**Post date:** [January 8, 2021, 10:58pm UTC](https://discuss.elastic.co/t/inconsistent-elasticsearch-input-vs-output-plugin-settings/260586/1 "2021-01-08T22:58:49Z")

</div>

Hi,

The Logstash Elasticsearch output supports the "ssl\_certificate\_verification" parameter whereas the input one doesn't.

This makes it more difficult when consuming data from an Elasticsearch cluster using self-signed certificates.  
This is of course a bad design, but long story short, the corporate world doesn't abide by the technical good practices.

---

<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:** [February 5, 2021, 10:59pm UTC](https://discuss.elastic.co/t/inconsistent-elasticsearch-input-vs-output-plugin-settings/260586/2 "2021-02-05T22:59:02Z")

</div>

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