LocalStack Community Meetups & Webinars

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/

Terraform 1.6 introduced native Terraform tests, but running them against real cloud resources leads to long deployment times and unnecessary costs. With LocalStack's Terraform integration (tflocal), you can validate configurations locally while closely emulating real cloud behaviour. By combining Terraform tests with LocalStack, developers can run integration tests in CI/CD environments, test event-driven serverless workflows, and establish a rapid feedback loop for cloud development.In this presentation, Harsh Mishra provides a hands-on demo of Terraform testing with LocalStack, exploring how to configure tests, validate infrastructure locally, and reduce costs and complexity while improving confidence in deployments.## Resources- Blog: https://blog.localstack.cloud/efficient-infrastructure-testing-localstack-terraform-tests-framework/- Documentation: https://developer.hashicorp.com/terraform/language/tests- tflocal: https://docs.localstack.cloud/user-guide/integrations/terraform/#tflocal-wrapper-script

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—and without access to create or modify resource configurations.* Simplifying the deployment experience by eliminating complexity and security requirements to run environments on AWS.* Tracking all activity to identify performance issues for LocalStack deployments and wasted cloud costs for AWS deployments proactively.

Debugging serverless functions has always been challenging, often requiring repeated invocations, extensive log tracing, and cloud deployments to diagnose an issue. The new Lambda Debug Mode in LocalStack changes this by allowing developers to debug AWS Lambda functions directly in their IDE, with breakpoints, variable inspection, and step-through execution, without leaving their local environment.In this presentation, Marco Edoardo Palma provides a hands-on demo of Lambda Debug Mode—from debugging standalone functions to handling multi-function workflows. Learn how this developer-first approach makes debugging serverless applications faster, smoother, and more intuitive.## Resources- Documentation: https://docs.localstack.cloud/user-guide/lambda-tools/debugging/#lambda-debug-mode-preview- Samples: https://github.com/localstack-samples/localstack-pro-samples/tree/master/lambda-debug-mode

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.

LocalStack Chaos API enables you to simulate outages in any AWS region or service. Chaos API provides an easy way to implement chaos engineering experiments to test a wide variety of simulated outages and failures within your application safely, without impacting your production users.Common examples can include:- Region-wide outages- DNS failovers- Service failures- Network faultsAll the testing scenarios described above can be executed within LocalStack, providing thorough coverage for critical situations in a matter of minutes rather than hours or days.In this presentation by Viren Nadkarni, we explore how Chaos API is leveraged to perform service failures in a local environment while using robust error handling to address and mitigate such issues.## Resources- Documentation: https://docs.localstack.cloud/user-guide/chaos-engineering/chaos-api/- Get access: https://www.localstack.cloud/contact