Cloud Pods

Cloud Pods are a mechanism that allows you to take a snapshot of the state in your current LocalStack instance, persist it to a storage backend, and easily share it with your team members.

While the Persistence feature ensures that the service state survives container restarts, Cloud Pods go beyond and allow more fine-grained control over your state. Instead of simply restoring a state when restarting LocalStack, Cloud Pods allow you to take snapshots of your local instance (with the command) and inject such snapshots into a running instance (with the inject command) without requiring a restart.

You can interact with Cloud Pods via the Web UI, and to load and store the persistent state of pods, you can use the localstack .

Below is a simple example of how you can and pull Cloud Pods to/from the remote platform using the localstack CLI:

Current Limitations

After pulling the pod, LocalStack will automatically inject its state into your instance at runtime, without requiring a restart. By default, the injecting state will replace the one in current the application state. The application and the injecting state can be merged with the flag.

Please be aware that the merge feature is still experimental and might lead sometimes to unwanted results. Please make sure to create a backup of any data before merging a cloud pod, if required.

Cloud Pods CLI

LocalStack provides a command line tool to manage the state of your instance via Cloud Pods.