Cloud Manager is an essential component of AEM as a Cloud Service and serves as the single entry point for your team. Its purpose-built CI/CD pipelines are equipped to ensure thorough testing and highest code quality to deliver exceptional experiences. To ensure customers can quickly start their projects, Cloud Manager provides everything required in a self-service manner including the ability to create your cloud resources and environments and access your git repositories. These features support enterprise development setups so teams can work towards committing changes frequently, rapidly delivering exceptional digital experiences, and accelerating time-to-value.
Your system administrator is responsible for setting up your Cloud Manager team which will include individuals that will create your cloud resources and developers. For more information about how to set up and scale your enterprise development team and see how AEM as a Cloud Service can support your development process, please refer to the document Enterprise Team Development Setup for AEM as a Cloud Service.
Follow these steps to navigate to Cloud Manager.
Navigate to Cloud Manager’s login page at
Select the program from Cloud Manager’s Programs and Products page to launch the Overview page.
You can also navigate to Cloud Manager’s Programs and Products page from Adobe Experience Cloud home page by following these steps.
Navigate to Adobe Experience Cloud at
https://experience.adobe.com and login using your Adobe ID.
Ensure that you are in the correct organization by referring to the organization name displayed at the top-right of the toolbar.
Select Experience Manager.
On the Cloud Manager card, click on Launch
|Permission||Description||Business Owner||Deployment Manager||Program Manager||Developer|
|Add a New Program
Add or remove solutions or add-ons
|Create Environment||Create production+staging and development environments||x||x|
|Update Environment||Update production+staging and development environments||x||x|
|Delete Dev Environment||Delete development environments||x||x|
|Pipeline Setup||Setup and edit pipelines||x|
|Pipeline Execution||Start pipelines||x||x|
|Pipeline Execution||Reject/approve important 3-tier quality gate failures||x||x||x|
|Pipeline Execution||Provide go live approval||x||x||x|
|Pipeline Execution||Schedule production deployments||x||x||x|
|Pipeline Delete||Allow pipeline deletion||x|
|Execution Cancel||Cancel current execution||x|
|Generate Personal Access Token||Access git||x||x|
A user can be assigned to multiple roles. For example assigning both Business Owner and Deployment Manager roles to a user gives the user the sum of these permissions.
Cloud Manager programs represent sets of Cloud Manager environments supporting logical groupings of business initiatives. These groupings typically correspond to a purchased Service Level Agreement (SLA). For example, one program may represent the AEM resources to support an organization’s public Web site, while another program represents an internal DAM.
Watch this video to learn more on using Cloud Manager programs.
A user can create a Sandbox or a Production program.
A production program is created to enable live traffic at the appropriate time in the future.
A sandbox program is typically created to serve the purposes of training, running demos, enablement, creating POCs, or for documentation.
Your cloud environments will be created, accessed and viewed via Cloud Manager. These environments can be production, staging, or development environments. Different environments serve different purposes and can be used with different CI/CD pipelines. Environments are composed of services such as:
An AEM authoring service is included in environments where site content and digital assets are created, managed, and updated. Typically only internal users have access to the authoring service and it is maintained behind a login screen. The authoring service acts as both an authoring and preview environment.
An AEM publishing service is included in environments that host the end-user experience, like a web site. This is the service that site visitors will view and interact with. Typically, the publishing service is publicly available.
The dispatcher is an
Apache HTTP Web server module that provides a security and performance layer that sits in front of the AEM publishing service.