Using Zeebe with OpenSearch instead of Elastic?

Thomas Heinrichs: Hi Cloud folk :wave:
Has anyone of you made some experiences using AWS OpenSearch instead of elastic? At least in the Forum I do find multiple unanswered questions about this :thinking_face:

Nicolas: It’s probably difficult to use the default exporter for this due to how AWS authentication works by signing every request (at least last time I checked). There’s no real built in way with the Zeebe exporter to do this - your best bet for now would be to extend the exporter yourself and implement the authentication required.

Thomas Heinrichs: Thanks! That is an awesome answer. :slightly_smiling_face:

Note: This post was generated by Slack Archivist from a conversation in the Zeebe Slack, a source of valuable discussions on Zeebe (get an invite). Someone in the Slack thought this was worth sharing!

If this post answered a question for you, hit the Like button - we use that to assess which posts to put into docs.

1 Like

We have many large customers who use and/or prefer AWS OpenSearch, and open source OpenSearch. We prefer the licensing structure of OpenSearch, and would like to be able to use OpenSearch. We have to use authentication and encrypted communication with OpenSearch.

We would appreciate it very much if you could also add support for AWS and open source OpenSearch in the ElasticsearchExporter. It seems like this could simply be a feature in the exporter.

Hi @VolueOle

You could fork the ES exporter and patch it to use AWS OpenSearch, then contribute the patch back. That would be the fastest way to get it done.