Cloud Manager is an essential component of AEM as a Cloud Service and serves as the single entry point for your team.
To support customers with enterprise development setups, AEM as a Cloud Service fully integrates with Cloud Manager and its purpose-built CI/CD pipelines, which are equipped to ensure thorough testing and highest code quality to deliver exceptional experiences.
To ensure customers can start quickly with AEM as a Cloud Service, Cloud Manager provides everything required to get started in a self-service manner including the ability to create your cloud resources and environments. In this manner, your AEM developers can access the Git repository via Cloud Manager. Using Cloud Manager, development teams can work towards committing changes frequently in a self-service manner.
Your System Administrator will be responsible to setting up your Cloud Manager team which will include individuals that will create your cloud resources and developers. Refer to Enterprise Team Development Setup for AEM as a Cloud Service to learn how Cloud Manager supports in Enterprise Team Development Setup.
Follow the steps below to navigate to Cloud Manager:
Navigate directly to Cloud Manager’s login page from my.cloudmanager.adobe.com.
Please bookmark this page for future reference and to help you navigate directly to Cloud Manager’s landing page.
Select the program from Cloud Manager’s Programs and Products page to launch the Overview page.
Additionally, you can also navigate to Cloud Manager’s Programs and Products page from Adobe Experience Cloud home page. Follow the steps below:
Navigate directly to Adobe Experience Cloud and login using your Adobe ID.
Select Experience Manager.
Click on Launch from the Cloud Manager card. Once you have successfully logged in to Cloud Manager, you are ready to use the User Interface (UI).
Upon successful login, you will be directed to the landing page of Cloud Manager.
|Permission||Description||Business Owner||Deployment Manager||Program Manager||Developer|
|Add a New Program.
Edit a program - Add or remove solutions or add-on’s
|Create Environment||Create Prod+Stage, Dev, Environments.||x||x|
|Update Environment||Update Prod+Stage, Dev, Environments.||x||x|
|Delete Dev Environment||Delete Dev Environments.||x||x|
|Pipeline Setup||Setup or Edit Pipeline.||x|
|Pipeline Execution||Start the Pipeline.||x||x|
|Pipeline Execution||Reject/Approve Important 3-Tier Failures.||x||x||x|
|Pipeline Execution||Provide GoLive Approval.||x||x||x|
|Pipeline Execution||Schedule Production Deployment.||x||x||x|
|Pipeline Delete||Allows Deleting of a Pipeline.||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 them the combination or sum of these permissions.
Cloud Manager Programs represent sets of Cloud Manager environments supporting logical sets of business initiatives, typically corresponding to a purchased Service Level Agreement (SLA). For example, one Program may represent the AEM resources to support the global public Web sites, while another Program represents an internal Central 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.
Refer to Introduction to Production Programs for more details.
A Sandbox Program is typically created to serve the purposes of training, running demo’s, enablement, POC’s, or documentation. It is not meant to carry live traffic and will have restrictions that a Production program will not. It will include Sites and Assets and will be delivered auto-populated with a Git branch that includes sample code, a Dev environment, and a non-production pipeline.
Refer to Introduction to Sandbox Programs for more details.
Your cloud environments will be created, accessed and viewed via Cloud Manager. These can be a Production environment, Stage environment, or Development environment. Different environments support different purposes and can be engaged using different CI/CD Pipelines. Environments are composed of services such as:
AEM Author Service is included in an environment where site content and digital assets are created, managed and updated. Typically, only internal users have access to the Author Service and is behind a login screen. The Authoring Service is designed both as an authoring and preview environment.
AEM Publish Service is included in an environment that hosts the end-user experience, like a web site. This is the service that site visitors will view and interact with. Typically, the Publish 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 Publish Service.