OpenSearchCon India 2026

We migrated ~1,500 OpenSearch nodes across 7 clusters in 5 regions from Intel to AWS Graviton 4, upgrading from OpenSearch 2.13 to 3.4 and JVM 17 to 21 along the way. We saw 2x indexing throughput and ~30% cost savings. We want to share the benchmarking data, compare migration strategies (inline upgrade, snapshot-restore, and why CCS didn't work), and push more teams toward Graviton.

A practical guide to evaluating and executing a Graviton migration at scale — covering instance type benchmarking (i4i/i4g/i7i/i8g), migration strategy trade-offs (inline upgrade is fast but risky, snapshot-restore is safe but needs parallel infrastructure, CCS doesn't work across major versions), production validation steps, and the real performance and cost numbers from 1,500 nodes in production.

Large-scale Graviton migration data for OpenSearch is scarce. By sharing production numbers from 7 clusters across 5 regions — including what didn't work — we want to de-risk Graviton adoption for the community. The 2x throughput and 30% cost reduction we're seeing should motivate more teams to make the move, and our migration playbook gives them a concrete path to follow.