Magento Elasticsearch OpenSearch compatibility is version-coupled: the supported engine depends on your exact Adobe Commerce patch and whether you run Cloud or on-premises. This guide covers the Adobe Commerce OpenSearch migration path, why Magento search not working after cutover is usually configuration or indexing, not a broken cluster, and how to avoid Magento Elasticsearch error blank-result failures.
Check the version matrix first
Adobe's system requirements are the source of truth.
| Commerce release | Search engine (Aug 2026) | Implication |
|---|---|---|
| 2.4.9 | OpenSearch 3 | OpenSearch is the native path |
| 2.4.8-p5 | OpenSearch 3; on-prem also lists Elasticsearch 8 | Deployment model matters |
| 2.4.7-p10 | OpenSearch 2.19 / 3; on-prem lists Elasticsearch 8 | Patch level changes matrix |
| 2.4.6-p15 | OpenSearch 2.19 / 3; ES not listed | Old “2.4.6 + ES 7” diagrams are stale |
Elasticsearch 7.17 end of support was 15 January 2026. Capture: edition + patch, Cloud vs on-prem, engine version, index prefix, modules, catalogue size, indexer duration, peak search latency.
Cloud and on-premises are not the same
Adobe Commerce on cloud uses OpenSearch for supported modern releases. Elasticsearch 7+ is not supported there.
On-premises allows only combinations in Adobe's matrix for your exact patch. Do not copy a Cloud matrix to on-prem or vice versa.
Five-minute audit before cutover
- Record exact Commerce patch and deployment model
- Run
bin/magento config:show catalog/search/engine - Capture search hostname, index prefix, TLS model (no secrets in audit)
- Check
catalogsearch_fulltextindexer status and last full reindex duration - Inventory search modules, Live Search, custom analyzers
- Pull Adobe's current matrix for your patch
- Build revenue-driving query set before changing engine
Magento search not working: symptom map
| Symptom | Likely cause | First check |
|---|---|---|
| Magento elasticsearch error / connection failure | Host/auth/TLS, env lock | Commerce logs + catalog/search/engine |
| Zero products after cutover | Index not built, wrong prefix | Index count + indexer status |
| Stale results | Indexer backlog | bin/magento indexer:status, cron/queue |
| Slow store during migration | Full reindex contention | DB + search CPU, latency |
A green cluster does not prove Commerce search is healthy.
Safe cutover sequence (reference architecture)
Build target OpenSearch/Elasticsearch in required Region → Reindex catalogsearch_fulltext → Replay revenue queries → Switch engine config → Smoke test search/category/PDP → Keep old endpoint for rollback.
For Australian merchants, host cluster, snapshots and reindex workers in ap-southeast-2 or ap-southeast-4. See Sydney & Melbourne residency.
Note: Elastic App Search is retired, different from native catalogue search. See Enterprise Search migration.
Our ecommerce OpenSearch case is a UAE reference, not an Australian merchant claim.
Readiness checklist
- Verify Commerce patch against Adobe's current search matrix
- Complete production-scale
catalogsearch_fulltextreindex on target - Replay top revenue queries and category paths
- Define rollback triggers and old-engine retention window
- Validate residency Region for search cluster and snapshots
- Schedule cutover outside peak trading if possible
Limitations
Reference architecture, not legal or Adobe support advice. Re-check Adobe requirements before production. No invented Australian merchant case studies.
Sources: Adobe Commerce system requirements, verified 8 August 2026.
Next step: Scope Commerce search cutover · EOL hub · OpenSearch cutover checklist
