Hello, I’m connecting my application, to my Splunk Cloud trial using HTTP Event Collector. Trial instance: prd-p-5mr63.splunkcloud.com In HEC Global Settings: All Tokens is enabled. SSL is enabled. The port is 8088. From my application’s Docker container, both documented hostname variants fail DNS resolution with ENOTFOUND: http-inputs-prd-p-5mr63.splunkcloud.com http-inputs.prd-p-5mr63.splunkcloud.com The alternative hostname inputs.prd-p-5mr63.splunkcloud.com resolves, but port 8088 presents a certificate named SplunkServerDefaultCert, issued by SplunkCommonCA. TLS validation fails with SELF_SIGNED_CERT_IN_CHAIN, and the certificate does not match the hostname. Could you please: Confirm the exact HTTPS HEC endpoint for this trial? Confirm whether the instance is hosted on AWS or GCP? Check that HEC DNS and a valid server certificate are provisioned? I’m sending JSON events to /services/collector/event. Thank you.
... View more