# Output filter, Elasticsearch & cloud instance

**URL:** <https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376>\
**Category:** Logstash\
**Created:** [July 22, 2022, 9:37am UTC](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376 "2022-07-22T09:37:58Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![Mark\_Rodman](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Mark\_Rodman](https://discuss.elastic.co/u/Mark_Rodman)\
**Post date:** [July 22, 2022, 9:54pm UTC](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376/21 "2022-07-22T21:54:01Z")

</div>

it's working.  
So it looks like it was my super complex password.  
I've double checked in the config numerous times, and it works with curl. But there seems to be an issue with the complexity in logstash. A bug possibly?  
The password was  
`£gm46h45eg4wffvwefvsrfgbhtnjymrek675j64w5h3gw4refdscxz324fre£$%^YTvid`  
of course I won't be using it again,

Can you test it?

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [July 22, 2022, 9:56pm UTC](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376/22 "2022-07-22T21:56:30Z")

</div>

Interesting... Perhaps later I will test... I have seen some edge cases like this ... in some other non logstash use case...  
thinking it may be the `£`

---

<div class="post-metadata">

**Author:** ![Mark\_Rodman](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Mark\_Rodman](https://discuss.elastic.co/u/Mark_Rodman)\
**Post date:** [July 22, 2022, 9:57pm UTC](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376/23 "2022-07-22T21:57:31Z")

</div>

thanks for the help!  
Just glad it's sorted, need to find a secure password now that Logstash is happy with 😃

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [July 23, 2022, 12:18am UTC](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376/24 "2022-07-23T00:18:29Z")

</div>

I duplicated the issue with the `£`... seeing if I get any insight on valid password character sets...  
Failed with leading or trailing (and I assume anywhere in the middle)

---

<div class="post-metadata">

**Author:** ![Mark\_Rodman](https://avatars.discourse-cdn.com/v4/letter/m/57b2e6/32.png) [@Mark\_Rodman](https://discuss.elastic.co/u/Mark_Rodman)\
**Post date:** [July 23, 2022, 9:51am UTC](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376/25 "2022-07-23T09:51:15Z")

</div>

thanks for following up.  
Interesting finding.

---

<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:** [August 20, 2022, 9:51am UTC](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376/26 "2022-08-20T09:51:21Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/output-filter-elasticsearch-cloud-instance/310376.md?page=1)