Cloud Pods Browser
The Cloud Pods Browser lets you access and manage all your Cloud Pods. The Cloud Pods Browser is a feature of our LocalStack Web Application that is exclusive to LocalStack Team & Enterprise users.
With Cloud Pods, you can have individual or shared ownership of a snapshot of your LocalStack instance.
You can use Cloud Pods to manage your local AWS infrastructure and collaborate with others:
- Cloud Pods are accessible to all LocalStack Team users in your organization namespace. Public Cloud Pods are accessible to all LocalStack users.
- Cloud Pods version history is available, which allows you to view the version history of a Cloud Pod and access previous versions of specific Cloud Pods.
- Cloud Pods can be made public, injected into a running LocalStack container, or deleted - all from the LocalStack Web Application.
Access the version history
To view the version history of a Cloud Pod, click on the Cloud Pod’s name in the Cloud Pods Browser. You will be able to see a list of all versions, and view details of a specific version, in JSON format, by clicking on it.
To create a new version of a Cloud Pod, refer to the Cloud Pods CLI documentation.
Save a Cloud Pod
Users do not need to upload their Cloud Pod to the LocalStack Web Application since the Cloud Pods CLI automatically uploads pods via the
save operation. Similarly, the Cloud Pods CLI automatically injects the Cloud Pod into a running LocalStack container via the
load operation after specifying the Cloud Pod’s name. You can alternatively select a Cloud Pod on the Cloud Pods Browser and inject it into a running LocalStack container.
We use a secure storage mechanism to store Cloud Pods on the LocalStack Web Application. When you push a Cloud Pod, it is stored securely in our storage backend in AWS, with each user/organization receiving a dedicated, isolated S3 bucket. Pushing and pulling a Cloud Pod from our Web Application is facilitated by using secure S3 pre-signed URLs for the Cloud Pods CLI to interact directly with the S3 bucket, rather than piping the state files through our LocalStack Platform APIs.