Aiven for OpenSearch is a replacement product for Aiven for Elasticsearch. It is powered by OpenSearch, a community-driven, an open source project derived from Apache 2.0 licensed Elasticsearch 7.10.2 and Kibana 7.10.2.

In January 2021, announced a more restrictive licensing policy, starting from version 7.11, that no longer permits third parties to offer Elasticsearch as a service.

For our existing Elasticsearch customers, this means that

  • Aiven for OpenSearch is available as an upgrade path for Aiven for Elasticsearch.

  • Aiven for Elasticsearch v7.x will reach end of life (EOL) on March 23rd, 2022.

  • You can safely upgrade to OpenSearch as soon as possible, as we maintain backwards compatibility for Aiven REST APIs and service metrics until EOL.

Before you begin

Here are some key things to know before you upgrade your Elasticsearch services.

  • You can upgrade to OpenSearch without any downtime.

  • Your old Elasticsearch service will not be available after the upgrade has been completed.

  • The upgrade introduces updates to Aiven API responses and service metrics names, although we have ensured backwards compatibility until the EOL of Elasticsearch version 7.x.

  • You need to update the Aiven Terraform Provider client to atleast version 2.2.

  • Aiven for OpenSearch comes with additional plugins. For more information on the available plugins, go to this section.

  • We advise you not to update your client libraries yet if your setup is working.

    • Recently, Elastic has introduced a change where Beats and Logstash 7.13+ and client libraries now check that they are connecting to an actual Elasticsearch cluster to ensure that the full set of expected capabilities are available.

    • If these capabilities do not exist in future releases, Beats, Logstash, and client libraries are expected to fail early instead of failing or prompting issues at runtime. (source: News from Elastic on June 12th)

  • OpenSearch does not include Logstash and Beats. See this documentation to check which versions of Logstash and Beats work with OpenSearch.

In addition, we recommend that you check the following OpenSearch resources for more information:

Our recommendation

We recommend that you test the change to OpenSearch both by creating a fork of your Elasticsearch service and upgrading that to OpenSearch and by creating a fork directly to OpenSearch. This approach gives you a better view of the changes and a smoother transition to Aiven for OpenSearch.

(1) Test the upgrade path with a database fork

We recommend creating a fork of your Aiven for Elasticsearch service and upgrading that fork to test the changes before you apply the upgrade to the actual service.

When testing the upgrade, consider running at least the following tests:

  • Run a set of queries both before and after the upgrade and check that the results are consistent in both cases.

  • Check that the OpenSearch dashboard works as expected.

  • Check that your configuration options are maintained and work as expected.

  • Check that the plugins you are using work as expected.

(2) Fork your Elasticsearch service to a new OpenSearch service

This is your clean test bed to discover the changes in the Aiven APIs and service metrics with a pure OpenSearch service. We migrate the data for you.

As we ensure backwards compatibility in Aiven APIs and service metrics only until EOL of Elasticsearch version 7.x on our platform, this allows you to discover the changes required in your client applications and monitoring dashboards so that you can update them well before EOL.

Go to the section on how to fork your service to OpenSearch for detailed instructions.

Upgrade your Elasticsearch service

Once you have tested the upgraded path with a fork and forked your Elasticsearch service to OpenSearch, you can upgrade the service:

  1. Log in to the Aiven web console and select your service.

  2. On the service overview page, scroll down to Elasticsearch version and click Upgrade Elasticsearch.

  3. Click Upgrade to confirm.
    This starts the upgrade process.

Note: The Kibana dashboard will be restarted to complete the upgrade to OpenSearch.

After a successful upgrade:

  • The service type displayed in the console is now OpenSearch, and there is also an update to the service logo.

  • Kibana is now OpenSearch Dashboards.

  • Your service name remains the same.

  • The API responses include both elasticsearch and opensearch fields.

  • The metrics that the service produces are duplicated both with elasticsearch_ and es_ prefixes, and with the opensearch_ prefix.

EOL of Elasticsearch v7.x

Aiven for Elasticsearch v7.x will reach end of life (EOL) on March 23rd, 2022.

Upon EOL, Aiven will

  • automatically upgrade all running Aiven for Elasticsearch services to Aiven for OpenSearch

  • powered-off Aiven for Elasticsearch services will no longer be accessible and their backups will be deleted

Read more about our EOL policy here.

How to fork your Aiven service to OpenSearch

  1. Log in to the Aiven web console and select your service.

  2. Scroll down to Fork Database and click New database fork.

  3. Select OpenSearch as the service type.

  4. Enter the details for the forked service and select the cloud provider, region, and service plan.

  5. Click Create fork.

Supported plugins in Aiven for OpenSearch

Aiven for OpenSearch includes the standard set of plugins that match those included in Aiven for Elasticsearch.

There are also several new OpenSearch plugins that are included in Aiven for OpenSearch services:

Did this answer your question?