Skip to content

Configure HTTP event collector for the Splunk Add-on for Amazon Web Services on a distributed Splunk Enterprise deployment



  1. Decide what index you want to use to collect your Amazon Kinesis Firehose data. Ensure that this index is enabled and active. Sending data to a disabled or deleted index results in dropped events. If you need to create a new index, see Create custom indexes in Managing Indexers and Clusters of Indexers.
  2. Set up the HTTP Event Collector on your distributed deployment. For instructions on how to configure the HTTP Event Collector and create a server class using the deployment server, see Scale HTTP Event Collector with distributed deployments. When you define the server class, specify all indexers that you want to use to collect Amazon Kinesis Firehose data.
  3. Enable the deployment server and push the configuration to the clients.
  4. On the deployment server, confirm that the Enable SSL box is checked in your HTTP Event Collector global settings.
  5. Create a new HTTP event collector token with indexer acknowledgments enabled. For a detailed walkthrough, see Create an Event Collector token in Getting Data In. During the token configuration:
    1. Specify a Source type for your incoming data. See Source types for the Splunk Add-on for AWS for the source types supported by this add-on.
    2. Select the Index to which Amazon Kinesis Firehose will send data.
    3. Check the box next to Enable indexer acknowledgement.
  6. Save the token that Splunk Web provides. You need this token when you configure Amazon Kinesis Firehose.
  7. Repeat steps 5 and 6 for each additional source type from which you want to collect data. Each source type requires a unique HTTP event collector token.

Next Step Configure Amazon Kinesis Firehose to send data to the Splunk platform