How to upgrade Managed OpenSearch to a newer version

Published on: November 20, 2026

New OpenSearch versions bring new features and fixes, while older versions are eventually retired. Some versions of UpCloud Managed OpenSearch have an end-of-life date, which the API lists for each version. Upgrading moves your service to a newer version, and the service keeps serving requests while the upgrade runs.

This guide shows how to upgrade a Managed OpenSearch service in the Control Panel or with the UpCloud API, and how to check that the upgrade has finished.

Before you start

You need:

Before you upgrade, check that your applications, client libraries and tools support the new version, because a new major version of OpenSearch can remove settings and features that older versions supported. The OpenSearch Breaking changes page lists what changes in each version.

How upgrades work

You can upgrade straight to any newer version, so a service on 2.19 can go directly to 3.6. Choose the newest version that your applications support. OpenSearch 3.8 is a preview version, so for production, upgrade to OpenSearch 3.6, the newest version that isn't a preview. An upgrade can't be undone: you can't go back to the earlier version afterwards.

The service keeps running during the upgrade, so your applications can keep reading and writing through the same hostname and port. Behind that hostname, the service first adds a full set of new nodes running the new version and copies your data to them. It then removes the old nodes one at a time.

The upgrade keeps your indices and documents, your users and their access rules, the allowed IP addresses and the service's properties. The nodes, however, are new servers with new names and new IP addresses. Connect to the service by its hostname rather than by the IP addresses of its nodes, so that your applications find the new nodes.

Upgrade the service

  1. Go to Databases and open the Managed OpenSearch service.
  2. On the Overview tab, under Details, Type shows the service's current version. Click Upgrade next to it.
  3. Under Version, select the version to upgrade to, and click Upgrade.
The Upgrade database version dialog with OpenSearch 3.6 selected

The service's status changes to Rebalancing… while the upgrade runs. Under Nodes, the new nodes appear as Setting up… and then Syncing data…. The old nodes show Leaving… as they're removed. The upgrade is done when the status is back to Started and Type shows the new version.

Check that the upgrade finished

Once the upgrade is done, list the service's nodes and their versions to check that every node runs the new version:

curl --user upadmin "https://<hostname>:<port>/_cat/nodes?v&h=name,version"
Output
Enter host password for user 'upadmin':
name              version
products-search-5 3.6.0
products-search-6 3.6.0
products-search-4 3.6.0

Then check that your indices are all there and that their health is green:

curl --user upadmin "https://<hostname>:<port>/_cat/indices?v&h=health,index,docs.count&s=index"
Output
Enter host password for user 'upadmin':
health index                docs.count
green  .kibana_1                     0
green  .kibana_2                     0
green  .opendistro_security         10
green  .plugins-ml-config            1
green  products                     10

The indices whose names start with a dot are OpenSearch's own.

Next steps

Contributed by: Samir Haliru

Can't find what you're looking for?

For more help you can contact our awesome 24/7 support team

Contact Support