Site creation fails with Edge Delivery Services template due to duplicate configuration in AEMaaCS
In Adobe Experience Manager as a Cloud Service (AEMaaCS), site creation using the Edge Delivery Services template fails when a cloud configuration for the same repository already exists. The process stops due to validation constraints that prevent duplicate configurations for a single repository. To resolve the issue, remove duplicates or use a new repository.
Description description
Environment
- Product: Adobe Experience Manager as a Cloud Service (AEMaaCS)
- Constraint: Site creation in a development environment
Issue/Symptoms
-
Site creation using the Edge Delivery Services Template 0.1.2 fails with the message: Create Site From Site Template - Failed - Background Job with source: “/content/eds-test-new-site1” has failed.
-
The logs display the following combined error message:
code language-none WARN com.adobe.aem.wcm.franklin.internal.SiteCreationProcessorImpl A cloud configuration for owner '<user>' and repo '<repo>' already exists at: /conf/<existing-site>/settings/cloudconfigs/edge-delivery-service-configuration ERROR com.adobe.granite.jobs.async.commons.AbstractAsyncJobExecutor Could not execute job ... com.day.cq.wcm.api.WCMException: Site creation validation failed (SiteCreationProcessorImpl) -
Site creation fails when a cloud configuration for the same repository already exists in the Author instance.
Root cause
Site creation enforces a validation rule that allows only one Edge Delivery Services cloud configuration per repository. Duplicate configurations for the same repository cause the validation to fail.
Resolution resolution
Follow these steps to resolve site creation failures caused by duplicate cloud configurations:
- In AEM Author, go to Tools
>Cloud Services>Edge Delivery Services Configuration. - Review the existing Edge Delivery configurations and confirm whether multiple entries exist for the same repository.
- Remove duplicate configurations by keeping only one Edge Delivery Services cloud configuration per repository and deleting the additional entries.
- Alternatively, create a new site by using a separate GitHub repository to avoid configuration conflicts.
- Retry site creation using the Edge Delivery Services template after removing duplicates or assigning a new repository.