Local development and testing are significant for engineers who wish to ship confidently onto production environments. Test-driven development (TDD) has been adopted as an essential practice to enforce that and ensure that every code change is validated locally and on CI. This is where we arrive at the Testcontainers libraries that support your tests, providing lightweight, ephemeral instances of common databases, message brokers, web browsers, or anything else that can run in a Docker container. With Testcontainers, available in different popular languages: Java, Go, .NET, JavaScript/Typescript, and Python, you can replicate the production environment on your local machine and test everything (including AWS APIs powered by LocalStack)! Testcontainers ensure that the data access layer, user interface, and application are tested well at each step. In this session, we have looked at Testcontainers and how to adopt them to develop our applications locally and run our integration tests while using LocalStack to provision cloud resources inside a Docker container before pushing your application to production! In the end, we have also discussed how LocalStack and the Java version of Testcontainers play nicely with each other and wind up with updates about the all-new LocalStack release!

Tired of rebuilding your stack from scratch every time you run tests or restart your dev environment? In this episode, we dive into Cloud Pods, LocalStack’s powerful state management feature.You’ll learn how to:- Snapshot your entire LocalStack environment (services, resources, data)- Restore that exact state across machines, teams, or CI runs- Speed up test cycles and workflows- Use Cloud Pods to make testing in CI/CD faster and more reliableCloud Pods let you freeze your infrastructure in time. Perfect for repeatable tests, isolated dev environments, or onboarding new teammates.🔗 Read the companion blog post: https://blog.localstack.cloud/save-and-share-localstack-state-with-cloudpods/

dbt (Data Build Tool) helps data engineers manage data transformations using modular SQL and brings version control, testing, and documentation to their transformation logic. However, running dbt against production data warehouses like Snowflake can be slow, expensive, and risky.This session introduces a new way to develop and test dbt workflows locally using the Snowflake emulator in LocalStack. You'll learn how to: Set up a local dbt environment Configure dbt to connect to the Snowflake emulator Run and validate dbt models locally without using a real Snowflake account Iterate quickly on transformations before pushing them to productionThrough a hands-on factory app example, we’ll walk through how to use the Snowflake emulator to run dbt models on your laptop, helping you test logic, catch issues early, and reduce cloud costs.

In this video, you'll learn how you can run an Elastic Compute Cloud (EC2) instance locally using LocalStack's core cloud emulator. Elastic Compute Cloud (EC2) is a core service within Amazon Web Services (AWS) that provides scalable and flexible virtual computing resources. EC2 enables users to launch and manage virtual servers, commonly referred to as instances. LocalStack is a core cloud emulator that allows you run EC2 instances using a Docker backend. Under the hood, LocalStack spins another Docker container that mimics an EC2 instance functionality, including other add-on features such as EBS, IMDS, and Load Balancers.For more information, check out our docs:- Install LocalStack: https://docs.localstack.cloud/getting-started/installation/- Configure an Auth Token: https://docs.localstack.cloud/getting-started/auth-token/ - Supported EC2 operations: https://docs.localstack.cloud/user-guide/aws/ec2/#operations - Supported Instances & AMIs: https://docs.localstack.cloud/user-guide/aws/ec2/#instances-and-amis Corrections:- LocalStack will no longer provide the Ubuntu 20.04 Docker AMI (used in this video) by default in the next major release. It can still be manually added.- On nine minutes & nine seconds mark, we meant 'localhost' instead of 'localstack'. To access the web server, you can hit the localhost:8000 endpoint as shown in the video.