Documentation

CDN configuration not applied in Edge Delivery Site for X-Walk architecture

Last update: Wed Nov 26 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

When using Adobe Experience Manager (AEM) for authoring and Edge Delivery Services (EDS) for delivery in an X-Walk setup, deploying CDN configurations to the wrong service can result in no effect. This issue occurs when customers use environment-specific YAML files (such as cdn-stage.yaml) with Edge Delivery Sites, which support only a single environment.

To fix this, ensure all CDN rules are consolidated into a single cdn.yaml file, use domain-based rules to isolate environment-specific behavior, and deploy the configuration using the Edge Config Pipeline.

Description description

Environment

  • AEM as a Cloud Service (AEMaaCS)
  • Edge Delivery Services
  • Config Pipelines
  • X-Walk implementations

Issue/Symptoms

  • CDN configuration changes made in cdn-stage.yaml or other environment-specific YAML files have no effect.
  • Domains are installed on the Edge Delivery Site, but CDN updates are attempted via the AEM config pipeline.
  • Edge Delivery Site doesn’t reflect expected behavior for dev, stage, or prod environments.
  • CDN rules are not applied as expected when using envTypes.

Resolution resolution

Note: Edge Delivery Sites support only one environment and have a 100 KB total CDN configuration size limit across all rules.

  1. Consolidate all CDN rules into one file named cdn.yaml.

  2. Set envType to prod in the configuration.

  3. Use domain-based rules to isolate environment-specific behavior. For example:

    code language-none 
    reqProperty: domain
            equals: stg-www.example.com

  4. In Cloud Manager, navigate to Edge Config Pipeline, upload cdn.yaml, and run the pipeline to apply changes. Do not use the AEM Config Pipeline for Edge Delivery Sites.

Use Config Pipelines in AEM as a Cloud Service User Guide.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f