AEMaaCS environment creation fails in Cloud Manager

Environment creation in Adobe Experience Manager as a Cloud Service may fail during provisioning in Cloud Manager. This issue commonly occurs due to missing permissions, absent product profiles, invalid configuration properties, or concurrent environment creation conflicts. These conditions prevent Cloud Manager from completing the provisioning workflow. Resolving the issue requires validating permissions, ensuring required profiles exist, and reviewing pipeline configurations. Confirming these prerequisites allows environment creation to proceed successfully.

Description description

Environment

  • Adobe Experience Manager as a Cloud Service (AEMaaCS)
  • Cloud Manager

Issue/Symptoms

  • Environment creation runs for some time and then fails
  • Cloud Manager displays a failed environment creation status
  • No environment is created after the provisioning process

Cause

Environment creation fails due to one or more of the following reasons:

  • Missing required product profiles for AEM Forms.
  • Insufficient permissions in Adobe Admin Console or Cloud Manager.
  • Invalid or incomplete configuration properties.
  • Pipeline execution failures.
  • Concurrent environment creation conflicts.

How to Confirm

  • Check whether another environment is currently in the Creating state in Cloud Manager.
  • Verify access to the Environments section without permission errors.
  • Confirm that required product profiles exist in Adobe Admin Console.
  • Review pipeline execution logs for configuration or timeout errors.

Resolution resolution

Follow these steps to resolve the issue

  1. Sign in to Cloud Manager and verify that no other environment creation is currently in progress.
  2. Wait for any active environment creation to complete before retrying.
  3. Verify that your account has the required permissions, such as Deployment Manager or System Administrator.
  4. Open Adobe Admin Console and confirm that required product profiles exist, especially for AEM Forms environments.
  5. Review the configuration pipeline and verify that all required properties are defined correctly and contain valid values.
  6. Open Cloud Manager pipelines and review the latest execution logs for configuration, timeout, or permission-related errors.
  7. Resolve the identified issues and retry creating the environment.
recommendation-more-help
experience-cloud-kcs-help-kbarticles