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 strategyHow to start experimenting with controlled failure locally, before it happens in the wildReal-world examples of chaos experiments that catch bugs you'd never find in traditional testingTools and techniques to get started without blowing up your infrastructureThrough 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.

Cloud infrastructure has fueled innovation for nearly two decades—yet cost control remains a challenge. Unforeseen expenses and complicated billing can hamper agility, forcing teams to overspend just to stay competitive.What if you could evaluate costs in real-time, identify inefficiencies, and optimize deployments—without slowing development? Imagine adjusting parameters based on on-the-fly estimates and usage.In this presentation, Malcolm Matalka, Co-founder and CTO of Terrateam, explores how OpenInfraQuote, a new open-source command-line tool, transforms Terraform and OpenTofu code into actionable cost insights. Learn how to automate price checks, compare scenarios, and avoid financial surprises—alongside how it differs from other solutions and how to integrate it into your workflow.Resources- GitHub: https://github.com/terrateamio/openinfraquote- Documentation: https://openinfraquote.readthedocs.io/en/latest/

Multi-account and multi-region compatibility enables users to manage and deploy resources across multiple AWS accounts and geographic regions. This functionality enhances the robustness of the deployments by offering improved fault tolerance, scalability, and regulatory compliance. By segregating resources into separate accounts and distributing them across various regions, users can minimize the impact of potential failures and optimize performance.In this session from LocalStack Community Meetup May '24, Sannya Singhal discussed how you could use LocalStack to emulate multi-account and multi-region environments locally for testing and development purposes, ensuring that applications were resilient and scalable before deployment to the cloud.

LocalStack's cloud emulator lets you run Amazon Elastic Container Service (ECS) clusters and tasks on your local computer. It's sometimes useful to mount code from the host filesystem directly into the ECS container. This helps quickly test changes without needing to rebuild and redeploy the ECS Task's Docker image each time.This video explains how to use code mounting with the ECS bind mounts feature. Here are the links to the resources mentioned in the video:• Sample repository: https://github.com/localstack-samples/ecs-code-mounting-python-cdk• LocalStack Docs: https://docs.localstack.cloud/user-guide/aws/ecs/#mounting-local-directories-for-ecs-tasks• AWS Docs: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/bind-mounts.html