Getting Data In

splunk-kinesis-stream-processor Lambda timeouts

iamkuba
New Member

Hello,

We're trying to use the Splunk provided Lambda application splunk-kinesis-stream-processor (from Serverless Application Repository):

https://github.com/splunk/splunk-aws-serverless-apps/tree/master/splunk-kinesis-stream-processor

We're using CW Events to catch events and send them to Kinesis and Splunk HEC endpoint via mentioned Lambda processor (we can't use Firehose Delivery Stream to Splunk, as Firehose does not support PrivateLink at the moment).

Our problem is that this Lambda function times out without any errors in the CW Logs. The Lambda runs inside the VPC, as Splunk HEC endpoint is behind NLB (VPC Endpoint Service). We're using Splunk Enterprise 6.5 (trial license for the moment). EC2 instance running in the same VPC can successfully send events to the HEC endpoint. Another Lambda function with the same settings (IAM role, VPC subnets + SG) can also run a curl subprocess successfully.

Thanks in advance for any ideas and your help.

Cheers,

Jakub

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!

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...