DocumentationExperience Cloud KCS

AEM as a Cloud Service: Production Config Pipeline Fails with ‘CDN Configuration could not be deployed’ due to unsupported fog forwarding Sink Type

Last update: June 28, 2026

This article explains how to resolve deployment failures in AEM as a Cloud Service pipelines caused by unsupported sink types in Log Forwarding configuration files.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms

When triggering a deployment pipeline for the Production environment, the pipeline fails during the configuration deployment phase. The following error is displayed in the Cloud Manager UI:

Error Pipeline details could not be displayed due to an intermittent error. Please try again.

Additionally, the pipeline execution logs show:

CONFIGURATION_DEPLOYMENT_FAILED
Error in config kind 'CDN': CDN Configuration could not be deployed.
  • The error occurs after validation, build, stage deployment, and approval steps have completed successfully.
  • The issue is reproducible by opening the pipeline execution page in Cloud Manager.

The problematic configuration in /config/prod/logForwarding-prod.yaml resembles:

data:
  customType:
    default:
      enabled: true
      url: "https://example.com/v1/logs/aemx"
      authHeaderName: "X-API-Key"
      authHeaderValue: "${{LOG_INGESTION_TOKEN}}"
    aem:
      enabled: false

This structure uses a custom top-level key customType that is not supported by the platform.

Resolution resolution

Try the following steps to solve the issue:

  1. Review the Log Forwarding configuration file used in the affected environment, typically located at /config/prod/logForwarding-prod.yaml.

  2. Identify any custom top-level keys (such as customType) in the configuration. AEM as a Cloud Service only supports sink-type keys listed in the documentation below:

    1. https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding

  3. Update the configuration to use a supported sink type. For example, replace the custom key with https while retaining the endpoint and authentication details as shown in the following example.

data:
  https:
    default:
      enabled: true
      url: "https://example.com/v1/logs/aem"
      authHeaderName: "X-API-Key"
      authHeaderValue: "${{LOG_INGESTION_TOKEN}}"
    aem:
      enabled: false

Commit and deploy the updated configuration to the affected environment. Re-run the pipeline in Cloud Manager and verify that the deployment completes successfully.

Cause

The deployment failed because the Log Forwarding configuration used an unsupported sink type key (customType). Only platform-recognized sink types (https, splunk, datadog) are allowed. Using an unsupported key prevents schema validation and causes the configuration deployment to fail.

recommendation-more-help
experience-cloud-kcs-help-kbarticles