Getting Data In

How do I fix AWS Lambda HEC error when parsing?

lavster
Path Finder

I wonder if someone can help, we are getting the following error when trying to send data into Splunk, this previously worked but now we cant seem to get it working at all,  I have tried to curl the event manually and it succeeds, which is even stranger. The error message is

token name=xxxx, channel=********* source_IP=******, reply=6, events_processed=0, http_input_body_size=101493, parsing_err="While expecting event object to start: Unexpected character while looking for value: 'E', totalRequestSize=101493"

the event we are trying to send looks like this

{
    "time": 1663679182,
    "host": "test-sandbox",
    "source": "aws/lambda",
    "sourcetype": "aws:lambda",
    "index": "xxx-xxx",
    "event": {
        "message": "2022/09/20 14:06:22 node=test-sandbox Starting to move cantabm_testfile-9.zip from c21-metadata-dropzone-sandbox to c21-metadata-dest-sandbox/Metadata/cantabm_testfile-9.zip\n",
        "account": "11111111111"
    }
}

Labels (1)
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...