Copilot said - Hi Javi, Yes, it’s possible to forward data from Splunk to third-party services like AWS EventBridge or Lambda, but it’s not a native feature out of the box. Splunk primarily ingests and indexes data, but you can achieve this forwarding through a few approaches: HTTP Event Collector (HEC) + AWS Integration Splunk can send data via HTTP Event Collector to an endpoint. You could set up an AWS API Gateway or Lambda function to receive these events and then route them to EventBridge. Splunk Add-ons or Apps There are Splunkbase apps and add-ons for AWS that can help with integration. For example, the Splunk Add-on for AWS is typically used for ingestion, but custom scripts or modular inputs can be adapted for forwarding. Custom Scripts / Modular Outputs Splunk supports custom alert actions or scripted outputs. You can configure Splunk to trigger a script whenever new data matches certain criteria, and that script can call AWS APIs to forward the data. Third-Party Middleware Some organizations use a message bus (like Kafka or Kinesis) as an intermediary between Splunk and AWS services for scalability and reliability. Summary: Splunk doesn’t automatically forward all ingested data to AWS, but with HEC, custom alert actions, or middleware, you can build a pipeline where Azure → Splunk → AWS EventBridge/Lambda works as you described. Would you like me to draft a step-by-step guide for setting up Splunk to forward data to AWS Lambda or EventBridge? Or should I prepare a diagram of the architecture for this flow?
... View more