
An agent will write you a CDK stack, a Terraform module, or a stack of IAM policies in seconds.
Whether any of it works is a separate question, and the usual way to find out is to deploy to a real AWS account and watch what breaks.
In an agentic workflow, that means giving AI access to a public cloud account, racking up costs on the AWS bill, and waiting for provisioning to complete every time you push new code to the environment.

When it comes to productivity, developer experience is more than just a buzzword. Creating an intuitive developer experience could help you get more out of LocalStack by democratizing access, cutting out manual tasks, and making environments more easily interchangeable between LocalStack and AWS. On a day-to-day basis, this could mean fewer tickets, less time spent creating environments, and more time on the important work that your environments support. This demo session will show how LocalStack’s new integration with Quali Torque can accelerate deployment on both LocalStack and AWS by using generative AI to create reusable environment templates that can be deployed to LocalStack and AWS interchangeably in just a few clicks, providing a self-service catalog for your teams to find and provision environments quickly and easily without access to create or modify resource configurations, simplifying the deployment experience by eliminating complexity and security requirements to run environments on AWS, and tracking all activity to identify performance issues for LocalStack deployments and wasted cloud costs for AWS deployments proactively.

Most people think the cloud is just files floating in the sky. Spoiler: it's not. In this episode, I’m breaking down what “the cloud” really is, why everything you’ve been told is probably wrong, and why it's the engine behind everything from Netflix to AI to your online checkout. This is the kickoff to WTH is the Cloud?! a fun series that makes cloud technology make sense.

Ever wonder why some teams intentionally break their own systems? Welcome to the world of chaos engineering — a practice that's not just for Netflix-scale infrastructure, but for any team that wants to build resilient, reliable applications. In this session, we'll demystify chaos engineering and explain why intentionally breaking things is actually the smart move. You'll learn what chaos engineering really is (in plain English, no buzzwords), why waiting for production failures is a terrible strategy, how to start experimenting with controlled failure locally, before it happens in the wild, real-world examples of chaos experiments that catch bugs you'd never find in traditional testing, and tools and techniques to get started without blowing up your infrastructure. Through practical demos using LocalStack's cloud emulation and chaos engineering tools, we'll simulate failures like network latency, service outages, and resource exhaustion right from your laptop. If you've ever said "it worked on my machine" only to watch it crash in production, this talk is for you—let's break things intentionally so they don't break unexpectedly.