Install localstack with Homebrew, Nix, scoop

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• localstack

Project history

The LocalStack project presents itself as a cloud software development framework for developing and testing AWS applications locally. Its GitHub README describes the runtime as a cloud service emulator that runs in a single container on a laptop or in CI, with support for services such as Lambda, S3, DynamoDB, Kinesis, SQS, and SNS.

The package distributed by Homebrew installs the LocalStack CLI, which the official documentation describes as the tool for starting, managing, and configuring the LocalStack container. This made the project fit naturally into Python, Docker, and Homebrew-driven development setups.

Adoption history

LocalStack's adoption grew around the need to test cloud applications, infrastructure-as-code templates, and serverless workflows locally. Official documentation highlights use cases including CDK, Terraform, Lambda, and CI workflows, making it a common dependency in developer machines and continuous-integration jobs.

By 2026, LocalStack's release and packaging story had shifted toward the unified LocalStack for AWS image, auth tokens, and calendar versioning. The project's own 2026.03.0 release announcement documents the move from semantic versioning to monthly calendar versions.

How it is used

Typical package-manager usage is to install the CLI, ensure Docker is available, run `localstack start`, and point AWS tools or SDKs at the local endpoint. Configuration is primarily environment-variable driven, with the CLI also using `~/.localstack` as its configuration directory.

Modern LocalStack for AWS usage may require a `LOCALSTACK_AUTH_TOKEN` supplied through `localstack auth set-token`, the environment, Docker, Docker Compose, or CI secrets. The official auth-token documentation treats the token as confidential and does not document a portable credentials file path.

Why package nerds care

LocalStack is a notable package because it packages a broad cloud-service compatibility layer into a local CLI/container workflow. It sits at the intersection of Homebrew, PyPI, Docker images, AWS SDK testing, and infrastructure-as-code tooling.

For maintainers, LocalStack is interesting because small version and image-policy changes can affect many downstream test suites. Pinning, auth-token handling, Docker availability, and service coverage are all part of the package-management story.

Timeline

• 2016: LocalStack repository history begins with public source development on GitHub.
• 2020: LocalStack 1.0-era packaging and service coverage made it a common local AWS emulator in developer workflows.
• 2023: LocalStack v2/v3 release planning and cleanup moved the project through major-version transitions.
• 2026: LocalStack for AWS 2026.03.0 moved product releases to calendar versioning and documented the unified image/auth-token direction.

Related projects

• awslocal provides an AWS CLI wrapper for LocalStack endpoints.
• Testcontainers LocalStack modules use LocalStack images for integration tests.
• Moto, MinIO, and individual AWS service emulators overlap with narrower parts of LocalStack's local-cloud testing role.

Sources

• https://blog.localstack.cloud/localstack-for-aws-release-2026-03-0/
• https://docs.localstack.cloud/aws/configuration/config/configuration/
• https://docs.localstack.cloud/aws/developer-tools/running-localstack/localstack-cli/
• https://docs.localstack.cloud/aws/getting-started/auth-token/
• https://github.com/localstack/localstack