In this part of the onboarding journey, you will learn how to use Cloud Manager to create your first environments.
After reading the previous document in this onboarding journey, Creating Programs, you now have your own Cloud Manager program. Now you can lean how to use Cloud Manager to create your first environments for that program.
After reading this document, you will:
Environments sit below programs within the hierarchy of Cloud Manager. While programs allow you to organize your solution and grant access to particular team members to those programs, environments belong to specific programs and are individual instances of the Adobe solutions within those programs. Environments are used for a specific purpose such as authoring content or testing new developments. Cloud Manager’s CI/CD pipelines facilitate the deployment of code to these environments from git repositories.
If you recall the example of the theoretical WKND Travel and Adventure Enterprises, who is a tenant that focuses on travel-related media, they might have two programs: one Sites program for its WKND Magazine division and one Assets program for WKND Media division. Each program would likely have a couple of environments such as one production environment which serves the actual traffic of the site and one development environment for testing new application code.
There are three different types of environments:
For the purposes of this onboarding journey, you will create a development environment.
Log into Cloud Manager at my.cloudmanager.adobe.com and select the appropriate organization.
Click on the program for which you want to add an environment.
From the Program Overview page, click on Add Environment on the Environments card to add an environment.
The Add Environment option is also available on the Environments tab.
The Add Environment option may be disabled due to lack of permissions or depending on the licensed resources.
In the Add environment dialog that appears:
Click Save to add the specified environment.
Once the environment is available, members of your organization assigned to the Developer product profile can log in to Cloud Manager and manage Cloud Manager git repositories.
Now that you have read this part of the onboarding journey, you should:
Your cloud resources have been created and are ready to be accessed by your team. As the system administrator you must first assign your team members to AEM as a Cloud Service product profiles from Adobe Admin Console in order for them to access those resources.
Therefore you should continue your onboarding journey by next reviewing the document Assigning Team Members to AEM as a Cloud Service Product Profiles. In that document you will learn how to grant your team members the rights they need to access your new environments.
Follow the additional resources to learn about: