Managing 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).
-
Production + Stage - The 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.
-
Development - A 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 Development - A rapid development environment (RDE) lets a developer swiftly deploy and review changes, minimizing the amount of time required to test features that are proven to work on a local development environment. See the rapid development environment documentation for details about how to use an RDE.
The capabilities of individual environments depend upon the solutions enabled in the program of the environment.
Adding an Environment adding-environments
To add or edit an environment, a user must be a member of the Business Owner role.
-
Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
-
On the My Programs screen, tap or click the program for which you want to add an environment.
-
From the Program Overview page, click Add Environment on the Environments card to add an environment.
-
The Add Environment option is also available on the Environments tab.
-
The Add Environment option may be disabled due to lack of permissions or depending on the licensed resources.
-
-
In the Add environment dialog that appears:
-
Select an environment type.
- The number of available/used environments is displayed in parentheses behind the environment type name.
-
Provide an environment Name.
-
Provide an environment Description.
-
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.
- Depending on your available entitlements, you may be able to configure multiple regions.
-
-
Click Save to add the specified environment.
The Overview screen 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.
Adding 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.
- Select the Primary region.
- The primary region cannot be changed after environment creation.
- Select the option Add additional publish regions and a new Additional publish regions option drop-down appears.
- In the Additional publish regions drop-down, select an extra region.
- The region selected is added below the drop-down to indicate its selection.
- Select the
Xnext to the selected region so you can de-select it.
- Select the
- Select another region from the Additional publish regions drop-down to add another region.
- Select Save when you are ready to create your environment.
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.
Editing 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).
-
From the Program Overview console of your program, click the ellipsis button for your production environment and select Edit from the menu.
-
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.
-
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.
Environment Details viewing-environment
You can use the Environments card on the overview page to access an environment’s detail in two ways.
-
From the Overview page, click the Environments tab at the top of the screen.
-
Alternatively, click the Show All button on the Environments card to jump directly to the Environments tab.
-
-
The Environments opens and lists all environments for the program.
-
Click an environment in the list so you can reveal its details.
Alternatively, click the ellipsis button of the environment you want and then select View Details.
Accessing 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 requisite permissions must complete the following steps before sharing the preview service URL to ensure access to it.
-
Create an appropriate IP allowlist, apply it to the preview service, and immediately unapply the
Preview Default [<envId>]allowlist.- See Applying and Unapplying IP Allow Lists for more details.
-
Use the update IP Allow List workflow to remove the default IP and add IPs as appropriate. See Managing IP Allow Lists to learn more.
After access to 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 UI inside AEM. See Previewing Content for more details.
2021.05.5368.20210529T101701Z or newer to use the preview service. Make sure that an update pipeline has successfully run on your environment so you can use the preview service.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.
-
On the Overview page, locate the Environments card.
-
On the Environments card, the Status column will reflect if there are any issues with the configured additional publish regions. Click the Info icon for details of the regions.
Alternatively you can access the same information from the Environments tab.
-
On the Overview page, select the Environments tab.
-
On the Environments tab, select the environment you want to query in the left navigation panel.
-
Once an environment is selected:
- The Environment Information table will show which regions are configured for the selected environment.
- The Status column of the Environment Segments table will reflect if there are any issues with the configured additional publish regions. Hover over the status for details of any issue.
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.
In any case, traffic is always routed to the other closest region that is online. If you continue to see issues, contact Adobe Customer Care.
Updating Environments updating-dev-environment
As a cloud-native service, updates of your staging and production environments within production programs are automatically managed by Adobe.
However, updates to development environments and 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.
If Cloud Manager detects that there is a newer version of AEM available than what was last deployed with the pipeline, it shows the Update Available status for the environment.
The process of updating is therefore a two-step process:
- Updating the pipeline with the latest AEM version
- Running the pipeline to deploy the new version of AEM to an environment
Updating Your Environments updating-your-environments
The Update option is available from the Environments card for development environments and environments in sandbox programs by clicking the ellipsis button of the environment.
This option is also available by clicking the Environments tab of the program and then selecting the ellipsis button 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.
- If the pipeline has already been updated, the Update option prompts the user to execute the pipeline.
- If the pipeline is already being updated, the Update option informs the user that an update is already running.
- If an appropriate pipeline does not exits, the Update option prompts the user to create one.
Deleting 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 the ellipsis button 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 the ellipsis button of the environment and select Delete.
- Production and staging environments created in a production program cannot be deleted.
- Production and staging environments in a sandbox program can be deleted.
Managing 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.
Accessing the Developer Console accessing-developer-console
Select Developer Console from the ellipsis menu of the environment on the Environments card. A new tab is opened in your browser with the log on 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 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 the ellipsis menu of an individual environment.
Login Locally login-locally
Select Local Login from the ellipsis menu of the environment in the Environments card to log on locally to Adobe Experience Manager.
Also, you can log on locally from the Environments tab of the Overview page.
Managing Custom Domain Names manage-cdn
Custom domain names are supported in Cloud Manager for Sites programs for both publish and preview services. Each Cloud Manager environment can host up to a maximum of 250 custom domains.
To configure custom domain names, navigate to the Environments tab and click an environment to view environment details.
A user must have the Business Owner or Deployment Manager role to add a custom domain name in Cloud Manager
The following actions can be performed on the publish service for your environment.
Managing IP Allow Lists manage-ip-allow-lists
IP allowlists are supported in Cloud Manager for author, publish, and preview services for Sites programs.
To manage IP allowlists, navigate to the Environments tab of the Overview page of your program. Click an individual environment so you can manage its details.
Applying an IP Allow List apply-ip-allow-list
Applying an IP allowlist associates all IP ranges included in the definition of the allowlist with an author or publish service in an environment. A user in the Business Owner or Deployment Manager role must be logged in to be able to apply an IP allowlist.
The IP allowlist must exist in Cloud Manager to apply it to an environment. To learn more about IP allowlists in Cloud Manager, see Introduction to IP Allow Lists in Cloud Manager.
To apply an IP allowlist:
- Navigate to the specific environment from the Environments tab of the program Overview screen and navigate to the IP Allow Lists table.
- Use the input fields at the top of the IP allowlist table so you can select the IP allowlist and the author or publish service you want to apply it to.
- Click Apply and confirm your submission.
Unapplying an IP allowlist unapply-ip-allow-list
Unapplying an IP allowlist disassociates all IP ranges included in the definition of the allowlist from an author or publisher service in an environment. A user in the Business Owner or Deployment Manager role must be logged in to be able to unapply an IP allowlist.
To unapply an IP allowlist:
- Navigate to the specific environment from the Environments tab of the program Overview screen and navigate to the IP Allow Lists table.
- Identify the row where the IP allowlist rule that you want to unapply is listed.
- Select the ellipsis button from end of the row.
- Select Unapply and confirm your submission.