Amazon Kinesis Data Firehose is unable to ingest data into Splunk via HEC.

Available Languages

Updated:September 29, 2026
Document ID:SPLK046779

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk Add-on for Amazon Web Services Splunk Enterprise Splunk Cloud

Description

The user has configured the Amazon Kinesis Data Firehose and created an HEC token on Splunk, but they are unable to ingest the data into Splunk.


Investigation

There are no error logs on the Splunk side, and the SPL query used was as follows:

index="_internal" HttpInputDataHandler sourcetype=splunkd "HEC token name"index="_introspection" sourcetype=http_event_collector_metrics| spath "data.token_name" | search "data.token_name"="HEC token name"
 

There is CloudWatch Log Groups have been created for the Kinesis Firehose, which include the destination error logs. so, requested the user to check if there are any destination error logs generated on the AWS side. The user can refer to the screenshot below from our lab environment and compare it with their own environment.

 







Resolution

 

  1. Verify that the HEC token added on the AWS side is correct.

  2. Create a new HEC token and enable indexer acknowledgment.

  3. Enable indexer acknowledgment on the currently used HEC token.



The issue was resolved after the user enabled indexer acknowledgment on the HEC token being used.




Troubleshooting Splunk for HEC

About HTTP Event Collector Indexer Acknowledgment

Revision History

Revision Publish Date Comments
1.0
29-Sep-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products