Cloud Manager Environments are composed of AEM Author, AEM Publish and Dispatcher services. Different environments support roles and can be engaged using different CI/CD Pipelines. Cloud Manager environments typically have one Production environment, one Stage environment, and one Development environment.
Each Programming Cloud Manager is broken into environments. Environments are sets of AEM author and publish services, and every program can have one production environment, one stage environment, which is used to validate deployments. And depending on what has been purchased, one or more non-production environments, also referred to as development environments. Development environments may be used for various purposes such as development integration or quality assurance of custom code prior to deployment to stage for user acceptance testing and finally production.
The program’s overview page has a summarized view of available environments, including their status, indicating their general state. Individual environment details can be viewed by tapping View Details in the Environments, Actions dropdown. Or a more holistic view can be accessed via the Show All button or Environments in the top bar.
The environments view lists all the program’s environments their statuses, as well as the URL to the AEM author service which is used to access AEM. If any remaining environments are available to the program’s quota, the Add Environment button in the top right can be used to create the new environments.
Let’s go through the process now of creating a new environment for a weekend site.
Environment type defines the type of the new environment. Either a single stage plus production environment set or a development environment. The environment name is used to identify the environment and the environment description provides additional optional context about the environment. Finally, the cloud region allows you to select which of the available geographic regions the environment resources will be provisioned in. Back in the Environments view, tapping on a specific environment displays its details, including its information such as the author service URL, the region the environment exists in and the AEM release version it’s running. Environment segments provide the status of as well as direct URLs to each service tier. Note that both the published service for AEM and published service for dispatcher link to the same URL, as all access to the published service is always made through the CDN, dispatcher and back to AEM publish. Actions for each environment are available from the details view via the actions dropdown in the top right. Only the actions provisioned to the user are accessible. These same actions are available for each environment from the programs overview screen via the action dropdown next to each environment enlisted there. Download logs lets you download all the environments logs. Developer console opens the developer console, which provides further technical details about the state of the environment and running applications. Manage access opens Adobe Admin Console directly in the environment’s product context, where user access to AEM author service is managed. And finally delete which completely removes the environment including the code and content. -