LocalStack provides a command line tool to manage the state of your instance via Cloud Pods.
3 minute read
The reference guide for LocalStack Cloud Pods CLI commands and how to get started on using them!
6 minute read
LocalStack provides a command line tool to manage the state of your instance via Cloud Pods.
3 minute read
Use Testcontainers with LocalStack
3 minute read
Use Spring Cloud Function framework with LocalStack
13 minute read
Hot code reloading continuously applies code changes to Lambda functions
10 minute read
The reference guide for LocalStack Cloud Pods CLI commands and how to get started on using them!
6 minute read
Tools to simplify application testing
2 minute read
Attach a debugger to your Lambda functions from within your IDE
8 minute read
Use LocalStack as DNS server to redirect AWS queries to LocalStack
8 minute read
Using patched SDKs in Lambdas to transparently redirect AWS API calls to LocalStack
2 minute read
Browser plugin to redirect AWS service calls to LocalStack
3 minute read
Cloud Pods provides a new way of collaborating in cloud application development workflows.
less than a minute
The LocalStack Cloud Pods Launchpad offers the easiest way of sharing and injecting cloud pods directly from your repositories or via a simple URL.
2 minute read
Using LocalStack Lambda with a self-managed Kafka cluster
2 minute read
Running LocalStack on Kubernetes
3 minute read
Get started with Amazon API Gateway on LocalStack
9 minute read
Get started with AWS Amplify on LocalStack
4 minute read
Get started with AWS Organizations on LocalStack
2 minute read
Get started with AWS DocumentDB on LocalStack
4 minute read
Get started with Amazon Elastic Compute Cloud (Amazon EC2) on LocalStack
10 minute read
Get started with Elastic Container Service (ECS) on LocalStack
2 minute read
Get started with Elastic MapReduce (EMR) on LocalStack
2 minute read
Get started with AWS ElastiCache on LocalStack
3 minute read
Get started with AWS IoT on LocalStack
4 minute read
Get started with AWS Lambdas on LocalStack
12 minute read
Get started with Quantum Ledger Database (QLDB) on LocalStack
less than a minute
Get started with Amazon Transfer on LocalStack
2 minute read
Use Testcontainers with LocalStack
3 minute read
Use Spring Cloud Function framework with LocalStack
13 minute read
Hot code reloading continuously applies code changes to Lambda functions
10 minute read
Tools to simplify application testing
2 minute read
Attach a debugger to your Lambda functions from within your IDE
8 minute read
Use LocalStack as DNS server to redirect AWS queries to LocalStack
8 minute read
Using patched SDKs in Lambdas to transparently redirect AWS API calls to LocalStack
2 minute read
Browser plugin to redirect AWS service calls to LocalStack
3 minute read
Using LocalStack Lambda with a self-managed Kafka cluster
2 minute read
Running LocalStack on Kubernetes
3 minute read
Get started with Amazon API Gateway on LocalStack
9 minute read
Get started with AWS Amplify on LocalStack
4 minute read
Get started with AWS Organizations on LocalStack
2 minute read
Get started with AWS DocumentDB on LocalStack
4 minute read
Get started with Amazon Elastic Compute Cloud (Amazon EC2) on LocalStack
10 minute read
Get started with Elastic Container Service (ECS) on LocalStack
2 minute read
Get started with Elastic MapReduce (EMR) on LocalStack
2 minute read
Get started with AWS ElastiCache on LocalStack
3 minute read
Get started with AWS IoT on LocalStack
4 minute read
Get started with AWS Lambdas on LocalStack
12 minute read
Get started with Quantum Ledger Database (QLDB) on LocalStack
less than a minute
Get started with Amazon Transfer on LocalStack
2 minute read
LocalStack provides a command line tool to manage the state of your instance via Cloud Pods.
3 minute read
The reference guide for LocalStack Cloud Pods CLI commands and how to get started on using them!
6 minute read
Cloud Pods provides a new way of collaborating in cloud application development workflows.
less than a minute
LocalStack provides a command line tool to manage the state of your instance via Cloud Pods.
3 minute read
The reference guide for LocalStack Cloud Pods CLI commands and how to get started on using them!
6 minute read
Use LocalStack as DNS server to redirect AWS queries to LocalStack
8 minute read
Using patched SDKs in Lambdas to transparently redirect AWS API calls to LocalStack
2 minute read
Cloud Pods provides a new way of collaborating in cloud application development workflows.
less than a minute
The LocalStack Cloud Pods Launchpad offers the easiest way of sharing and injecting cloud pods directly from your repositories or via a simple URL.
2 minute read
Use LocalStack as DNS server to redirect AWS queries to LocalStack
8 minute read
Using patched SDKs in Lambdas to transparently redirect AWS API calls to LocalStack
2 minute read
less than a minute
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 save command) and inject such snapshots into a running instance (with the load command) without requiring a restart.
In addition, we provide a remote storage backend that can be used to store the state of your running application and share it with your team members.
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 command-line interface (CLI).
LocalStack provides a command line tool to manage the state of your instance via Cloud Pods.
Get started with LocalStack Community Cloud Pods to to save and load your container state at will
The reference guide for LocalStack Cloud Pods remotes and how to get started on using them!
The reference guide for LocalStack Cloud Pods CLI commands and how to get started on using them!
The LocalStack Cloud Pods Launchpad offers the easiest way of sharing and injecting cloud pods directly from your repositories or via a simple URL.
less than a minute
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.
The Persistence feature ensures that the service state persists across container restarts. In contrast, Cloud Pods provide more detailed control over your state.
Rather than just restoring a state during LocalStack restarts, Cloud Pods enable you to capture snapshots of your local instance using the save command and inject these snapshots into a running instance using the load command, all without needing to perform a full restart.
In addition, LocalStack provides a remote storage backend that can be used to store the state of your running application and share it with your team members.
You can interact with Cloud Pods via the LocalStack Web Application. To save and load the persistent state of Cloud Pods, you can use the Cloud Pods command-line interface (CLI).
Get started with Cloud Pods to manage the state of your LocalStack instance state
Reference guide for LocalStack Cloud Pods CLI commands and how to get started on using them!
The reference guide for LocalStack Cloud Pods remotes and how to get started on using them!
Get started with Cloud Pods Launchpad to share and inject Cloud Pods into your LocalStack instance via a URL
Get started with LocalStack Community Cloud Pods to to save and load your container state at will
2 minute read
The LocalStack Cloud Pods Launchpad allows you to quickly share and inject cloud pods into a LocalStack instance.
Navigate to https://app.localstack.cloud/launchpad where you can create a sharable link for your pods.
Enter a public URl to your pod in the first input field, and click on ‘Generate Link’. -The resulting link can be copied and shared with others.
You can also copy the markdown snippet to quickly add a badge to your repository.
Please consider that the launchpad takes an arbitrary URL as input and passes it onto your LocalStack instance to inject the pod. -This may lead to unintended side effects, as the URL that is passed to the launchpad is not validated in any way.
We also display the URL on the UI, so please make sure that your trust the URL when using the launchpad.
If you want to add a badge to your README that links to the Cloud Pod Launchpad, you can use the following markdown snippet:
[](https://app.localstack.cloud/launchpad?url=url_of_your_pod)
-
Please note that you have to add the url_of_your_pod as the url query parameter to the URL.
-For example if you are hosting the pod in the same repository, just use the URL pointing to the raw pod file.
-Additionally, you can use the Link Generator to create the sharable link for your pod and copy the markdown for your repo.
Check out a proper example on this GitHub repository.
In this section we present an overview of common problems and how to solve them.
In case your LocalStack instance is not running, you will see the following error message:
Please start up your LocalStack instance and try again. -Find out more about how to start LocalStack in the Getting Started section.
In case the launchpad fails to load the metadata of your pod, you will see the following error message:
This can happen if the pod is not available anymore or if the URL is not valid. -Please check the URL and try again.
In case the launchpad fails to inject the pod into your LocalStack instance, you will see ‘Pod injection failed’ in the log message. -This may be due to a couple of reasons, like version mismatch. -Please check out your LocalStack logs for more information.
2 minute read
The LocalStack Cloud Pods Launchpad enables you to easily share and inject Cloud Pods into a LocalStack instance.
You can visit Cloud Pods launchpad to generate a shareable link for your pods.
Enter a public URL to your pod Cloud Pod the first input field, then click Generate Link. You can copy the resulting link and share it with others. Additionally, you have the option to copy a markdown snippet for quickly adding a badge to your repository.
The Launchpad accepts any URL as input and directly passes it to your LocalStack instance for Cloud Pod injection. As a result, this process may carry the risk of unintended side effects, as there is no validation applied to the URL provided to the launchpad.
Furthermore, it’s essential to exercise caution and only use URLs that you trust when utilizing the launchpad, as the URL is displayed in the user interface.
To add a badge to your README that links to the Cloud Pod Launchpad, you can include the following markdown snippet:
[](https://app.localstack.cloud/launchpad?url=url_of_your_pod)
+
You need to include the url_of_your_pod as the url query parameter in the URL. For instance, if your Cloud Pod is hosted within the same repository, simply use the URL that directs to the raw Cloud Pod file.
Additionally, you can utilize the Link Generator to generate a sharable link for your pod and copy the corresponding markdown snippet for your repository. Check out a proper example on th Cloud Pod badge GitHub repository.
In this section we present an overview of common problems and how to solve them.
If your LocalStack instance is not running, you will encounter the following error message:
Start your LocalStack instance and attempt the operation once more. For detailed instructions on starting LocalStack, refer to the Getting Started section.
If the launchpad encounters difficulties while loading the metadata of your pod, you will receive the following error message:
This can occur when the pod is no longer accessible or if the URL provided is invalid. Review the URL and attempt the operation once more.
If the launchpad is unable to successfully inject the pod into your LocalStack instance, you will encounter a Pod injection failed message in the log. This issue may arise from various factors, such as version disparities. For further insights and information, please review your LocalStack logs.