Money-saving tips for the frugal serverless developer
summary
Uses concrete fixes: enable billing alarms early, stop Secrets Manager calls per invocation that spiked costs, set CloudWatch retention to ~30 days and sample debug logs, and use Lambda extensions with the Telemetry API to avoid double ingestion by CloudWatch. Right-size memory with the power tuning tool — a video encoder drops from $10k/month to 10% of that by cutting from 10 GB to 1.8 GB until code is multicore aware. Avoid synchronous Lambda→Lambda calls, add caching and increase Route 53 TTL to reduce DNS charges.
AI-written summary · about
chapters (9)
- 0:00Introduction to frugal serverless
- 1:15Cost-saving with billing alarms
- 3:01Reducing CloudWatch log costs
- 8:54Optimizing Lambda memory settings
- 17:27Lambda to Lambda invocation costs
- 24:50Architecture simplification tips
- 30:04Choosing cost-efficient AWS services
- 36:01When to avoid API Gateway
- 42:20Q&A on cost visualization
related talks
42mServerless Systems That Won't Burn a Hole in Your Pocket
42mBest practices for serverless developers
58mServerless: Five Key Things you need to Know
53mBottlenecks in Serverless Applications- 42mServerless Systems That Won't Burn a Hole in Your Pocket
42mServerless Tales from the Trenches
19m(N+1) Lessons I learned about serverless
46mServerless Architecture Patterns and Best Practices