Jump to content

Featured Replies

Posted

Hey All,

We are looking at possibly replacing ElasticSearch with OpenSearch and according to some topics and posts around the community, this seems to be possible. This post in particular seems to suggest that 2.0 is usable:

However, we get a notice in the Admin Panel:

Ghan-07-15-22_13:45:07.png

The same error message appeared with 2.0.1 and 2.1

However, 1.3.4 seems to work fine.

  • Author
 

What version of Invision Community are you running?

Invision Community v4.7.0

  • Author
 

I've tagged a developer to confirm if that should work here or not. Someone will be with you shortly.

Thank you.

  • Author
 

I believe we're using 1.2, which is the latest version AWS OpenSearch Service supports.

Is there any chance you've tested with any higher versions?

Our current test version attempt worked fine with 1.3.4, and it rebuilt all the indexes, but we can't seem to get 2.0.0 to work even though others in that topic mention that it should work just fine.

  • Author
 

I haven't tested with 2.x or newer, OpenSearch & Elastic Search release updates very quickly, often (previously) with breaking changes.

Thanks for the updates :).

  • 2 weeks later...
 

I believe we're using 1.2, which is the latest version AWS OpenSearch Service supports.

How to add the IAM data on AdminCP to allow OpenSearch to work with IPS Community? 

AWS does not allow open access anymore.

  • 2 weeks later...
 

How to add the IAM data on AdminCP to allow OpenSearch to work with IPS Community? 

AWS does not allow open access anymore.

If anyone is struggling with this, I have found on init.php ELASTICSEARCH_USER and ELASTICSEARCH_PASSWORD constants. So you can launch AWS OpenSearch with fine-grained access control (main user and password).

By the way, using OpenSearch 1.3 without issues.

Recently Browsing 0

  • No registered users viewing this page.