DocumentationExperience Cloud KCS

AEMaaCS environment creation failure due to missing required product profiles or configuration conflicts

Last update: July 9, 2026

AEM as a Cloud Service environment creation can fail in Cloud Manager with a generic failed status and no logs. This usually happens when a required Admin Console product profile is missing, most commonly CM_CS_DEFAULT under Integrations – Cloud Service, although insufficient permissions, concurrent provisioning, or configuration conflicts can also contribute. To fix the issue, confirm no other creation is running, verify your permissions, create the missing product profile, and retry provisioning.

Description description

Environment

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

Issue/Symptoms

  • Environment creation fails without generating logs.
  • Cloud Manager shows the environment status as Failed.
  • Provisioning does not progress beyond the initial stage.
  • Cloud Manager does not display a detailed error message.

Cause

Environment creation fails when the required product profile CM_CS_DEFAULT is missing under Integrations – Cloud Service. Other contributing factors include insufficient permissions, concurrent environment creation, configuration conflicts, or provisioning timeouts.

Resolution resolution

Follow these steps to resolve the issue

  1. Verify that no other environment creation process is running in Cloud Manager.
  2. Verify that the user has the required Cloud Manager permissions and product profile assignments.
  3. In Admin Console, verify that the CM_CS_DEFAULT  product profile exists under Integrations – Cloud Service. Create the profile if it is missing.
  4. Retry environment creation and monitor the provisioning status.
  5. Review pipeline or provisioning conflicts, resolve any identified issues, and retry environment creation.
recommendation-more-help
experience-cloud-kcs-help-kbarticles