Troubleshooting AEM as a Cloud Service environment creation failures in Cloud Manager
AEM as a Cloud Service environment creation fails in Cloud Manager because of insufficient permissions, a missing required Admin Console profile, internal provisioning or pipeline errors, timeouts, or conflicts from concurrent environment operations. The failure often runs for some time and then stops without a clear error in the UI, which makes the cause hard to see. For AEM Forms environments specifically, a missing Automated Forms Conversion Service profile in the Admin Console causes the failure. Verifying your Cloud Manager permissions, confirming no concurrent operation is blocking provisioning, and ensuring the required profile exists lets the environment create successfully.
Description description
Environments:
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- Cloud Manager (environment provisioning)
- Adobe Admin Console
- AEM Forms as a Cloud Service (Automated Forms Conversion Service)
Issue/Symptoms:
- Environment creation in Cloud Manager stops or fails after running for an extended period.
- The Cloud Manager UI shows a generic failure notice without detailed error information.
- For AEM Forms environments, the failure occurs when the required Automated Forms Conversion Service profile is missing.
Root cause:
Environment creation in AEM as a Cloud Service relies on Cloud Manager provisioning sequences, permissions, and linked Admin Console configurations. Failures occur when the user lacks the required Cloud Manager permissions, a required product profile (such as the one for AEM Forms Automated Forms Conversion Service) is missing, an internal provisioning task hits a timeout, the configuration is invalid, or another environment creation or pipeline operation is running concurrently and blocking resources.
How to confirm
- Confirm you have the correct Cloud Manager permissions. Open Cloud Manager and verify you can reach Program
>Environments>Create Environment and that the Create Environment button is visible and clickable. If it isn’t, confirm your Adobe ID is assigned a Cloud Manager admin or deployer role. - Confirm no concurrent operation is running. In Cloud Manager
>Activity, review recent activities and confirm no environment creation or code deployment pipeline is actively running that could block provisioning. - Review the activity logs for the failed attempt. In Cloud Manager
>Activity, select the failed environment creation and look for any failure-stage messages (provisioning, configuration, or deployment), even if they’re generic.
Resolution resolution
Follow these steps to resolve the issue:
- Assign the required Cloud Manager role. If you can’t reach the Create Environment wizard, have your Org Admin add your Adobe ID to the correct Cloud Manager product profile with an admin or deployer role.
- Wait for concurrent operations to finish. If an environment creation or pipeline is already running, wait until it completes before starting a new environment creation, so it doesn’t block provisioning resources.
- For an AEM Forms environment, confirm the Automated Forms Conversion Service profile exists. Log in to the Admin Console with an administrator Adobe ID (not a Federated ID) and go to Automated Forms Conversion Service
>Products>New Profile. Confirm at least one profile exists with a Name, Display Name, and Description. If none exists, create one by clicking New Profile, filling out the required fields, and clicking Done. - Re-attempt the environment creation. In Cloud Manager, go to Program
>Environments>Create Environment and confirm the wizard completes without immediate validation errors and that the activity moves through the early provisioning stages. If it fails again, collect the timestamps, screenshots, and program ID for escalation.
Validation
- Confirm the environment appears under Program
>Environments in a Ready or Running state. - Trigger a simple pipeline, if applicable, to confirm the new environment accepts deployments.
- Confirm the environment services (Author, Publish, Dispatcher) appear on the Cloud Manager environment overview page.