AWS Lambda corrupts image buffer - Serverless Framework - node.js

Question

I'm having an issue where AWS lambda is corrupting my image buffer when I try and send it to a discord webhook. It works locally with SLS Offline and I can see image in discord channel with no issues, but when I deploy it to AWS I get
instead of the image itself. Looking around at similar people with this issue I've tried adding to my serverless.yml
plugins:
- serverless-apigw-binary
with apigwBinary in custom path.
apigwBinary:
types: #list of mime-types
- 'image/png'
I also saw another post about adding AwsApiGateway under provider in serverless.yml like so
provider:
AwsApiGateway:
binaryMediaTypes:
- 'image/png'
When I console.log('Sending Buffer', buffer); the buffer to make sure it's actually there in cloudwatch I see
Sending Buffer <Buffer fd 50 4e 47 0d 0a 1a 0a 00 00 00 0d 49 48 44 52 00 00 04 fd 00 00 02.... 162236 more bytes>
So the buffer is definitely making it to the lambda, but it gets corrupted when it makes it to discord. But again it does work locally with no issues. So Lambda is corrupting it somehow. I even tried adding a 3 second delay to see if that might fix it as if it was a race condition or something even though I can see buffer in console log, but nope.
webhook.send({
files: [{
attachment: buffer,
name: newFileName
}]
})
.then((res) => {
console.log('FINISHED', res);
});
}
catch (e) {
console.log('ERROR', e);
}
How can I get the image buffer to make it to discord as an image and not be corrupted. I appreciate any help!

Answer 1

Have you tried setting the Content-Type header of the HTTP response to 'image/png' ?
.then((res) => {
console.log('FINISHED', res);
return {
statusCode: 200,
headers: {
'Content-Type': 'image/png'
},
body: ''
};
})