What can you do with AWS Lambda@Edge, exactly? Alex will discuss the most interesting use cases and a few preview-related limitations. You will learn how to execute serverless functions at CloudFront's Edge Locations to implement unique functionalities and optimize network latency.
11. CloudFront Triggers
Viewer Request
Viewer Response
Origin Request
Origin Response
Before cache hit/miss
A8er cache hit/miss
Only if cache miss, before forwarding
Only if cache miss, a8er forwarding
clda.co/lambda-‐edge-‐sea.le
12. Benefits and use cases
Use cases categorisa@on and analysis
clda.co/lambda-‐edge-‐sea.le
13. AWS Lambda@Edge Use cases
Request/Response manipulaQon
Dynamic content generaQon
Pure latency opQmizaQon
clda.co/lambda-‐edge-‐sea.le
14. 1. Request/Response manipulaPon
Custom HTTP headers
Adapt to client capabiliQes
Add Qmezone-‐related info
A/B tesQng
URL rewriQng / redirects
EncrypQon at the Edge
clda.co/lambda-‐edge-‐sea.le
15. 2. Dynamic content generaPon *
Custom error pages
Custom signup forms
Opzimized JS code (Polyfill.io)
Dynamic HTML
* Never hit the origin!
clda.co/lambda-‐edge-‐sea.le
16. 3. Pure latency opPmizaPon *
401 errors (if missing auth)
Edge-‐based logging
Custom data validaQon
Custom data transformaQon
* Assuming dynamic origin
clda.co/lambda-‐edge-‐sea.le
17. Preview & GA
What about Preview limita@ons, GA, and pricing?
clda.co/lambda-‐edge-‐sea.le
18. LimitaPons (preview only)
Max 50ms
Only 128MB (RAM)
Only 1MB of code
Only Node.js 4.3
Programming model Only 1 trigger
clda.co/lambda-‐edge-‐sea.le
19. LimitaPons (permanent)
Cold starts
Only Node.js
No VPC
No API Gateway distribuQons
Slow propagaQon (~5min)
No real-‐Qme logging
clda.co/lambda-‐edge-‐sea.le
No DLQ Explicit HTTP convenQons
20. General Availability (soon!)
HTTP calls / AWS SDK
Dynamic Content!
Be.er (3rd-‐party) monitoring
More RAM, Qme, and storage
clda.co/lambda-‐edge-‐sea.le
MulQple triggers Be.er LocaQon awareness