AWS Lambda – Best practices

Re:AWS Lambda – Best practices by throwaway2016a on Thursday March 02, 2017 @10:21AM (#13774611)

Binary data is tricky with Lambda proxy (and by tricky I mean... I haven't gotten it to work). But I also haven't tried much. Typically best practice for me has been:

- When dealing with uploads have an API call to get a pre-signed S3 upload URL

- When dealing with downloads using HATEOAS and/or the Location header to send the client to S3 to grab the actual file.

It requires some client-side designing around eventual consistency but it works well and is very scalable.

[ Parent | on HN ]

Re:AWS Lambda – Best practices by breandr on Thursday March 02, 2017 @12:44PM (#13776252)

You need to specify your MIME type (most commonly, application/json) to be treated as binary (from console: API -> Binary Support). In your Lambda function: `callback(null, { body: base64EncodedBody, status: 200, headers: {}, isBase64Encoded: true })`

[ Parent | on HN ]

Re:AWS Lambda – Best practices by wiredfool on Thursday March 02, 2017 @04:16PM (#13778304)

The mimetype of the response from lambda? Or the mimetype in the headers?

[ Parent | on HN ]