Realise the value of data with Splunk
summary
Splunk demonstrates concrete tooling to avoid ingesting everything: use Ingest Actions, Edge Processor or the Splunk-managed Ingest Processor to filter, redact, metrize logs and route raw data to Amazon S3 or Security Lake. Federated Search queries S3 via Glue catalog and SDselect; Federated Analytics caches 30‑day temporary indexes or performs federated queries against Amazon Security Lake. Data scale claim: ~175 zettabytes per year (visualised as reaching the Moon 23 times). GenAI cuts observability incident time from 40 minutes to 7 minutes and security investigations from hours to minutes.
AI-written summary · about
chapters (12)
- 0:00Introduction and welcome
- 1:51Data growth and visualization
- 4:03Data classification challenges
- 6:50Splunk data management overview
- 9:35Getting data in with Ingest Actions
- 13:31Edge Processor for scalable pipelines
- 15:35Ingest Processor for cloud management
- 17:42Free usage for Splunk customers
- 18:03Federated search for Amazon S3
- 21:15Amazon Security Lake integration
- 23:21Splunk AI capabilities
- 26:30Closing and call to action
related talks
20mData lake deep dive: Using accelerated indexing for threat detection
38mKeynote: The Evolution of Data Infrastructure at Splunk
30mRaw Data to Business Insights: What You Need to Build a Modern Data Lake
21mOptimize and manage data on Amazon S3
22mUse generative AI and Amazon Security Lake to enhance threat analysis
01h 33mSplunk as a Big Data Platform for Developers
38mGet the most out of Splunk Security, OCSF, and Amazon Security Lake
28mTurn Data Into Insights