How we 10x Our Lambda@Edge Development Speed 🚀


AWS FOR THE REAL WORLD
⏱️
Reading time: 10 minutes
🎯
Main Learning: Building and testing Lambda@Edge functions with CloudFront is complicated, as deployments can take up to 10 minutes. With LocalStack, you can build, test, and debug your Lambda@Edge functions locally!
📝

Hey Reader 👋🏽

Happy new year! We hope you had a great time with your families and loved ones 😊

We took some time off. Sandro is bridging the cold winter in Thailand (say hi if you're here!) and Tobi started working with a new client project this year. Finally, some HUGE AWS scale again - hopefully we can talk more about that in the future 👀

We don't have any AWS news for you this time. Nothing exciting came out - if you've found something, share it with us!

In this issue, we talk about CloudFront and Lambda@Edge deployments.

Rather watch a video? We've recorded one for you!

Lambda@Edge functions are great for things like:

  • Request forwarding
  • URL rewriting
  • A/B testing

In theory they're powerful. But building and debugging them is a pain. This is what this deep dive is about 👆🏽

video preview

Note: This issue is not sponsored by LocalStack. But we love the tool + the founders. Here's how we've used it for this use case.

Let's get into it!

Cover

📚 This Week's Deep Dive

The Problem: 10-Minute Deployments for Every Change

Lambda@Edge functions are powerful. But debugging them is painful. Even in 2025.

Every change triggers a CloudFront deployment. That's up to 10 minutes of waiting. One typo? Another 10 minutes. Wrong header name? Another 10 minutes.

The Solution: LocalStack for Lambda@Edge

LocalStack lets you run CloudFront and Lambda@Edge locally. Change your function, redeploy in seconds. No waiting. No risk of breaking production.

The video walks through the full setup: LocalStack CLI, creating distributions via awslocal, attaching Lambda@Edge functions, and iterating on custom response headers.

🎬 Watch the Full Tutorial →

Prefer reading? Read the blog post instead

Have you used Lambda@Edge or CloudFront Functions before? If you need more information about CloudFront, here's our infographic!

Our topics for the next weeks:

  • Generating diagrams with Kiro & AI
  • How to save Lambda costs

All of them will come with videos as well!

Have a great start of the year and see you soon!

Sandro & Tobi

PS: Here's a snapshot from Thailand 😊

AWS for the Real World

We teach AWS for the real world - not for certifications. Join more than 10,500 developers learning how to build real-world applications on AWS.

Read more from AWS for the Real World

AWS FOR THE REAL WORLD ⏱️ Reading time: 5 minutes 🎯 Main Learning: How to make Claude write production-ready Terraform instead of technical debt 🎬 Watch on YouTube 📝 Blog Post 💻 GitHub Repository Hey Reader 👋🏽 We've been heads-down the past weeks. Preparing the live AMA workshops from Black Friday (sorry for the delay!) and recording new YouTube videos. It's been a lot of fun. Speaking of videos - this week Tobi recorded one you'll want to watch. Here's the problem: LLMs want to close the...

AWS FOR THE REAL WORLD ⏱️ Reading time: 8 minutes 🎯 Main Learning: 5 practical techniques to cut Lambda costs (memory, timeouts, ARM, batching, caching) 📝 Blog Post 🎬 Watch on YouTube Hey Reader 👋🏽 Lambda bills can sneak up on you. One function is often not expensive. But then you scale it up and 💥 it costs you $5,000. Sounds familiar? We had this exact problem with our Shopify fraud detection app. Orders coming in via EventBridge, each triggering its own Lambda.And the bill was $150/month...

AWS FOR THE REAL WORLD ⏱️ Reading time: 8 minutes 🎯 Main Learning: Generate AWS architecture diagrams using AI with Kiro and MCP servers - skip the hours of dragging boxes in Lucidchart. 📝 Blog Post 🎬 Watch on YouTube Hey Reader 👋🏽 Big news: We launched our YouTube channel! 🎬 We've published 7 videos so far and are almost at 800 subscribers. Our goal is to keep a weekly rhythm, so expect fresh content every week. If you haven't subscribed yet, here's the link. No exciting AWS news this week....