Splunk Cloud HTTP Event Collector (HEC) accepts JSON and raw event streams exclusively over HTTPS port 443 in production. Port 8088 is used only on Splunk Enterprise or Splunk Cloud free trial stacks.
Pay close attention to DNS naming differences across cloud providers. On AWS stacks, standard HEC uses a hyphenated prefix (https://http-inputs-<stack>.splunkcloud.com:443/services/collector/event), and AWS Kinesis Data Firehose uses http-inputs-firehose-<stack>.splunkcloud.com. On GCP and AWS GovCloud stacks, HEC uses a dotted prefix (https://http-inputs.<stack>.splunkcloud.com:443/services/collector/event).
Clients authenticate with the header Authorization: Splunk <hec_token>, and sender IPs must be permitted on the ACS hec IP allowlist. Enabling indexer acknowledgment (useACK=true) requires clients to supply an X-Splunk-Request-Channel header and poll the ack endpoint.
# AWS Splunk Cloud stack
curl -k "https://http-inputs-acme.splunkcloud.com:443/services/collector/event" \
-H "Authorization: Splunk $HEC_TOKEN" \
-d '{"event":"deploy_ok","sourcetype":"ci:deploy"}'
# GCP or AWS GovCloud stack (note dot after http-inputs)
curl -k "https://http-inputs.acme.splunkcloud.com:443/services/collector/event" \
-H "Authorization: Splunk $HEC_TOKEN" \
-d '{"event":"deploy_ok","sourcetype":"ci:deploy"}'