Manage Environments

Last update: June 11, 2025
  • Applies to:
  • Experience Manager as a Cloud Service

CREATED FOR:

  • Admin
  • Developer

Learn about the types of environments that you can create and how to create them for your Cloud Manager project.

Environment types

A user with the requisite permissions can create the following environment types (within the bounds of what is available to the specific tenant).

Environment typeDescription
Production + StageThe production and staging environments are available as a pair and are used for production and testing purposes, respectively. Conduct performance and security tests on stage environment. It has the same sizing as production.
DevelopmentA development environment can be created for development and testing purposes and can be associated with non-production pipelines only. Development environments do not have the same sizing as stage and production, and should not be used to conduct performance and security tests.
Rapid DevelopmentA Rapid Development Environment (RDE) lets developers quickly deploy and review changes. This ability reduces the time needed to test features that have already been validated in a local development environment. See the rapid development environment documentation for details about how to use an RDE.
Specialized Testing EnvironmentSpecialized Testing Environments provide a dedicated space to validate features under near-production conditions, ideal for stress testing and advanced pre-deployment checks. See Add a Specialized Testing Environment
NOTE
The Specialized Testing Environment feature is currently available only through the private beta program. To sign up for the private beta, see Specialized Testing Environment.

The capabilities of individual environments depend on the solutions that are enabled in the program of the environment.

NOTE
Production and staging environments are only created as a pair. You cannot create a production-only or a staging-only environment.

Add an environment

To add or edit an environment, a user must be a member of the Business Owner role.

To add an environment:

  1. Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.

  2. On the My Programs console, click the program for which you want to add an environment.

  3. Do one of the following:

    If the Add Environment option is dimmed (disabled), it may be due to a lack of permissions or dependent on the licensed resources.

    • On the My Programs console, on the Environments card, click Add Environment.

    Environments card

    • On the left side panel, click Data icon Environments, then on the Environments page, near the upper-right corner, click Add Environment.

      Environments tab

  4. In the Add environment dialog box, do the following:

    • Select an environment type. The number of available/used environments is displayed in parentheses behind the environment type name.
    • Provide an environment Name. The environment name cannot be changed after the environment is created.
    • Provide an optional Description for the environment.
    • If you are adding a Production + Stage environment, you must provide an environment name and description for both your production and staging environments.
    • Select a Primary region from the drop-down. The primary region cannot be changed after creation. Also, depending on your available entitlements, you may be able to configure multiple regions.

    Add environment dialog

  5. Click Save.

The Overview page now displays your new environment in the Environments card. You can now set up pipelines for your new environment.

Multiple publish regions

A user with the Business Owner role can configure production and staging environments to include up to three additional publish regions in addition to the primary region. Additional publish regions can improve availability. See the Additional Publish Regions documentation for more details.

TIP
You can use the Cloud Manager API to query a current list of available regions.

Add multiple publish regions to a new environment

When you add an environment, you can elect to configure additional regions in addition to the primary region.

  1. Select the Primary region.
    • The primary region cannot be changed after environment creation.
  2. Select the option Add additional publish regions and a new Additional publish regions option drop-down appears.
  3. In the Additional publish regions drop-down, select an extra region.
  4. The region selected is added below the drop-down to indicate its selection.
    • Select the X next to the selected region so you can de-select it.
  5. Select another region from the Additional publish regions drop-down to add another region.
  6. Select Save when you are ready to create your environment.

Selecting multiple regions

The selected regions apply to both production and staging environments.

If you do not specify any additional regions, you can do so later after the environments are created.

If you want to provision advanced networking for the program, it is recommended that this provisioning is done before adding additional publish regions to the environments by using the Cloud Manager API. Otherwise, the additional publish regions’ traffic goes through the primary region’s proxy.

Edit multiple publish regions

If you did not specify any additional regions initially, you can do so after the environment is created and you have the necessary entitlements.

You can also remove additional publish regions. However, you can only add or only remove regions in one transaction. If you must add one region and remove one region, first add, save your change, and then remove (or conversely).

  1. From the Program Overview console of your program, click More icon for your production environment and select Edit from the menu.

    Edit environment

  2. In the Edit Production Environment dialog, make the necessary changes to the additional publish regions.

    • Use the Additional publish regions drop-down to select additional regions.
    • Click the X next to selected additional publish regions to de-select them.

    Edit environment

  3. Select Save to save the changes.

Changes made to the production environment apply to both production and staging environments. Changes to multiple publish regions can only be edited in the production environment.

If you want to provision advanced networking for the program, it is recommended that this provisioning is done before adding additional publish regions to the environments. Otherwise, the additional publish regions’ traffic goes through the primary region’s proxy.