Getting Data In

Best AWS ingestion approach

oleg106
Explorer

Hello,

I am trying to settle on a new AWS event collection strategy.  We are currently collecting using the older pull (SQS/SNS) method, and would like to move to a more modern and flexible way of doing it.  Would like to collect AWS Config, CloudTrail, VPC Flow logs, CloudWatch, GuardDuty events from 100+ accounts into Splunk.  Also would like a filtering capability at the source where logs can be discarded based on some criteria (account or arn) and not sent to Splunk to be filtered.   

Seems like Splunk has changed their recommendations in the last few years (lambda push, firehouse, etc)_, and I am not certain what is the recommended approach now to do this now with as little complexity as possible.  Project Trumpet seems like a good option, but  I am not seeing Splunk steer people to that.   Also unclear what caveats are with each of these approaches.  If you go the Firehose route, how do you discard unwanted events?  Also there are cost considerations and it's unclear which approach is more cost effective.

Wondering what people have settled on in similar circumstances and why.  Thanks!

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...