Elasticsearch and OpenSearch as a Magento 2.4 requirement

Adobe Commerce and Magento Open Source need a compatible search engine to index the catalogue. The supported product and its version depend on each Magento version: current branches may require OpenSearch or a specific version of Elasticsearch.

Before installing or upgrading, check the official Adobe Commerce requirements matrix for the exact version you are going to deploy. Do not reuse another branch's matrix or simply pick the latest version of the search engine.

Safe installation or upgrade

1. Confirm the matrix for Magento, PHP, Composer, database, OpenSearch or Elasticsearch and other dependencies.
2. Provision the compatible engine on a VPS, dedicated server or managed service with enough resources.
3. Restrict network access, enable authentication and TLS, store the credentials outside the webroot and set up backups and monitoring.
4. Test the connection, indexing, search, catalogue and performance in staging.
5. Run the upgrade without skipping requirements and keep a verified rollback plan.

If your hosting service cannot run the required engine, use a compatible managed service or migrate the application to suitable infrastructure.

Do not skip the requirements

Do not disable the core search modules to force the installation or skip Composer's requirement checks. These shortcuts can leave you with a shop that looks installed but has no working search, incompatible dependencies or no valid support path.

Alternative engines are only valid when the documentation for the Magento version and the extension vendor declare them compatible and maintained. Install them with Composer constraints satisfied and validate them in staging; do not replace a core requirement blindly.

Details to confirm before ordering the engine

Ask for the exact product and version, a private or restricted endpoint, authentication, TLS and available capacity. Check that the application's hosting can connect to that destination and that the integration supports its parameters. Having PHP and MySQL does not mean the plan includes an OpenSearch or Elasticsearch process.

After setting up the connection, test both indexing and public searches, filters and catalogue changes. A successful connection test button does not prove that the indexes are complete or that there is enough memory for the catalogue.

If an upgrade fails, keep the error and the version matrix before changing dependencies. A rollback may require restoring code and data together; reinstalling an earlier version of the engine does not by itself revert the shop's changes.