DocumentationExperience Cloud KCS

Cloud Manager LogForwarding audit fails with context deadline exceeded in Adobe Experience Manager

Last update: July 31, 2026

In Adobe Experience Manager as a Cloud Service, Cloud Manager deployment pipelines can fail during LogForwarding credential audits when forwarding logs to an external Splunk HEC endpoint. The failure occurs during the pre-flight LogForwarding credentials audit and returns a timeout error. To fix this issue, correct the LogForwarding.yaml structure, validate advanced networking settings, and deploy the configuration properly.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Issue/Symptoms

  • When configuring external log forwarding to a Splunk HTTP Event Collector (HEC) endpoint using LogForwarding.yaml, the Cloud Manager deployment pipeline fails during the pre-flight LogForwarding credentials audit job.
  • The following error is observed:context deadline exceeded (Client.Timeout exceeded)
  • The network connectivity test from the live AEM environment to the Splunk endpoint is successful, as the dedicated static egress IP is allowlisted upstream.
  • The pipeline build container uses dynamic IPs, which are not allowlisted, causing the audit job to fail.
  • The customer requests either the public egress IP CIDR ranges for the build agents or a method to route pipeline/pre-flight traffic through the dedicated egress IP.

Cause

The LogForwarding credential audit fails because the pipeline’s dynamic IP addresses aren’t allowlisted and advanced networking isn’t enabled correctly in the configuration.

Resolution resolution

To fix this issue, follow these steps:

  1. Verify that Advanced Networking/Dedicated Egress is enabled for the relevant environments (Dev, Stage, and Production) in Cloud Manager.

  2. Correct the LogForwarding.yaml structure. Place the aem: block that enables advanced networking inside the splunk: block instead of defining it as a sibling block. Use the following structure:

    code language-none 
    kind: "LogForwarding"
version: "1"
metadata:
  envTypes: [ "dev", "stage", "prod"]
data:
  splunk:
    default:
      enabled: true
      host: "<splunk-hec-host>"
      port: 443
      token: "${{SPLUNK_TOKEN}}"
      index: "aem"
    aem:
      advancedNetworking: true

  3. Deploy the configuration to each environment. For a shared configuration file, include all relevant environments in envTypes. For separate files, deploy each correctly structured file through the corresponding Configuration Pipeline.

  4. Deploy to Stage first and confirm that the credential audit passes and that logs are received in the Splunk index. After validation, repeat the deployment for Production.

Note: Cloud Manager pipeline build agents use dynamic IPs and individual allowlisting is not supported. Cloud Manager pipeline and pre-flight traffic can’t be routed through the program’s dedicated egress IP. Only runtime AEM environments use the dedicated egress IP.

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