Cedric is a Senior Splunk Consultant at SP6, specializing in Splunk architecture, administration and data input. His experience spans all major Splunk use cases, including IT Operations, IT Service Management, and Security, DevOps. Cedric's accreditations include Splunk Certified Consultant II, Splunk Core Implementation, Splunk Enterprise Security (ES) Implementation, Splunk IT Service Intelligence (ITSI) Analyst, and Implementation Amazon Web Services Certification Architect-Associate. Prior to joining SP6, Cedric was also a ITSM Architect/Engineer, providing event, fault, monitoring, asset, change, incident and performance management and business analytics architected and integrated with tools (Splunk, CA, HP, BMC, ServiceNow), etc.
Blog
Question mark in crystal ball

AWS Lambda vs AWS Firehose

Splunk has multiple methods in regards to Getting Data In (GDI). One very popular method is the Http Event Collector (HEC). The use of the HEC allows data ingestion into Splunk via HTTP POST messages. Two popular methods that send POST messages out of AWS into Splunk are the AWS services: Lambda and Firehose.

Blog
Cloud illustration with connected devices

Logging Cloudwatch Events

Logging for Cloudwatch Events using Splunk HEC Welcome to another installment on how to log multiple AWS accounts into Splunk, when the recommended method is not feasible. In this article we will take a look at Splunking AWS Cloudwatch Event data using an HTTP Event Collector (HEC) input.