AEM Cloud Manager Quickstart
AEM as a Cloud Service (AEMaaCS) changed the way how AEM is managed and upgraded. The fastest way to get value of your new AEMaaCS deployment is to onboard teams to efficiently use Cloud Manager. In AEMaaCS, Cloud Manager is the front door for everything related to access, environments, and CI/CD.
Cloud Manager provisions resources, centralizes access, and ships with built in CI/CD tailored to AEM with quality gates, security scanning, and performance checks. If you’re new to it, start with Adobe’s Cloud Manager introduction [1]. For a broader context on what’s new in AEMaaCS vs. prior versions, see this comparison [2].
- [1] - Cloud Manager introduction - setup, pipelines, and quality gates: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/concepts/cloud-manager-introduction
- [2] - AEMaaCS What is New and Different: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/overview/what-is-new-and-different
Below are five main steps that should support teams to start their new AEM Cloud Manager journey.
1) Introduction
2) Admin Console Setup
3) Cloud Manager Bootstrapping
4) Developer & Author Readiness
5) Recommended Learning
1) Introduction
Before anyone clicks around, align on what AEMaaCS is and isn’t. Review the core terminology and what changes when you move from on‑premises/AMS to cloud (see terminology) [3].
Check the overall architecture and the onboarding journey so the team can see the end‑to‑end path and where their role fits (overview) [4].
If you’re also using Assets, note the Cloud Service‑specific changes for authors [5].
💡 Tip: By the end of this step, your team should be able to explain why Cloud Manager exists and how AEM as a Cloud Service runs as always‑current service.
- [3] - AEM as a Cloud Service - Terminology: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/overview/terminology
- [4] - Onboarding Journey overview - step‑by‑step from access to first content: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/journey/overview
- [5] - Experience Manager Assets as a Cloud Service - Overview: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/overview
2) Admin Console Setup
Next, get people into the right roles early. In Adobe Admin Console, assign product profiles for AEM and the appropriate Cloud Manager roles (Deployment Manager, Developer, Business Owner, and so on) [6][7][8][9].
Decide who can open support tickets and confirm those options [10].
If you own your domains and certificates, plan ahead for SSL certificate management [13][14], and if your security model requires it, configure IP Allow Lists to restrict access by network [15][16][17].
💡 Tip: Create simple one‑page matrix mapping job functions to required access.
- [6] - Accessing the Admin Console (Onboarding Journey): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/journey/admin-console
- [7] - Admin Console overview (Adobe HelpX): https://helpx.adobe.com/enterprise/using/admin-console.html
- [8] - AEM as a Cloud Service - Team & Product Profiles: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/concepts/aem-cs-team-product-profiles
- [9] - Assign Team Members to Cloud Manager Product Profiles: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/journey/assign-profiles-cloud-manager
- [10] - Support Options for Experience Cloud: https://helpx.adobe.com/enterprise/using/support-for-experience-cloud.html
- [11] - SSL Certificates - Introduction: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/manage-ssl-certificates/introduction-to-ssl-certificates
- [12] - Manage SSL Certificates: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/manage-ssl-certificates/managing-certificates
- [13] - IP Allow Lists - Introduction: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/ip-allow-lists/introduction
- [14] - Manage IP Allow Lists: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/ip-allow-lists/managing-ip-allow-lists
- [15] - Apply/Unapply IP Allow Lists: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/ip-allow-lists/apply-allow-list
3) Cloud Manager Bootstrapping
Let's see how to prepare for implementation and delivery. Access Cloud Manager and confirm you’re in the right organization and context. Create your first Program (Production or Sandbox) and make sure the team understands program types [16][17].
Spin up the Environments you need, Dev, Stage, and Prod, with a topology that matches your requirements [18][19].
Initialize Git (either Adobe‑hosted or your own connection) and review the CI/CD pipelines for non‑production and production, including the quality gates and the promotion flow [20][21][22][23].
The goal is to establish a repeatable, policy‑driven pipeline where developers commit code and the gates take care of the heavy lifting.
- [16] - Programs and Program Types (Cloud Manager): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/programs/program-types
- [17] - Create a Program on Cloud Manager (Onboarding Journey): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/journey/create-program
- [18] - Create Environments on Cloud Manager (Onboarding Journey): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/journey/create-environments
- [19] - Managing Environments (Cloud Manager): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/manage-environments
- [20] - Repository Access Information (Git): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/accessing-repos
- [21] - CI/CD Production Pipeline (video + guide): https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/cloud-manager/cicd-production-pipeline
- [22] - CI/CD Non‑Production Pipeline (video + guide): https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/cloud-manager/cicd-non-production-pipeline
- [23] - CI/CD Pipelines - Overview and concepts: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-manager/content/overview/ci-cd-pipelines
4) Developer & Author Readiness
Unblock day‑to‑day work for both builders and creators.
Developers should validate local tooling, agree on a branch strategy, and confirm how pipeline triggers work, the onboarding guide for developers is a quick checklist [24]. Make sure teams know how to access and manage logs for troubleshooting and performance insight [25][26]. For local development, install the AEM as a Cloud Service SDK and follow the quickstart tutorial to ensure consistency across environments [27][28].
Authors should verify sign‑in paths and publish a first piece of content in the target environment. Consult AEM users guide [29].
💡 Tip: Keep in mind that previously referenced onboarding journey remains the best quick orientation for both tracks [4].
When this step is complete, engineers experience a smooth continuous integration flow, and authors get simple way to access and test implementation, without infrastructure delays.
- [24] - Developer & Deployment Manager Tasks (Onboarding Journey): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/journey/developers
- [25] - Accessing and Managing Logs: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/manage-logs
- [26] - Logging for AEM as a Cloud Service (concepts & CLI): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/logging
- [27] - Local Development Environment - Overview tutorial: https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/overview
- [28] - Set up local development environment (AEM as a Cloud Service SDK): https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/developing/basics/local-development-environment
- [29] - AEM User Tasks - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/journey/aem-users
5) Recommended Learning
Subscribe admins to release notes and set up notification profiles (user groups) so the right people get the right alerts [30].
Capture the important differences from AEM 6.5/AMS to avoid legacy assumptions [31].
Finally, confirm your entitlement view in the License Dashboard so stakeholders know what’s provisioned and who owns what [32].
💡 Tip: To learn more about optimization of AEMaaCS license costs, consult our guide - How To Lower AEMaaCS License Costs: 5 Cost-Reduction Tips To Save
- [30] - Notification Profiles - create user groups for notifications: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/onboarding/concepts/notification-profiles
- [31] - What is New and Different (AEMaaCS vs. prior versions): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/overview/what-is-new-and-different
- [32] - License Dashboard (solution entitlements): https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/license-dashboard