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.
Configure connections to external services
In order to connect the Splunk Data Stream Processor to an external service, you must create a connection with the appropriate connector and then use the connection in your data pipeline. Each connector lets you use a specific external service as a data source, or a data destination, or both.
Currently, you can use the following connectors to access an external service as a data source:
- The Amazon CloudWatch connector
- The Amazon Metadata connector
- The Amazon S3 connector
- The Apache Pulsar connector
- The Microsoft Azure Monitor connector
- The Google Cloud Monitoring Connector
- The Connector for Google Cloud Pub/Sub
- The Microsoft 365 connector
You can use the following connectors to access an external service as a data destination:
- The Write Connector for Amazon S3
- The Connector for Splunk Observability
- The Splunk Enterprise Connector
Connections from the following connectors can be used to reach both data sources and data destinations:
- The Connector for Amazon Kinesis Data Streams. See the following:
- The Connector for Microsoft Azure Event Hubs. See the following:
- The SSL Connector for Kafka and the No-Authentication Connector for Kafka. See the following:
Cluster configuration options | Data retention policies |
This documentation applies to the following versions of Splunk® Data Stream Processor: 1.2.1, 1.2.2-patch02, 1.2.4, 1.2.5, 1.3.0, 1.3.1
Feedback submitted, thanks!