On October 30, 2022, all 1.2.x versions of the Splunk Data Stream Processor will reach its end of support date. See the Splunk Software Support Policy for details.
Connecting Amazon Kinesis Data Streams to your DSP pipeline as a data destination
When creating a data pipeline in the , you can connect to Amazon Kinesis Data Streams and use it as a data destination. You can get data into a pipeline, transform it, and then send the transformed data to a Kinesis data stream.
To connect to Kinesis as a data destination, you must complete the following tasks:
- If the stream that you want to send data to does not already exist in your Kinesis instance, create it. For information about creating a stream, search for "Creating a Stream" in the Amazon Kinesis Data Streams Developer Guide.
If you try to send data to a stream that does not already exist, the pipeline will fail to send data to Kinesis after retrying the operation several times.
- Create a connection that allows DSP to send data to your Kinesis data stream. See Create a DSP connection to Amazon Kinesis Data Streams.
- Create a pipeline that ends with the Send to Amazon Kinesis Data Streams sink function. See the Building a pipeline chapter in the Use the Data Stream Processor manual for instructions on how to build a data pipeline.
- Configure the Send to Amazon Kinesis Data Streams sink function to use your Kinesis connection and send data to an existing stream. See Send data to Amazon Kinesis in the Function Reference manual.
When you activate the pipeline, the sink function starts sending data from the pipeline to the specified Kinesis data stream.
If your data fails to get into Kinesis, check the connection settings to make sure you have the correct credentials and Amazon Web Services (AWS) region for your Kinesis data stream.
Connecting Amazon Kinesis Data Streams to your DSP pipeline as a data source
Create a DSP connection to Amazon Kinesis Data Streams
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.0, 1.2.1-patch02, 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1