Deployment Architecture

AWS Cloudwatch Logs to Splunk Ingestion

AmithB
Engager

We have Splunk Heavy Forwarder running in a couple of different regions/accounts in AWS.

We need to ingest the CloudWatch Logs into Splunk Heavy Forwarder. And the architecture proposed is as follows

CloudWatch Logs (multiple accounts) >> Near-real time streaming through KDF >> S3 Bucket (Centralized bucket) >> (SQS) >> Splunk Heavy Forwarder.

We are looking for a implementation document mainly for aggregating CloudWatch logs to S3 (from multiple accounts) and to improve the architecture. Direct ingestion from CloudWatch logs or KDF to Splunk is not preferred.  S3 centralized logging is preferred.

We would like to reduce management overhead (hence don't prefer managing lambdas unless we have to), and also be cost effective.

Kindly include implementation documentation if available.

Labels (2)
0 Karma
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL

Splunk AI Assistant for SPL | Key Use Cases to Unlock the Power of SPL  The Splunk AI Assistant for SPL ...

Buttercup Games: Further Dashboarding Techniques (Part 5)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...

Customers Increasingly Choose Splunk for Observability

For the second year in a row, Splunk was recognized as a Leader in the 2024 Gartner® Magic Quadrant™ for ...