Manage Environments managing-environments

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

Environment types 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).

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

Add an environment adding-environments

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

To add an environment:

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 multiple-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.

Add multiple publish regions to a new environment add-regions

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

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 edit-regions

If you did not specify any additional regions initially, you can do so after the environments are created if 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).

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.

Access Environment details viewing-environment

Access the preview service access-preview-service

Cloud Manager provides a preview service (delivered as an extra publish service) to each AEM as a Cloud Service environment.

Using the service you can preview a website’s final experience before it reaches the actual publish environment and is available publicly.

On creation, the preview service has a default IP allowlist applied to it, labeled Preview Default [<envId>], which blocks all traffic to the preview service. Unapply the default IP allowlist from the preview service so you can enable access.

A user with the requisite permissions must complete the following steps before sharing the preview service URL to ensure access to it.

After access to the preview service is unlocked, the lock icon in front of the preview service name is no longer displayed.

Once activated, you can publish content to the preview service by using the Manage Publication user interface inside AEM. See Preview content for more details.

Status of additional publish regions additional-region-status

If you have activated additional publish regions, you can check the status of these regions from the Environments card.

Alternatively you can access the same information from the Environments tab.

If there are any issues reported with additional publish regions, be patient. Cloud Manager continuously tries to recover the region and it may become available at any time. If the problem persists after several hours, you can remove the additional publish region and re-add it (either the same region or another region) to trigger a complete deployment.

How long you wait for the system to recover on its own before taking additional action depends on the impact the failure of that region has to your systems.

Regardless, traffic is always routed to the closest region that is online. If you continue to see issues, contact Adobe Customer Care.

Update environments updating-dev-environment

As a cloud-native service, Adobe automatically manages updates for your development, staging, and production environments within production programs.

However, updates to environments in sandbox programs are managed within the programs. When such an environment is not running the latest publicly available AEM version, the status on the Environments card on the Overview screen of the program shows Update Available.

Updates and pipelines updates-pipelines

Pipelines are the only way to deploy code to the environments of AEM as a Cloud Service. For this reason, each pipeline is associated with a particular AEM version.

When Cloud Manager detects a newer version of AEM than the one last deployed with the pipeline, it displays the Update Available status for the environment.

The process of updating is therefore a two-step process:

Update your environments updating-your-environments

The Update option is available on the Environments card for specific development and sandbox environments. Click next to the environment to access Update.

This option is also available by clicking the Environments tab of the program and then clicking of the environment.

A user with the Deployment Manager or Business Owner role can use this option to update the pipeline associated with this environment to the latest AEM version.

Once the pipeline version is updated to the latest publicly available AEM version, the user is prompted to run the associated pipeline to deploy the latest version to the environment.

The Update option’s behavior varies depending on the configuration and current state of the program.

Delete development environments deleting-environment

A user with the Deployment Manager or Business Owner role is able to delete a development environment.

From the Overview screen of the program on the Environments card, click of the development environment you want to delete.

The Delete option is also available from the Environments tab of the Overview window of the program. Click of the environment and select Delete.

Manage access managing-access

Select Manage Access from the ellipsis menu of the environment on the Environments card. You can navigate to the author instance directly and manage access for your environment.

Access the Developer console accessing-developer-console

A new tab is opened in your browser with the logon page to the Developer Console.

Only a user with the Developer role has access to the Developer Console. However, for sandbox programs, any user with access to the sandbox program has access to the Developer Console.

See Hibernating and De-hibernating Sandbox Environments for more details.

This option is also available from the Environment tab of the Overview window when clicking of an individual environment.

Login locally login-locally

Manage custom domain names manage-cdn

Custom domain names are supported in Cloud Manager for Sites programs for both publish and preview services.

Manage IP Allow Lists manage-ip-allow-lists

An IP Allow List is supported in Cloud Manager for author, publish, and preview services for Sites programs.

To manage IP Allow Lists, navigate to the Environments page of the Overview page of your program. Click an individual environment so you can manage its details.

Apply an IP Allow List apply-ip-allow-list

Applying an IP Allow List links all defined IP ranges to an author or publish service in the environment.