AEM as a Cloud Service environment creation fails

Last update: July 24, 2026

Environment creation in Cloud Manager fails during provisioning and does not complete successfully. The failure can occur without a specific error message and is commonly caused by missing product profiles, insufficient permissions, configuration issues, or concurrent environment creation operations.

Description description

Environment

AEM as a Cloud Service (AEMaaCS)
Cloud Manager

Issue/Symptoms

Environment creation does not complete or stops after running for some time.
Cloud Manager shows the environment creation process as failed without a specific error message.

Root cause

Cloud Manager validates permissions, product profiles, and configurations before provisioning an environment. Provisioning fails when required product profiles are missing, the user lacks the required Cloud Manager role, configuration issues exist in related pipelines, or another environment creation task is already running.

Resolution resolution

To resolve this issue, follow these steps:

Open Cloud Manager and review the Environment Activity page for concurrent environment creation operations.
If another environment creation task is running, wait for it to complete before creating a new environment.
Verify that your account has the required Cloud Manager permissions, such as Deployment Manager or Product Owner.
Check that all required product profiles are available in Adobe Admin Console.
Create missing product profiles if they are required for your environment configuration.
Review recent Cloud Manager pipeline activity and identify configuration-related failures.
Correct any repository, OSGi, or Dispatcher configuration issues identified in pipeline logs.
Retry environment creation from Cloud Manager.
If the environment creation still fails, collect failure screenshots and contact Support.

recommendation-more-help

experience-cloud-kcs-help-kbarticles