Hi @georhe6,
It seems Adobe is successfully reaching your Splunk instance, but the endpoint path or token is not being accepted, leading to a 404 Not Found error.
Please double check
1. Correct Splunk cloud HEC host format
For Splunk Cloud, the HEC endpoint host usually looks like:
http-inputs-<your-splunk-instance>.splunkcloud.com
NOT just org.splunkcloud.com
So update:
host: "http-inputs-org.splunkcloud.com"
Replace org
with your actual Splunk account prefix.
You can confirm the correct HEC URL from Splunk under:
2. Check HEC token
Ensure:
-
Token is enabled
-
Enable Indexer Acknowledgment
is optional but can help with tracking
-
Token has permissions to write to the index
you configured (e.g., name_aem
)
3. Test Token from Local cURL (Optional)
curl -k https://http-inputs-<your-prefix>.splunkcloud.com:443/services/collector/event \
-H "Authorization: Splunk <YOUR_TOKEN>" \
-d '{"event": "test event from Adobe"}'
You should get a {"text":"Success","code":0}
response.
Updated working example
kind: "LogForwarding"
version: "1"
metadata:
envTypes: ["dev"]
data:
splunk:
default:
enabled: true
host: "http-inputs-org.splunkcloud.com"
port: 443
token: "${{SPLUNK_HEC_TOKEN}}"
index: "name_aem"
Replace "http-inputs-org.splunkcloud.com"
with your actual Splunk Cloud endpoint prefix.
Santosh Sai

