Output filter, Elasticsearch & cloud instance

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?

1 Like

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 £

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

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)

thanks for following up.
Interesting finding.

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