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 creation in Cloud Manager fails after running for a period of time and ends in a failed state. The failure can occur in development, stage, production, or rapid development environments and may persist even after retrying the creation process.
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.
- Check that no other environment creation processes are running concurrently.
- Review Cloud Manager logs for deployment or configuration errors.
Resolution resolution
- Create a required Admin Console profile if none exists.
- Ensure the user has appropriate Cloud Manager permissions.
- Wait for or stop any concurrent environment creation operations.
- Fix any configuration or deployment issues identified in logs.
- Delete the failed environment and retry the environment creation.