AWS OpenSearch and Zamad

[v1r]

Hi everyone,

I’m currently using the Dockerized version of Zammad and I’m trying to connect it to OpenSearch (an Elasticsearch-compatible service on AWS). However, I’m having trouble figuring out where to input the OpenSearch credentials in the docker-compose .env file. I tried ELASTICSEARCH_USER and ELASTICSEARCH_PASSWORD but no luck.

Could anyone point me in the right direction or share some guidance on how to configure this?

Thank you!

[javlin]

Hi,
If you are OK with configuring this on the running zammad container, you can open rails console on your zammad instance and run these commands

bundle exec rails r “Setting.set(‘es_url’, ‘your-opensearch-https-url’)”

bundle exec rails r “Setting.set(‘es_user’, ‘your-opensearch-user’)”

bundle exec rails r “Setting.set(‘es_password’, ‘your-opensearch-password’)”

#Rebuild index

rake zammad:searchindex:rebuild

Hope this helps!

[MrGeneration]

@javlin’s approach is not update safe, it will be overwritten with a stack restart and thus be a pain to maintain.

Note that opensearch officially has no support from Zammad:
https://docs.zammad.org/en/latest/prerequisites/software.html#elasticsearch-optional

This might help you though:

Zammad 6: Opensearch instead of Elasticsearch - Zammad 6 refuses

I have tried to run Zammad 6 with OpenSearch, so far un successfully. Configured OpenSearch 2.9.0 (also tested 2.8.0) and Zammad 6.0.0-1690378408.79860681.bookworm. I configured OpenSearch to pretend it is ElasticSearch, according to this post: $ grep compatibility /etc/opensearch/opensearch.yml compatibility.override_main_response_version: true OpenSearch is up and available. But if I try to have Zammad talk to OpenSearch, Zammad aborts: $ zammad run rake zammad:searchindex:rebuild rake ab…

[javlin]

I agree with @MrGeneration regarding the approach I suggested - It will be valid only for the particular container life (I had mentioned that rider though!)