DocumentationExperience Cloud KCS

Environment creation fails in Cloud Manager due to configuration or permission issues

Last update: June 27, 2026

AEM environment creation in Cloud Manager fails without clear error messages, often stopping shortly after initiation. It could happen due to insufficient permissions, missing service profiles, configuration issues, or internal pipeline errors. To resolve this, validate access, check configurations and profiles, and review logs.

Description description

Environment:

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

Issue/Symptoms:

  • Environment creation fails after running for some time
  • Cloud Manager displays a failed status without detailed error information

Root cause:

Environment creation depends on correct permissions, valid configuration, and available backend resources. Missing required Admin Console profiles, insufficient user permissions, configuration issues, internal pipeline errors, timeouts, or concurrent environment creation attempts can cause failures.

How to confirm

  • Verify that the Add Environment option is available and usable in Cloud Manager
  • Check that no other environment creation process is currently in progress
  • Review pipeline logs for errors such as timeouts or configuration failures
  • Confirm that required service profiles exist in the Admin Console

Resolution resolution

To fix the issue:

  1. Verify that the user has sufficient permissions to create environments.
  2. Ensure no other environment creation process is running; wait or cancel if needed.
  3. Confirm required service profiles exist in the Admin Console for relevant services.
  4. Review pipeline logs to identify internal errors or timeouts.
  5. Validate all configuration inputs such as environment type, region, and enabled features.
  6. Retry environment creation after correcting any identified issues.
recommendation-more-help
experience-cloud-kcs-help-kbarticles