iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
For Adobe Commerce 2.4.8 and later, use OpenSearch: Adobe no longer supports Elasticsearch on those releases. On earlier releases, the supported choice depends on the exact Commerce version and patch, and Cloud and on-premises deployments can have different compatibility rules. Check the release-specific requirements before selecting or upgrading an engine.
Start with your Adobe Commerce version
“Magento 2” is still a common name for the platform, but Adobe’s current documentation calls it Adobe Commerce. The engine decision is governed by your exact Commerce release and patch, not by the generic Magento 2 label.
Adobe’s System Requirements lists tested software combinations by release and says configurations outside its tables are not validated or supported. For example, its current latest-release table lists OpenSearch 3 for Commerce 2.4.9. That is a release-specific compatibility entry, not a general recommendation to pair every Commerce version with OpenSearch 3.
| Commerce release or deployment | What Adobe’s guidance establishes | What to check |
|---|---|---|
| 2.4.8 and later | Elasticsearch is no longer supported; Adobe directs users to OpenSearch. | Use the System Requirements table for the precise OpenSearch version supported by your release and patch. |
| 2.4.9 | Adobe’s current requirements table lists OpenSearch 3. | Confirm the full release and patch combination in the current table. |
| Earlier supported releases | Support varies across release lines and patches; older lines can have different Elasticsearch or OpenSearch entries. | Do not carry a version or configuration label forward from another release. Check the matching requirements and upgrade guidance. |
| Adobe Commerce on Cloud infrastructure | Adobe says Elasticsearch 7 and later is not supported on Cloud and directs Commerce 2.4.4 and later users to its OpenSearch service. | Check the service version available for your Cloud environment and PHP client compatibility. |
Adobe’s upgrade prerequisites specifically say Commerce 2.4.8 and later no longer support Elasticsearch and direct users to OpenSearch: Upgrade prerequisites. Adobe also notes that from Commerce 2.4.6 onward the configuration engine value for OpenSearch is opensearch. Older supported releases may require different labels or patch levels, so use the instructions for the target release.
#1 Best Overall
Cloud and on-premises support are not interchangeable
Adobe Commerce on Cloud infrastructure
Adobe’s Cloud OpenSearch service documentation says Elasticsearch 7 and later is not supported on Cloud and directs Commerce 2.4.4 and later users to the OpenSearch service. Cloud service support reflects versions tested and deployed on Adobe’s Cloud infrastructure; it can differ from on-premises compatibility.
When setting up or upgrading the Cloud service, verify that the deployed OpenSearch version is compatible with the OpenSearch PHP client used by the application. Adobe also documents that production or staging service configuration changes may require an Adobe Support ticket, depending on the environment.
On-premises installations
For an on-premises deployment, use the System Requirements entry for your precise Commerce release and patch. A version listed for on-premises use does not establish that the same version is available or supported as a Cloud service, and Cloud guidance should not be treated as the on-premises compatibility table.
What the names mean—and what they do not
Adobe describes OpenSearch as an open-source fork of Elasticsearch 7.10.2, following Elasticsearch’s licensing changes. That history explains their relationship, but it does not mean every major version, client, plugin, or operational detail is interchangeable. For a Commerce deployment, the applicable release and environment support matrix is the deciding reference: Adobe Commerce System Requirements.
Rank #3
Configuration checks when setting up or changing engines
After choosing an engine supported by your release, verify the connection settings in Commerce’s configuration. Adobe’s search-engine configuration guide covers the engine selection and connection details.
- Engine selection: Choose the value required by the target Commerce release. From 2.4.6 onward, Adobe specifies
opensearchfor OpenSearch. - Hostname and port: Enter the server host and port that apply to your deployment. Adobe gives 9200 as the default port; verify the actual service endpoint rather than assuming the default.
- Index prefix: Adobe gives
magento2as the default. Use a unique prefix if multiple Commerce installations share one engine instance, so their indexes remain distinct. - Authentication: Set HTTP authentication details if the service requires them.
- Connection test: Run the configuration’s connection test and resolve connectivity or credential errors before relying on the service.
For Cloud deployments, follow the Cloud service setup path as well as the application configuration steps, and verify PHP client compatibility with the deployed service version.
Engine choice does not solve every search requirement
Do not choose OpenSearch on the assumption that it provides suffix search out of the box. Adobe says neither Elasticsearch nor OpenSearch has built-in suffix-search support. For example, searching only the ending portion of a SKU may not return the expected result. If suffix matching is required, treat it as a separate search-behavior requirement and assess an appropriate implementation rather than assuming an engine switch will add it. See Adobe’s explanation of search-engine upgrade prerequisites.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A practical selection checklist
- Identify the exact Adobe Commerce version and patch you run or plan to install.
- Open Adobe’s System Requirements and confirm the engine version for that release.
- If the target is Commerce 2.4.8 or later, plan on OpenSearch because Elasticsearch is no longer supported.
- For Cloud, confirm the OpenSearch service version available to your environment and compatibility with the application’s PHP client.
- Configure the engine selection, hostname, port, index prefix, and authentication, then run the connection test.
- List search behaviors such as suffix matching separately; neither engine provides that capability out of the box according to Adobe.
What Adobe’s compatibility evidence does not tell you
Adobe’s published material establishes compatibility by Commerce release and deployment type. It does not establish a universal winner for search speed, relevance, or total operating cost. Those outcomes depend on the application, configuration, data, workload, and infrastructure; do not infer a performance advantage from the compatibility tables alone.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
