Logo Light
  Menu
Lessons
 

Getting Started with AEMasCs

Before we get started with AEM as a Cloud Service (AEMasCS), it’s essential to have a foundational understanding of several key applications and their purposes. Here’s an overview of each:

  1. Adobe Admin Console: The Adobe Admin Console serves as a centralized platform for user management across various Adobe applications, including AEM, Adobe Analytics, Adobe Experience Manager Sites, and others. This console enables administrators to manage user permissions, assign roles, and control access to different features and services within the Adobe ecosystem. It simplifies the process of onboarding new users, managing licenses, and ensuring compliance with organizational policies. By leveraging the Admin Console, teams can maintain security and streamline collaboration across different Adobe products, making it easier to manage both internal and external stakeholders.

  2. AEM Cloud Manager: AEM Cloud Manager is an integral tool for managing AEM environments in the cloud. It provides a streamlined process for creating, configuring, and deploying various AEM environments, such as development, staging, and production. With Cloud Manager, developers can automate deployment workflows, ensuring consistency and reducing the risk of human error during the deployment process. Additionally, it offers performance monitoring and optimization features, allowing teams to track the health of their applications and make necessary adjustments to enhance performance. Cloud Manager also facilitates continuous integration and continuous delivery (CI/CD) practices, enabling faster and more reliable updates to AEM applications.

  3. Adobe Developer Console: The Adobe Developer Console is a powerful platform designed for integrating Adobe applications with third-party services and APIs. It provides developers with the tools necessary to create and manage integrations, enabling seamless data exchange and functionality between different systems. Through the Developer Console, users can generate API credentials, manage service accounts, and access Adobe’s extensive libraries and SDKs. This console supports a wide range of use cases, from connecting AEM with external content sources to integrating analytics and marketing tools, thereby enhancing the overall capabilities of Adobe solutions and facilitating a more connected digital experience.

AEMasCS Terminology

To get started with AEM as a Cloud Service (AEMasCS), it’s essential to familiarize yourself with the basic terminology associated with the platform. The diagram below provides a detailed overview of these key terms and concepts.

  • TENANT – Every customer is provisioned with a tenant. A tenant is also referred to as an IMS org (more on IMS later in this journey)
  • PROGRAMS – Each tenant has one or more programs, which often reflect the customer’s licensed solutions.
  • ENVIRONMENTS – Each program has multiple environments such as production for live content, one for staging, and one for development purposes.
  • REPOSITORY – The environments have one or more git repositories where application and front-end code is maintained.
  • TOOLS & WORKFLOWS – Pipelines manage the deployment of code from the repositories to the environments.