Users reported that the Lamba was failing with uncaught exceptions. These exceptions turned out to be ClassCastExceptions related to the handling of OriginResponseTimeMillis. The exceptions were not manifesting in JUnit tests, but did appear when the code was executed as an AWS Lambda. The change also enables stack trace logging for uncaught exceptions.
Change also includes an update to README.md to reflect the fact that AWS no longer wants region in S3 bucket ARN and a spelling correction in a failing JUnit test.
Verified that JUnits work. Verified that Lambda runs successfully and Graylog server receives events.
Users reported that the Lamba was failing with uncaught exceptions. These exceptions turned out to be ClassCastExceptions related to the handling of OriginResponseTimeMillis. The exceptions were not manifesting in JUnit tests, but did appear when the code was executed as an AWS Lambda. The change also enables stack trace logging for uncaught exceptions.
Change also includes an update to README.md to reflect the fact that AWS no longer wants region in S3 bucket ARN and a spelling correction in a failing JUnit test.
Verified that JUnits work. Verified that Lambda runs successfully and Graylog server receives events.
Related Issue: https://github.com/Graylog2/graylog-s3-lambda/issues/9