How the destination for Ingest Processor works
In order to send data from an Ingest Processor to a storage location such as an index, or Splunk Observability Cloud, you must define the location as a destination. Each destination contains the connection information necessary for allowing Ingest Processor to send data to a given location.
The steps for adding a destination to the Ingest Processor service varies depending on whether the destination is part of the Splunk Cloud Platform deployment that's connected to your cloud tenant, as well as the specific Splunk Cloud Platform version that your deployment is running:
- When you connect your tenant to a Splunk Cloud Platform deployment as part of the first-time setup of the Ingest Processor solution, all the indexes that the service account can access become available as destinations. For information about working with destinations that are associated with this connection, see Send data from Ingest Processors to the Splunk Cloud Platform deployment connected to your tenant.
- To send data to Splunk Observability Cloud, or to send data to Amazon S3 when using Splunk Cloud Platform version 10.3.2512 or lower, you must use the Destinations page in the Ingest Processor service to add and configure destinations. See the following pages for more information:
-
To send data to Amazon S3 or Microsoft Azure when using Splunk Cloud Platform version 10.4.2604 or higher, you must create a connection and dataset in the Data Management app. See the following pages for more information:
You can confirm the destinations that are available by checking the Destinations page in the Ingest Processor service, and view additional details about a given destination by selecting it.