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/

Recreating the unique state of a cloud app environment is notoriously complex, making it difficult to diagnose bugs, collaborate with teammates, or even just pick up where you left off. Join us as we deep dive into LocalStack’s powerful state management and persistence features, exploring how to maintain, snapshot, and seamlessly share your local cloud environments using core features like persistence, Cloud Pods, and state files. Learn how to restore a previous state, share preconfigured environments with colleagues for collaboration or onboarding, or restore preset services and data for functional tests in CI. We'll also showcase LocalStack's new Model Context Protocol (MCP) integration, revealing how AI can manage, inspect, and automate your local cloud state.

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.

The rise of agentic AI in the software delivery lifecycle creates a dilemma with high-stakes implications.
As agents create new applications at an unprecedented rate, how do you integrate security without slowing down delivery?