Deprecation Notice: Elasticsearch 7.10, OpenSearch 1.x, and OpenSearch 2.x
Elasticsearch 7.10, OpenSearch 1.x, and OpenSearch 2.x are all being retired
for the aws-elasticsearch service.
All service instances still running any of these versions must be upgraded,
in stages, to OpenSearch_3.7 by November 7, 2027.
Elasticsearch_7.10 was already removed from new-instance creation in
October 2026 (see the
OpenSearch 3.7 availability announcement).
This notice is about the existing instances still
running Elasticesearch 7.10, plus the planned phase-out of OpenSearch_1.x and
OpenSearch_2.x for both existing and new instances.
Who is impacted?
If you have an existing aws-elasticsearch service instance running
Elasticsearch_7.10, any OpenSearch_1.x version, or any OpenSearch_2.x
version, you are affected. Your instance continues to run today without any
action required, but it must be upgraded before the deadline below.
Already on OpenSearch_2.19? You don't need to take the March or June
2027 steps below — just complete the final upgrade to OpenSearch_3.7 before
November 7, 2027.
If you're creating a new instance today, this doesn't affect you,
new instances already default to OpenSearch_3.7 and cannot be
created on Elasticsearch 7.10 or OpenSearch_1.3. OpenSearch_2.19 can
still be requested for new instances, but is planned to be
removed from instance creation on its own date below, so new work should
target OpenSearch_3.7 now.
Important dates
| When | Existing instances | New instance creation |
|---|---|---|
| November 9, 2026 | OpenSearch_1.3 can no longer be requested for new instances. New instances must use OpenSearch 2.19 or OpenSearch 3.7. | |
| March 2027 | Target date for all instances to be off Elasticsearch 7.10 and onto OpenSearch 1.3. | |
| June 1, 2027 | Target date for all instances to be off OpenSearch 1.x and onto OpenSearch 2.19. | OpenSearch_2.19 can no longer be requested for new instances. New instances must use OpenSearch 3.7. |
| November 7, 2027 | Final deadline. All instances must be upgraded to OpenSearch_3.7. | Only OpenSearch_3.7 remains requestable (it has been the default since October 2026). |
The March and June 2027 dates are target dates for having moved off each
version. The Cloud.gov team will follow up with customers regarding any instances that haven't upgraded ahead of
each date. November 7, 2027 is the hard final deadline for every instance to
be on OpenSearch_3.7.
We strongly encourage upgrading well ahead of these dates. Each upgrade step triggers an AWS blue/green deployment and can take 30 minutes or more depending on your plan size and data volume, so plan for some amount of downtime and schedule each step during a low traffic window, don't wait until the week of the deadline to start.
Find your starting point
cf service ${SERVICE_NAME} shows your plan and last-operation status, but
not the engine version. To check the current engine version, use the
--params flag:
cf service ${SERVICE_NAME} --params
This returns current_elasticsearch_version in the output. Then jump to
the step below that matches it, you don't need to repeat earlier steps:
- Currently on
Elasticsearch_7.10? Start at Step 1. - Currently on any
OpenSearch_1.x(e.g.OpenSearch_1.3)? Start at Step 2. - Currently on any
OpenSearch_2.x(e.g.OpenSearch_2.19)? Start at Step 3.
See the aws-elasticsearch service documentation for the full list of supported versions and upgrade rules.
The upgrade path
AWS does not allow jumping directly from Elasticsearch 7.10 to OpenSearch
3.x. You'll need to move through the following versions, one cf update-service at a time, waiting for each step to finish before starting
the next.
Step 1: Elasticsearch 7.10 to OpenSearch 1.3
cf update-service ${SERVICE_NAME} \
-c '{"elasticsearchVersion": "OpenSearch_1.3"}'
Wait for this to complete (cf service ${SERVICE_NAME} shows update succeeded) before continuing.
Step 2: OpenSearch 1.3 to OpenSearch 2.19
cf update-service ${SERVICE_NAME} \
-c '{"elasticsearchVersion": "OpenSearch_2.19"}'
Wait for this step to fully complete before continuing.
Step 3: OpenSearch 2.19 to OpenSearch 3.7
cf update-service ${SERVICE_NAME} \
-c '{"elasticsearchVersion": "OpenSearch_3.7"}'
Again, wait for this step to fully complete before making any other changes to the instance.
Before you upgrade
- Test on a non-production instance first if you have one available. Each step is a real AWS migration, not a quick config change.
- Don't combine an engine version upgrade with a plan change or other
modification. Make each change as a separate
cf update-servicecall.
An index keeps a record of the engine that created it. OpenSearch 3.x will not open an index that was originally created by Elasticsearch, even after you've upgraded the domain through several versions — the indexes carried along by those upgrades are still Elasticsearch-created indexes, We encourage you to get to OpenSearch 2.x early to make new indexs made on opensearch to lessen the burden.
Before upgrading past OpenSearch 2.x, reindex any Elasticsearch-era indexes into new indexes (or restore a snapshot into new indexes, see Managing backups for how to create and restore a manual snapshot), switch your application and any aliases over to the new indexes, and delete the old ones. See the AWS OpenSearch upgrade documentation for current guidance.
If you skip this, the pre-upgrade check AWS runs will fail and your domain (AWS's term for your service instance) will stay on its current version, this is the single most common cause of a failed upgrade step, so don't skip it.
Questions
If you have any questions or concerns about this change, please contact support@cloud.gov.