LocalStack's core cloud emulator lets you emulate various cloud services on your own computer. This means you can develop and test your cloud-based solutions without connecting to a remote cloud.However, there are times when you need to seamlessly switch between your local setup and actual cloud resources, especially in hybrid situations. For instance, you might want to share a database with your local Lambda function or access S3 files stored remotely while running a Glue ETL job locally.With LocalStack's AWS Replicator extension, your local environment can replicate AWS cloud resources at the API level, allowing direct interaction with cloud services. The Replicator extension enables you to forward specific requests from LocalStack to AWS without complex proxy setups, and create test scenarios that involve a mix of local and cloud resources.Check out our tutorial — https://docs.localstack.cloud/tutorials/replicate-aws-resources-localstack-extension/

You've been there: Lambda triggers, SQS messages fly, Step Functions execute, and somewhere in the middle, something breaks. You have no idea what triggered what, what payload was passed, or where it all went wrong.
That's the black box problem of AWS development.
Once your architecture grows beyond a single service, visibility disappears fast. You're left stitching together scattered logs and redeploying just to see what's going on.
App Inspector is LocalStack's built-in observability layer that opens up that black box. It gives you a real-time, unified view of every service interaction happening inside your local cloud: what triggered what, with what payload, in what order.
In this talk, we'll walk through what App Inspector is, how it fits into your LocalStack workflow, and how to use it to catch bugs locally before they ever reach staging or production.

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.