DocumentationExperience Cloud KCS

Upgrade Rapid Development Environments to a new AEM release in Adobe Experience Manager as a Cloud Service

Last update: August 18, 2026

This article explains how to upgrade Rapid Development Environments in Adobe Experience Manager as a Cloud Service to the latest available AEM release. Since in-place upgrades aren’t supported, a reset is required.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS), Rapid Development Environments (RDEs)

Symptoms

A Rapid Development Environment (RDE) remains on an older AEM release and doesn’t automatically update to the latest available version. There are no specific error messages, but the environment doesn’t reflect the current AEM release after new versions are available.

Cause

Rapid Development Environments don’t support in-place upgrades to new AEM releases. The only supported method to upgrade to the latest release is to reset the environment, which removes all existing content and configurations.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Back up any required content, configurations, and test assets from each environment. This can be done by exporting packages or storing assets in source control.

  2. Ensure your AEM project builds successfully so it can be redeployed after the reset.

  3. Confirm all required packages and configurations are available for redeployment.

  4. Prepare smoke tests to validate the environment after the reset.

  5. Reset the environment using one of the following methods:

    • Using Cloud Manager:

    a. Log in to Cloud Manager for your AEM Cloud Service program.

    b. Navigate to the Environments page.

    c. Locate the target environment.

    d. Click Reset and confirm when prompted.

    • Using the AEM RDE CLI:

    a. Ensure the CLI is configured for the target environment.

    b. Run the command: aio aem rde reset

  6. Wait for the environment to restart. The environment will now be on the latest available AEM release.

  7. Verify the AEM version:

    • In Cloud Manager, check the AEM release displayed for the environment, or

    • On the Author URL, open /system/console/productinfo and confirm the release string.

  8. Redeploy your AEM project (code, configurations, dispatcher rules, as applicable) to the environment.

  9. Run smoke tests to confirm successful deployment and environment health.

If the environment fails to reset, remains on an unexpected release, or requires a version override, open a new support request with the environment details and relevant error information.

recommendation-more-help
experience-cloud-kcs-help-kbarticles