Troubleshooting AEM as a Cloud Service environment creation failures in Cloud Manager
Creating a new AEM as a Cloud Service environment in Cloud Manager fails, often after the provisioning workflow has run for some time, leaving no environment provisioned. The failure traces to insufficient Cloud Manager permissions, a configuration problem such as a missing required product profile for AEM Forms, an internal pipeline or service error, a timeout, or a conflict with another environment creation running at the same time. These conditions stop Cloud Manager from provisioning the Author, Publish, and Dispatcher services. Confirming permissions, clearing concurrent provisioning, reviewing the pipeline logs, creating any missing Forms profile, and re-attempting the creation restores a successful provisioning run.
Description description
Environments:
- Adobe Experience Manager as a Cloud Service
- Adobe Cloud Manager
- AEM Forms as a Cloud Service
- Adobe Admin Console
- Author, Publish, and Dispatcher services
Issue/Symptoms:
- Environment creation in Cloud Manager fails after running for some time, with no specific error text.
- The Cloud Manager UI stops or marks environment creation as failed, and no environment is provisioned.
Root cause:
Environment creation fails when Cloud Manager can’t complete the required provisioning steps. The causes include insufficient user permissions, misconfiguration such as a missing required profile in the Admin Console for AEM Forms as a Cloud Service, internal pipeline or service errors, timeouts, or conflicts with a concurrent environment creation. Any of these prevent Cloud Manager from provisioning the Author, Publish, and Dispatcher services.
How to confirm
- Confirm you have the correct Cloud Manager permissions. Sign in to Cloud Manager and open your program’s Environments. If you can see the Add Environment or Create Environment option, you can initiate a creation request. If not, capture the permission error and ask your organization administrator to adjust your permissions.
- Check for concurrent environment creation. In Cloud Manager, confirm no other provisioning task is running under Environments — every environment should show Ready or Failed, not Provisioning. If one is in progress, wait for it to finish or cancel it if allowed.
- Review the pipeline logs. In Cloud Manager, open Pipelines, select the associated pipeline, open Execution History, and open the latest failed execution. Look for permission errors, configuration validation failures, or service-related errors, and download the logs if you need to escalate.
Resolution resolution
Follow these steps to resolve the issue:
- Validate the product profile prerequisites for AEM Forms. If you’re provisioning an AEM Forms as a Cloud Service environment, sign in to the Adobe Admin Console with an Adobe ID that has administrator rights, not a Federated ID. Under Automated Forms Conversion Service, open the Products tab and confirm at least one profile exists.
- Create the missing Forms profile if it’s absent. Click Automated Forms Conversion Service, click New Profile, enter the Name, Display Name, and Description, and click Done.
- Re-attempt environment creation. Return to Cloud Manager, open Environments, select Add Environment, and create the environment again. The environment enters the Provisioning state — monitor it until it transitions to Ready.
- Confirm the result. Verify the environment shows Ready, and confirm the Author, Publish, and Dispatcher services are accessible through the Cloud Manager environment links.
If the issue persists
Contact Adobe Support if environment creation still fails after these steps. Provide Cloud Manager screenshots of the failure state, the downloaded pipeline logs, and, if you’re using AEM Forms, screenshots of the Admin Console profile.