On 30 October 2026 Adobe began enforcing its security requirements for Adobe Commerce on Cloud. Cloud environments on versions 2.4.4 to 2.4.9 that still run Elasticsearch, MariaDB 10.5 or older, or RabbitMQ 3.9 or older are now out of policy. Adobe says such environments may have Admin access suspended while the storefront stays online, and/or have inbound traffic suspended, which takes the storefront offline. If you run Magento on Adobe's PaaS cloud, it's worth checking today where you stand.
Who this applies to
The policy covers Adobe Commerce on Cloud (the PaaS offering) on versions 2.4.4 through 2.4.9. Adobe's page notes that it does not apply to Adobe Commerce as a Cloud Service (the SaaS product) or to on-premises deployments. If you host Magento Open Source or Adobe Commerce yourself, nobody will switch your store off, but the same software still reaches end of support, so the checklist below is still useful.
What was due on 30 October
- Elasticsearch, any version. Move to OpenSearch: 2.19 for stores on 2.4.4 and 2.4.5, version 3 for 2.4.6 and newer.
- MariaDB / Galera 10.5 or older. Move to 10.6 or newer.
- RabbitMQ 3.9 or older. Move to 3.13 or newer.
What is due on 31 May 2027
- PHP 8.1 or older. Move to 8.2 or newer.
- MariaDB between 10.5 and 10.11. Move to 10.11 or newer.
- OpenSearch 1.x. Move to 2.19 or 3, depending on your Magento version.
- Redis 5 or older. Move to Valkey 8 or newer.
- RabbitMQ between 3.9 and 3.13. Move to 4.3 or newer.
The Magento version deadlines
Separately from the services, the policy table sets dates for the Magento version itself. Stores on 2.4.4 or 2.4.5 need to upgrade to the latest version or migrate to Adobe Commerce as a Cloud Service by 1 June 2027. Stores on 2.4.6 or 2.4.7 have until 1 June 2028. Adobe lists 2.4.8 and 2.4.9 as fully supported. Adobe's version upgrade enforcement policy adds that once extended support ends for a release line, Adobe reserves the right to decommission Cloud environments still running it, with the first enforcement date on 1 June 2027.
What to do this week
- Check what is actually running. Look at the service versions in every environment, not just production, because the requirements apply to all of them.
- Open a support ticket if anything is out of date. On Cloud, Adobe performs service upgrades for Staging and Production through a ticket, and its upgrade guide says Production changes on Pro need at least two business days' notice. Adobe's policy page asks you to contact your account team or Support as soon as possible if you can't meet a deadline.
- Test before production. Adobe recommends validating on a non-production environment first, covering at least checkout, search, cart and any custom integrations.
- Redeploy and reindex. Adobe's guide says to redeploy after a service upgrade so the change takes effect, and a search engine switch needs a full reindex.
- Plan the version upgrade now. If you're on 2.4.4 to 2.4.7, the service moves and the Magento upgrade are one project. Doing them together usually beats two rounds of testing.
Don't forget your extensions
Moving from Elasticsearch to OpenSearch, or from Redis to Valkey, changes software under every module that depends on search, caching or queues. Ask your extension vendors which versions they support before the upgrade window, not after. Claspwell syncs your catalog into its own database and searches there, so it doesn't query your OpenSearch cluster directly. It's still worth a quick check of the chat widget on staging after any upgrade, along with checkout and search.
Sources: Adobe: required actions and deadlines to secure Commerce environments, Adobe: Cloud version upgrade enforcement policy, Adobe: upgrade Commerce version on Cloud.