Connecting Amazon S3 to your DSP pipeline as a data destination
When creating a data pipeline in the , you can connect to Amazon S3 and use it as a data destination. You can get data into a data pipeline, transform it, and then send the transformed data to an Amazon S3 bucket.
To connect to Amazon S3 as a data destination, you must complete the following tasks:
- If the bucket that you want to send data to doesn't already exist in your Amazon S3 instance, create it. Don't include any periods ( . ) in the bucket name. For information about creating an S3 bucket, search for "How do I create an S3 Bucket?" in the Amazon Simple Storage Service Console User Guide.
If you try to send data to a bucket that doesn't already exist, or to a bucket that has a period ( . ) in its name, the pipeline fails to send data to Amazon S3 and restarts indefinitely.
- Create a connection that allows DSP to send data to your Amazon S3 bucket. See Create a DSP connection to send data to Amazon S3.
- Create a pipeline that ends with the Send to Amazon S3 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 S3 sink function to use your Amazon S3 connection and send data to an existing S3 bucket. See Send data to Amazon S3 in the Function Reference manual.
- If you're planning to send data to Amazon S3 in Parquet format, make sure to extract relevant data from union-typed fields into explicitly typed top-level fields. See Formatting DSP data for Parquet files in Amazon S3.
When you activate the pipeline, the sink function starts sending data from the pipeline to the specified S3 bucket.
If your data fails to get into Amazon S3, check the connection settings to make sure that you have the correct credentials for accessing Amazon S3.
Connecting Amazon S3 to your pipeline as a data source
Create a connection to get data from Amazon S3
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