I followed this documentation on setting this up: https://aws.amazon.com/blogs/mt/ingest-aws-config-data-into-splunk-with-ease/
We are on Splunk Enterprise 7.1.3.
Sometimes our data is parsed properly, but I've noticed that on many occasions multiple events get forwarded to HEC and HEC can't properly parse them. These multiple events end up as just raw input in splunk when I need splunk to intelligently parse this info.
I have setup a lambda function on my kinesis stream so I can manually parse this, I'm also considering splitting the records up and making sure only one record gets forwarded to Splunk at a time and then I'll throw the extra messages back into the kinesis stream but that feels like a really bad hack. Not sure what I can do to fix this, has anyone else had this issue and have a solution?
