Unable to create an AEM as a Cloud Service environment in Cloud Manager
Adobe Experience Manager (AEM) as a Cloud Service environment creation fails in Cloud Manager when required permissions, product configurations, or provisioning prerequisites are missing or misconfigured. This issue occurs because Cloud Manager cannot successfully provision a new environment when required roles, profiles, configuration settings, or provisioning resources are unavailable. Concurrent environment creation requests can also prevent successful provisioning. To resolve the issue, validate permissions, review provisioning, and retry creation.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS)
Issue/Symptoms
- An environment creation job in Cloud Manager runs for some time and ultimately fails without creating the environment.
- The Add Environment option is dimmed or unavailable because of permission or resource-related issues.
- Environment provisioning begins but fails before the environment reaches a provisioned state.
- Cloud Manager activity logs show internal errors, configuration issues, timeout conditions, or provisioning failures during environment creation.
- Reattempting environment creation results in repeated provisioning failures.
Root cause
The issue occurs when Cloud Manager cannot provision an AEM environment because of missing or misconfigured required settings, insufficient permissions, missing product profiles, provisioning failures, timeout conditions, or resource locks caused by another concurrent environment creation request. Missing Business Owner permissions and missing Automated Forms Conversion Service profiles are common causes.
Resolution resolution
Follow these steps to identify and resolve environment provisioning failures in Cloud Manager:
- Verify that the Add Environment option is available by opening Cloud Manager, selecting the target program, and checking the Environments card.
- Validate Cloud Manager permissions by confirming that the account has the required Business Owner role.
- Check for concurrent environment creation or provisioning operations by reviewing the Environments and Pipelines sections and confirming that no conflicting provisioning activity is running.
- Verify that required profiles exist in Adobe Admin Console when the environment includes AEM Forms functionality by reviewing the Automated Forms Conversion Service product profiles.
- Reattempt environment creation after permissions, profiles, and provisioning conflicts are validated or corrected.
- Review Cloud Manager activity logs and identify whether the failure relates to permissions, configuration issues, internal errors, or timeout conditions.
- Collect failure details, screenshots, timestamps, and provisioning information when the issue persists after the retry attempt.
- Attempt environment creation again after all identified issues are addressed.
- Validate the resolution by confirming that the new environment appears in Cloud Manager, reaches the Provisioned state, and no environment creation operations remain stuck.
When to escalate
- Environment creation continues to fail after all customer troubleshooting steps are completed.
- Required profiles cannot be created or assigned in Adobe Admin Console.
- Cloud Manager activity logs continue to show provisioning failures after configuration and permission issues are resolved.
- Repeated provisioning attempts fail for the same program or organization.