# Fluent-bit config changes to connect to xpack securitiy enabled elasticsearch running in kubernetes

**URL:** <https://discuss.elastic.co/t/fluent-bit-config-changes-to-connect-to-xpack-securitiy-enabled-elasticsearch-running-in-kubernetes/143900>\
**Category:** Elasticsearch\
**Created:** [August 10, 2018, 4:14pm UTC](https://discuss.elastic.co/t/fluent-bit-config-changes-to-connect-to-xpack-securitiy-enabled-elasticsearch-running-in-kubernetes/143900 "2018-08-10T16:14:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DStorck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dstorck/32/33811_2.png) [@DStorck](https://discuss.elastic.co/u/DStorck)\
**Post date:** [August 10, 2018, 4:14pm UTC](https://discuss.elastic.co/t/fluent-bit-config-changes-to-connect-to-xpack-securitiy-enabled-elasticsearch-running-in-kubernetes/143900/1 "2018-08-10T16:14:03Z")

</div>

I was able to set up my elasticsearch to use xpack, and the es -\> kibana connection is working just fine, but I am unsure of what config changes need to be made to fluent-bit to be able to send logs to elasticsearch. The fluent-bit docs mention two parameters for the es output plugin that are xpack related, HTTP\_User and HTTP\_Passwd, so I tried setting them to the default user and password of elastic and changeme, but so far no luck. I don't see any other info about it on the fluent-bit end so I assume there are config changes that need to occur on the elasticsearch end to get this connection enabled. Has anyone had success with this ?

---

<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:** [September 7, 2018, 4:14pm UTC](https://discuss.elastic.co/t/fluent-bit-config-changes-to-connect-to-xpack-securitiy-enabled-elasticsearch-running-in-kubernetes/143900/2 "2018-09-07T16:14:15Z")

</div>

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