Add support for CloudFront Lambda@Edge functions

[tolidano]

There are request parsing differences with CloudFront as the event is structured differently: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-event-structure.html

[jeremydaly]

This is something I've been thinking about for awhile. Thanks for the ticket.

[jeremydaly]

Moved the additional API Gateway input support to a new issue #69.

[jeremydaly]

Besides Lambda@Edge having a different input, it also has a different output depending on how it is invoked. Will need to do some more research on this. Any example use cases?

[tolidano]

Because of the time it takes to deploy a CloudFront distribution and the version requirement, it usually makes sense to do a lot of testing via API Gateway first and once ready for the optimal runtime, push to the edge.

We repeatedly used this during testing some edge Lambdas.

On Nov 15, 2018, at 4:47 PM, Jeremy Daly [email protected] wrote:

Besides Lambda@Edge having a different input, it also has a different output depending on how it is invoked. Will need to do some more research on this. Any example use cases?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[jeremydaly]

Some docs/notes on this:

• Generating HTTP Responses in Request Triggers
• Lambda@Edge Example Functions

Lots to work through with this, so bumping to the next release.