The AI Cloud Engineers

The AI Cloud Engineers

5 Lambda Cost Mistakes I See Teams Make (And How to Fix Them)

Lefteris Karageorgiou's avatar
Lefteris Karageorgiou
Dec 24, 2025
∙ Paid

Lambda’s pay-per-use model sounds simple: you pay for what you use. But after reviewing dozens of AWS bills with teams, I’ve found that “what you use” is often far more than “what you need.”

Here are the five most expensive mistakes I see repeatedly—and how to fix them.

Thanks for reading The Cloud Engineers! Subscribe for free to receive new posts and support my work.

Mistake #1: Using the Default 128MB Memory

This is the most common mistake, and it’s counterintuitive: allocating more memory can actually lower your bill.

Many teams deploy Lambda functions with the default 128MB memory allocation, thinking they’re being cost-conscious. The problem is that Lambda allocates CPU power proportionally to memory. At 128MB, your function gets a tiny slice of CPU, which means slower execution times.

Lambda pricing is calculated by multiplying the memory allocated by the execution time by the price per GB-second. If doubling your memory cuts execution time by more than half, you save money.

The Fix

Us…

User's avatar

Continue reading this post for free, courtesy of Lefteris Karageorgiou.

Or purchase a paid subscription.
© 2026 Lefteris Karageorgiou · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for writing, podcasting, and media founders.