Log forwarding to Splunk fails in Adobe Experience Manager as a Cloud Service
This article describes why log forwarding to Splunk fails during configuration in Adobe Experience Manager as a Cloud Service and outlines steps to resolve the issue.
Description description
Environment
Adobe Experience Manager as a Cloud Service (AEMaaCS) (all versions)
Symptoms
When configuring log forwarding to Splunk in Adobe Experience Manager as a Cloud Service, the configuration pipeline fails when unsupported networking methods are used. Updating certificates, port numbers, or advanced networking settings doesn’t resolve the issue. Error messages in the pipeline logs don’t provide actionable details. This issue can occur in any environment where log forwarding is configured using unsupported methods.
Resolution resolution
Follow the steps below to resolve the issue:
- Confirm that log forwarding over VPN connections isn’t supported in Adobe Experience Manager as a Cloud Service. Only use supported networking methods for log forwarding.
- Ensure the Splunk endpoint is accessible from the Adobe Experience Manager as a Cloud Service environment without requiring a VPN connection. The endpoint, port, and protocol must match Splunk’s requirements and be reachable from the cloud environment.
- Validate that the certificates used for secure communication are valid and not expired.
- Review advanced networking configurations for any misconfigurations that could block connectivity.
- Refer to the official Adobe Experience Manager as a Cloud Service Log Forwarding documentation for supported configurations.
- If the issue persists after verifying the above, collect pipeline execution logs and configuration details, and contact Adobe Support for further assistance.
recommendation-more-help
experience-cloud-kcs-help-kbarticles