Non-proxy API integration with Java Lambda fails when error message contains newline characters

See discussion in https://stackoverflow.com/questions/61474701/aws-api-gateway-integration-response-lambda-error-regex-fails-matching-when-re/72107597#72107597

To summarise, given an API Gateway non-proxy (also know as HTTP I think) integration with a Java 8 Lambda, if the lambda handler throws an Exception but the error message in the Exception contains new line characters then the returned JSON from the API is invalid (missing required double quote characters) and doesn't match response patterns so gets the default status code (in my case 200).

I'd really like to see this fixed as it is an annoying bug in AWS non-proxy integration that should be pretty easy and obvious to fix.

Can this be passed to the appropriate team for fixing please?