Environment creation fails in Cloud Manager due to permissions, configuration, or concurrent provisioning
Creating an AEM as a Cloud Service environment in Cloud Manager can fail before provisioning completes, often showing only a generic error while the environment stays stuck. This is usually caused by missing permissions or product profiles, invalid configurations, or a concurrent provisioning operation. To fix the issue, verify your Admin Console permissions and required profiles, ensure no other creation job is running, and reattempt the environment creation.
Description description
Environment
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- Cloud Manager
Issue/Symptoms
- The environment creation job stops with a generic failure message and does not complete.
- The environment remains in a failed or stuck state after extended provisioning time.
- The Cloud Manager UI shows no detailed error, and creation never progresses past initialization.
Root cause
Provisioning cannot complete because of incorrect or missing entitlements, missing product profiles (such as a required Automated Forms Conversion Service profile), misconfigured permissions, invalid configurations pushed during creation, internal deployment or pipeline failures, or collisions with another provisioning operation running at the same time.
How to confirm
- Confirm that your user account is assigned to at least one AEM as a Cloud Service product profile in Admin Console.
- Check whether the required Automated Forms Conversion Service profile exists in Admin Console.
- Review the Environments list in Cloud Manager for any other environment that is currently provisioning.
Resolution resolution
To fix the issue:
- Validate your permissions in Admin Console. Sign in with an Adobe ID that has administrator rights, go to Products
>AEM as a Cloud Service, and confirm that your account is assigned to the appropriate product profile. If it is not, assign the correct profile or ask your administrator to assign it. - Verify that required product profiles exist. In Admin Console, go to Automated Forms Conversion Service
>Profiles and confirm the required profile is present. If it is missing, select New Profile, enter a name and description, and select Done. - Ensure no other environment creation is running for the same program. In Cloud Manager, open Environments and confirm all other environments are in a stable (Ready) state. If another job is provisioning, wait for it to finish or cancel it if appropriate.
- Reattempt environment creation. In Cloud Manager, select Environments
>Add Environment and complete the wizard. - After resolving any detected issues, re-run the environment creation. Confirm that the environment moves to the Ready state and that the author URL loads successfully, and verify that no other environments or pipelines show new failures.
- If the creation still fails, contact Adobe Support and provide the Cloud Manager job logs, screenshots of the failure, confirmation of your permissions, and confirmation that the required profiles are present.