AEM as a Cloud Service environment creation fails in Cloud Manager
Environment creation in AEM as a Cloud Service can fail with a generic failed status after the process runs for some time. This is often caused by missing Admin Console product profiles, insufficient permissions, configuration issues, or concurrent provisioning conflicts. Pipeline errors or backend platform issues can also prevent successful provisioning. Resolution requires validating profiles, confirming permissions, checking logs, and correcting configuration issues.
Description description
Environment
- Adobe Experience Manager as a Cloud Service
- Cloud Manager
- Adobe Admin Console
Issue/Symptoms
- Environment creation displays a failed status in Cloud Manager
- The process runs for some time before failing
- A message may suggest deleting and recreating the environment
- Repeated attempts to create the environment continue to fail
Root cause
Failures occur when required Admin Console product profiles, especially for Forms-related services, are missing. Other causes include insufficient permissions, invalid configurations, pipeline execution errors, concurrent provisioning operations, or backend platform issues.
How to confirm
- Verify that at least one Automated Forms Conversion Service profile exists in the Admin Console.
- Confirm the user has permissions to create environments in Cloud Manager. In Cloud Manager, the Add Environment option is available and enabled when permissions are sufficient.
- Check that no other environment creation processes are running concurrently. Review the Environments list for any environment stuck in a Creating state.
- Review Cloud Manager logs for deployment or configuration errors. If creation involves a pipeline, open Cloud Manager
>Pipelines>View Logs and search the output for permission-related failures such asAccessDeniedExceptionorsling-distributionerrors.
Resolution resolution
- Create a required Admin Console profile if none exists. In Admin Console, select Automated Forms Conversion Service
>New Profile, enter a Name, Display Name, and Description, and select Done. Reload the page to confirm the profile persists. - Ensure the user has appropriate Cloud Manager permissions. If the Add Environment option is unavailable, contact your Organization Admin to grant the correct Cloud Manager roles.
- Wait for or stop any concurrent environment creation operations.
- Fix any configuration or deployment issues identified in logs. Correct the affected code or configuration (for example, Dispatcher configuration) in your Git repository and retry the deployment.
- Delete the failed environment and retry the environment creation. The environment should transition from Creating to Ready.
Validation
- The environment status in Cloud Manager shows Ready and not Failed.
- If a pipeline runs during creation, it completes with no errors in the deploy step logs.
- The author and publish service URLs shown in Cloud Manager are reachable.
When to escalate
Contact Adobe Support if environment creation continues to fail after completing all steps above. Provide the following:
- Timestamp of the failure
- Screenshots of the Cloud Manager UI
- The Admin Console product profile list
- Pipeline logs (if a pipeline is used during creation)
- Any error messages shown in the UI, and the Cloud Manager program ID and environment ID