For one-off tasks, AWS Lambda really can be incredibly easy. You write a few lines of code, deploy it, and you have a function running in the cloud ready to respond to events, scale automatically, and that only costs you pennies.But as your application grows, so does some necessary complexity. When a few one-off functions become a full serverless backend architecture made up of interconnected services, you’ll need to pay careful attention to best practices to ensure that your application is easy to debug, maintain, and scale.That’s where AWS Powertools for Lambda fits in. It’s a suite of reusable utilities designed to simplify bringing best practices around things like logging, tracing, metrics, idempotency and more to your Lambda functions with minimal effort.This demo session will dive into some of the functionality provided by the AWS Powertools (TypeScript) core libraries, such as:Encapsulating best practices into reusable libraries for structured logging, metrics collection, idempotency, and more.Leveraging Middy middleware to integrate common cross-cutting concerns, such as injecting Lambda context or automatically flushing metric.Enabling local testing with LocalStack, allowing you to deploy and debug Lambda functions with structured logs, trace data, and embedded metrics.Providing modular examples that can be deployed to AWS or LocalStack with ease, enabling developers to explore libraries.

You’ve been there: Your Unit tests pass both locally and in CI. You deploy with confidence. You thought.. Then staging in the real cloud reveals the truth—bugs that only show up with actual RDS parameter settings, real SQS and SNS throughput limits, or Lambda and API Gateway behaviour your local mocks never captured.
The solution is Testcontainers.
Testcontainers is a testing library that provides easy and lightweight APIs for bootstrapping integration tests with real services wrapped in Docker containers. Using Testcontainers, you can write tests talking to the same type of services you use in production without mocks or in-memory services. Spin them up, run migrations, execute your Node.js service against them, assert results, auto-cleanup.

So many of the challenges that slow down software development stem from the fact that early-stage dev & test cycles are performed in cloud environments.
Local cloud development removes these challenges.
By simulating AWS application behavior in a local container, the local cloud enables developers and agents to validate the security, quality, and reliability of their applications faster and more effectively than they can on the cloud.

Silvio and Carole introduce lstk, LocalStack's next-generation CLI built from scratch in Go. They explain why the team rebuilt the CLI, walk through its key features — zero-config startup, seamless browser-based authentication, and a rich interactive TUI that surfaces real-time progress and actionable errors — and demo how lstk gets you from install to a running emulator in seconds. They also dive into the architecture behind lstk and how it is designed to support multiple emulators, flexible runtimes, and deep integrations with CI pipelines and IDEs.