What
When handling logs with non-ASCII information, the splunk-cloudwatch-logs-processor lambda blows up
Why
This is because it is trying to read the event string using the ASCII encoding
https://github.com/splunk/splunk-aws-serverless-apps/blob/master/splunk-cloudwatch-logs-processor/index.js#L46
Quick Fix
A quick fix for this is to instead use utf-8 encoding when reading the AWSevent
Reproducing this issue
- base64 decode the sample event
- add some Chinese characters to one of the messages
- base64 encode sample event
- run integration test
- observe test failure