Lambda Image Resizing

Lunch and Learn - April 2016

Transcript

1. WE DON’T NEED NO STINKING SERVERS IMAGE RESIZING WITH AWS LAMBDA
2. The Problem: For the last 6 years, users have been able to upload any image they like for use in a VizZle lesson 10144 × 8054 pixels 32.6 MB 980 DPI minutes to download
3. And the app would never show it at that resolution! Max Page Size: 1920 x 1080 414x329 915x686 944x708
4. Or the old app Flash “Card” Size: 520 x 390
5. The Solution: Batch convert all the images! Max Image Size 960x540 680x540 $ convert 1416855261.78270 -size x540
6. “How many images are there anyway?” –Hey Blinken
10. “Are you going to download every one from the internet?” –Al Gore
13. “What are we going to do with new uploads?” –Johnny Five
16. “Who is going to maintain that EC2 instance?” –Jeff Bezos
25. Or any binary compiled on Amazon Linux!
33. Read/Write S3 Role Type: AWS Lambda Attach Policy: AWSLambdaExecute
36. Lambda Interface
39. Deployment
40. Configuration
41. Testing
42. Testing
43. Testing
44. Image Resizing Gotchas Maintain Aspect Ratios Lossy vs Lossless Lossy vs Headless Lambda Inception ACLs
45. Image Resizing Gotchas Maintain Aspect Ratios Lossy vs Lossless Lossy vs Headless Lambda Inception ACLs
46. Lambda Gotchas Function runtime is limited to 5 minutes Maximum of 1.5GB memory Debugging involves waiting for CloudWatch logs to show up
47. “What else can we do with it?” –Jeff Bezos