AWS OpenSearch Clone-Based Upgrades (November 2026): What Startups Need to Know

What did the vendor release?

AWS published this Amazon OpenSearch Service announcement on 10 November 2026. Clone-based upgrades let you validate a new OpenSearch version alongside your current one and cut over when you are satisfied.

OpenSearch Service copies data from your existing primary cluster to a second cluster running the new version, called the cloned cluster. While the primary cluster keeps serving your workload, you can run the same search queries on both clusters and compare performance using Amazon CloudWatch metrics.

After validation, you can cut over to the cloned cluster. If you find a problem, you can cancel before cutover.

Which startups are affected?

Clone-based upgrades are available for domains running OpenSearch 1.1 or later, or Elasticsearch 7.10.

They are available in AWS Commercial Regions where Amazon OpenSearch Service is offered, except Asia Pacific (New Zealand), Asia Pacific (Taipei), Asia Pacific (Thailand), and Mexico (Central).

Our recommendation: Check the domain version and Region before adding this feature to your upgrade plan. For a startup already planning a version upgrade, identify the search queries you want to compare. Agree on what an acceptable result looks like before starting the clone.

Adopt it or keep the existing approach?

If you keep the previous version for a retention period you choose, you can roll back to it at any time during that period.

Our recommendation: Use clone-based upgrades when you want to review a new version alongside the current version before approving the cutover. Make the decision around a specific upgrade and a written set of acceptance checks.

Our recommendation: Keep your current version in place while you decide which queries to compare, which CloudWatch metrics to review and who can approve the cutover. Assign an owner for the comparison and a separate decision point for proceeding or cancelling.

Our recommendation: Choose the retention period before cutting over if rollback is part of your plan. Write down the conditions that would trigger a rollback and who will make that call. Set a review time within that period, then decide whether to keep the new version.

Our recommendation: Give the cutover owner a short written record of the queries tested, the metrics compared and any unresolved differences. Ask for an explicit proceed or cancel decision. Investigate any unanswered questions from the comparison before approving the cutover.

What to check before enabling it?

You can start and manage a clone-based upgrade through the AWS Management Console, the AWS CLI or the OpenSearch Service APIs.

• Our recommendation: Record the exact domain, its starting version and its Region in the upgrade plan.
• Our recommendation: Prepare the same query set for both clusters. Save the comparison results and document whether they meet your acceptance checks.
• Our recommendation: Choose your management route, then review the access needed for the person or automation carrying out the upgrade.
• Our recommendation: Review the expected cost and your data-handling requirements before starting. Include any questions about validation, cutover and rollback in that review.
• Our recommendation: Record the chosen retention period and its end time. Schedule the rollback decision before that period ends.