Aws Re:invent 2025 - The Bill Shock That Taught Me Cost...

🦄 Making great presentations more accessible. This project aims to enhances multilingual accessibility and discoverability while maintaining the integrity of original content. Detailed transcriptions and keyframes preserve the nuances and technical insights that make each session compelling.

📖 AWS re:Invent 2025 - The bill shock that taught me cost optimization (DEV208)

In this video, Rejoice, a technical lead at Intelligi, shares how a $86 daily Lambda function cost taught her FinOps optimization. She explains that this single function accumulated over $31,000 annually due to idle wait time while calling Transcribe and Comprehend. Through Lambda Power Tuning, right-sizing memory allocation, breaking monolithic functions into smaller handlers, and optimizing log retention strategies, her team achieved a 97.7% cost reduction to under $730 per year. She provides actionable advice: audit Lambda functions in Cost Explorer, use AWS Lambda Power Tuning tool, set up cost alerts in AWS Budgets, and log only essential identifiers rather than full payloads.

; This article is entirely auto-generated while preserving the original presentation content as much as possible. Please note that there may be typos or inaccuracies.

Alright, hello everybody. It's good to see you all. Thank you so much for coming. You guys look tired. Are you tired? Wow, alright, cool. Let's get to it. I know there's a party next door, so let's just try to stay here. Okay, cool.

As I was introduced, my name is Rejoice. I'm a technical lead at Intelligi, which is a fintech startup in South Africa. All the way from South Africa, we're saying hello, Las Vegas. Right now I want to take you through some very interesting things. I think the title of my talk is "The Bill Shock that Taught Me Cost Optimization." This is something more around learning experiences and what we did with what we learned to sort of get into the space of FinOps.

When we think about the bill shock, I know you're probably thinking, how much did she have? Not a big number, right? Yeah, I know you're thinking, come on, Rejoice, $86? Really? Are we sitting here for $86? You're under $100. What? Is this a bill shock? Alright, I'm going to tell you why it is a bill shock. Firstly, this was a cost for just one Lambda function per day. Is it starting to, are you seeing it? So what this means is this number got burned in my head because the more I had to work around it, the more I learned how to optimize costs.

For today, on

Source: Dev.to