docs: community image & license updates#502
Open
quetzalliwrites wants to merge 4 commits intomainfrom
Open
Conversation
quetzalliwrites
requested review from
HarshCasper,
anisaoshafi,
bentsku,
cloutierMat,
dfangl,
dominikschubert,
giograno,
hovaesco,
joe4dev,
k-a-il,
macnev2013,
pinzon,
remotesynth,
silv-io,
simonrw,
thrau and
viren-nadkarni
as code owners
Deploying localstack-docs with
|
| Latest commit: |
6d3799d
|
| Status: | 🚫 Build failed. |
silv-io
reviewed
Mar 17, 2026
silv-io
reviewed
Mar 17, 2026
src/content/docs/aws/capabilities/config/initialization-hooks.mdx
Outdated
Show resolved
Hide resolved
remotesynth
requested changes
Mar 17, 2026
Collaborator
remotesynth
left a comment
remotesynth
left a comment
There was a problem hiding this comment.
Mostly minor tweaks and corrections
| | `LAMBDA_DOCKER_FLAGS` | `-e KEY=VALUE`, `-v host:container`, `-p host:container`, `--add-host domain:ip` | Additional flags passed to Docker `run`\|`create` commands. Supports environment variables (also with `--env-file`, but the file has to be mounted into the LocalStack container), ports, volume mounts, extra hosts, networks, DNS servers, labels, ulimits, user, platform, and privileged mode. The `--env-file` argument for Docker `run` and Docker Compose have different feature sets. To provide both, we support the `--env-file` for environment files with the docker run syntax, while `--compose-env-file` supports the full docker compose features, like placeholders with `${}`, replacing quotes, etc. | | ||
| | `LAMBDA_DOCKER_NETWORK` | `bridge` (Docker default) | [Docker network driver](https://docs.docker.com/network/) for the Lambda and ECS containers. Needs to be set to the network the LocalStack container is connected to. Limitation: `host` mode currently not supported. | | ||
| | `LAMBDA_DOWNLOAD_AWS_LAYERS` | `1` (default, pro) | Whether to download public Lambda layers from AWS through a LocalStack proxy when creating or updating functions. | | ||
| | `LAMBDA_DOWNLOAD_AWS_LAYERS` | `1` (default, pro) | Whether to download public Lambda layers from AWS through a LocalStack for AWSxy when creating or updating functions. | |
Collaborator
There was a problem hiding this comment.
Suggested change
| | `LAMBDA_DOWNLOAD_AWS_LAYERS` | `1` (default, pro) | Whether to download public Lambda layers from AWS through a LocalStack for AWSxy when creating or updating functions. | | |
| | `LAMBDA_DOWNLOAD_AWS_LAYERS` | `1` (default, pro) | Whether to download public Lambda layers from AWS through a LocalStack for AWS when creating or updating functions. | |
| You can use the Community image to start your LocalStack container using various [installation methods](/aws/getting-started/installation/). | ||
| While configuring to run LocalStack with Docker or Docker Compose, run the `localstack/localstack` image with the appropriate tag you have pulled (if not `latest`). | ||
|
|
||
| ## LocalStack Pro image |
Collaborator
There was a problem hiding this comment.
Since LocalStack Pro isn't the name of a product, let's maybe make it clearer this is an image name
Suggested change
| ## LocalStack Pro image | |
| ## `localStack-pro` image |
|
|
||
| ## LocalStack Pro image | ||
|
|
||
| LocalStack Pro contains various advanced extensions to the LocalStack base platform. |
Collaborator
There was a problem hiding this comment.
This isn't really accurate anymore. Trying to reword it but maybe this sentence isn't even needed anymore.
Suggested change
| LocalStack Pro contains various advanced extensions to the LocalStack base platform. | |
| The `localStack-pro` Docket image is the primary image for the LocalStack platform. |
| We occasionally create patch releases for minor bug fixes and enhancements, to ensure that we can deliver changes quickly while not breaking your existing workflows (in case you prefer not to use `latest`). | ||
|
|
||
| To check out the various tags available for LocalStack, you can visit the [LocalStack Community](https://hub.docker.com/r/localstack/localstack/tags?page=1&ordering=last_updated) & [LocalStack Pro](https://hub.docker.com/r/localstack/localstack-pro/tags?page=1&ordering=last_updated) Docker Hub pages. | ||
| Visit the [LocalStack Pro tag](https://hub.docker.com/r/localstack/localstack-pro/tags?page=1&ordering=last_updated) in Docker Hub pages. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Visit the [LocalStack Pro tag](https://hub.docker.com/r/localstack/localstack-pro/tags?page=1&ordering=last_updated) in Docker Hub pages. | |
| Visit the [`localStack-pro` tag](https://hub.docker.com/r/localstack/localstack-pro/tags?page=1&ordering=last_updated) in Docker Hub pages. |
| localstack: | ||
| container_name: "localstack-main" | ||
| image: localstack/localstack-pro # required for Pro | ||
| image: localstack/localstack # required for Pro |
Collaborator
There was a problem hiding this comment.
We're still suggesting people use the pro image. It's all very confusing since localstack/localstack will technically be the same as localstack/localstack-pro.
Suggested change
| image: localstack/localstack # required for Pro | |
| image: localstack/localstack-pro |
| With LocalStack, you can easily mount code from your host filesystem into the ECS container, allowing for a quicker debugging loop that doesn't require rebuilding and redeploying the task's Docker image for each change. | ||
|
|
||
| To try out this tutorial for yourself, you can find the code in our LocalStack Pro samples on [LocalStack Pro samples](https://github.com/localstack/localstack-pro-samples/tree/master/ecs-ecr-container-app) over GitHub, including a `Makefile` to execute each step of the process. | ||
| To try out this tutorial for yourself, you can find the code in our LocalStack for AWS samples on [LocalStack for AWS samples](https://github.com/localstack/localstack-pro-samples/tree/master/ecs-ecr-container-app) over GitHub, including a `Makefile` to execute each step of the process. |
Collaborator
There was a problem hiding this comment.
This sounds redundant.
Suggested change
| To try out this tutorial for yourself, you can find the code in our LocalStack for AWS samples on [LocalStack for AWS samples](https://github.com/localstack/localstack-pro-samples/tree/master/ecs-ecr-container-app) over GitHub, including a `Makefile` to execute each step of the process. | |
| To try out this tutorial for yourself, you can find the code in our [`localstack-pro-samples` repository](https://github.com/localstack/localstack-pro-samples/tree/master/ecs-ecr-container-app) over GitHub, including a `Makefile` to execute each step of the process. |
| We have also explored creating, configuring, and deploying a Serverless project with LocalStack, enabling developers to develop and test Cloud and Serverless applications locally without AWS costs—accelerating iteration for cloud-native workloads. | ||
|
|
||
| LocalStack offers integrations with various popular tools such as Terraform, Pulumi, Serverless Application Model (SAM), and more. For more information about LocalStack integrations, you can refer to our [Integration documentation](https://docs.localstack.cloud/aws/integrations). To further explore and experiment with the concepts covered in this tutorial, you can access the code and resources on our [LocalStack Pro samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/elb-load-balancing) along with a Makefile for step-by-step execution. | ||
| LocalStack offers integrations with various popular tools such as Terraform, Pulumi, Serverless Application Model (SAM), and more. For more information about LocalStack integrations, you can refer to our [Integration documentation](https://docs.localstack.cloud/aws/integrations). To further explore and experiment with the concepts covered in this tutorial, you can access the code and resources on our [LocalStack for AWS samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/elb-load-balancing) along with a Makefile for step-by-step execution. |
Collaborator
There was a problem hiding this comment.
Suggested change
| LocalStack offers integrations with various popular tools such as Terraform, Pulumi, Serverless Application Model (SAM), and more. For more information about LocalStack integrations, you can refer to our [Integration documentation](https://docs.localstack.cloud/aws/integrations). To further explore and experiment with the concepts covered in this tutorial, you can access the code and resources on our [LocalStack for AWS samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/elb-load-balancing) along with a Makefile for step-by-step execution. | |
| LocalStack for AWS offers integrations with various popular tools such as Terraform, Pulumi, Serverless Application Model (SAM), and more. For more information about integrations, you can refer to our [Integrations documentation](https://docs.localstack.cloud/aws/integrations). To further explore and experiment with the concepts covered in this tutorial, you can access the code and resources on our [`localstack-pro-samples` repository on GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/elb-load-balancing) along with a Makefile for step-by-step execution. |
| For more advanced usage patterns, you can explore features like [Lambda Hot Reloading](/aws/tooling/lambda-tools/hot-reloading) and [Lambda Debugging](/aws/tooling/lambda-tools/remote-debugging). | ||
|
|
||
| To further explore and experiment with the concepts covered in this tutorial, you can access the code and accompanying `Makefile` on our [LocalStack Pro samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/lambda-container-image). | ||
| To further explore and experiment with the concepts covered in this tutorial, you can access the code and accompanying `Makefile` on our [LocalStack for AWS samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/lambda-container-image). |
Collaborator
There was a problem hiding this comment.
Suggested change
| To further explore and experiment with the concepts covered in this tutorial, you can access the code and accompanying `Makefile` on our [LocalStack for AWS samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/lambda-container-image). | |
| To further explore and experiment with the concepts covered in this tutorial, you can access the code and accompanying `Makefile` on our [`localstack-pro-samples` repository on GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/lambda-container-image). |
|
|
||
| For more information about LocalStack Cloud Pods, refer to the documentation provided. | ||
| The code for this tutorial, including a Makefile to execute it step-by-step, is available in the [LocalStack Pro samples repository](https://github.com/localstack/localstack-pro-samples/tree/master/reproducible-ml) on GitHub. | ||
| The code for this tutorial, including a Makefile to execute it step-by-step, is available in the [LocalStack for AWS samples repository](https://github.com/localstack/localstack-pro-samples/tree/master/reproducible-ml) on GitHub. |
Collaborator
There was a problem hiding this comment.
Suggested change
| The code for this tutorial, including a Makefile to execute it step-by-step, is available in the [LocalStack for AWS samples repository](https://github.com/localstack/localstack-pro-samples/tree/master/reproducible-ml) on GitHub. | |
| The code for this tutorial, including a Makefile to execute it step-by-step, is available in the [`localstack-pro-samples` repository on GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/reproducible-ml) on GitHub. |
| [AWS Glue Schema Registry](/aws/services/glue) is supported by LocalStack for AWS as well, ultimately allowing you to test the evolution of your data streaming application completely on your local machine. | ||
| It allows you develop and test your application's data schema evolution locally. | ||
| The code for this tutorial (including a script to execute it step-by-step) can be found in our [LocalStack Pro samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/glue-msk-schema-registry). | ||
| The code for this tutorial (including a script to execute it step-by-step) can be found in our [LocalStack for AWS samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/glue-msk-schema-registry). |
Collaborator
There was a problem hiding this comment.
Suggested change
| The code for this tutorial (including a script to execute it step-by-step) can be found in our [LocalStack for AWS samples over GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/glue-msk-schema-registry). | |
| The code for this tutorial (including a script to execute it step-by-step) can be found in our [`localstack-pro-samples` repository on GitHub](https://github.com/localstack/localstack-pro-samples/tree/master/glue-msk-schema-registry). |
HarshCasper
requested changes
Mar 18, 2026
Comment on lines
-187
to
-195
| ## Credit Consumption | ||
|
|
||
| Ephemeral Instances consume credits based on the resources used and the duration of the instance. | ||
| You can view the credit consumption of the Ephemeral Instance in the **Ephemeral Instance** page. | ||
| Currently, for every 1 credit, you can run an Ephemeral Instance for 1 minute. | ||
| You can view the available minutes under the **Lifetime in minutes** slider when creating an Ephemeral Instance. | ||
| You can also see the credit consumption in the **Credit Consumption** section of the Ephemeral Instance page. | ||
|
|
||
|  No newline at end of file |
Member
There was a problem hiding this comment.
We shouldn't remove this, since Ephemeral Instances still require credits to be used. The only mention we should be removing is of CI credits.
Collaborator
Author
There was a problem hiding this comment.
TY for the catch! got it
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves: