💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
LocalStack release 0.14.0
ES_ENDPOINT_STRATEGY=port
(formerly off
) and ES_MULTI_CLUSTER=0
, a port from the external service port range is used (instead of PORT_ELASTICSEARCH
or 4571
by default).ES_ENDPOINT_STRATEGY
, ES_MULTI_CLUSTER
, and ES_CUSTOM_BACKEND
. Instead, the OPENSEARCH_*
variables should be used. The ES_ENDPOINT_STRATEGY=off
is being renamed to port
(i.e. please use OPENSEARCH_ENDPOINT_STRATEGY=port
from now on).LocalStack release 0.13.3
uname
command in system check for windows compatibilityLocalStack release 0.13.2
2.17.0
to fix the critical security vulnerabilities CVE-2021-44228, CVE-2021-45046
LocalStack release 0.13.1
LEGACY_PERSISTENCE
config, which determines whether the legacy persistence mechanism (based on API calls record&replay) should be used. Currently still defaults to LEGACY_PERSISTENCE=1
, but the logic will be disabled by default and may get removed entirely in a future release. (Please note: this is only affecting the legacy persistence in Community - if you're using the Pro version, you can ignore this message.)make init-testlibs
S3_SKIP_SIGNATURE_VALIDATION=True
LogStream.filter_log_events
to use get_pattern_matcher
EVENTS_TMP_DIR
LocalStack release 0.13.0
This release introduces three major changes
#4754 introduced a multi-platform docker build to support both amd64 and arm64. Alpine and musl made things unnecessarily difficult, so we switched to a Debian buster base image. Post-init (e.g., in /docker-entrypoint-initaws.d
) scripts that expect an Alpine environment (e.g., use apk
commands to install things into the LocalStack container) will stop working.
As part of an ongoing effort to improve startup performance, we have introduced a new code loading and service startup mechanism to allow lazy-loading of services. After LocalStack starts, services used to be in the state running
, indicating that they are loaded and ready to serve requests. To allow more fine-grained state handling for services with lazy loading, we have introduced a new type of state called available
.
When starting LocalStack, services are by default in the state available
, which means that clients can start making requests to the services, and at the first time the service is hit, all the necessary code is loaded and the backend service is started, at which point the service after which the service will be in the running
state. The environment variable EAGER_SERVICE_LOADING
controls this behavior.
Scripts that depend on the output of /health
being running
will require setting setting EAGER_SERVICE_LOADING=1
, which will start all services eagerly. This works together with the SERVICES
variable to create the behavior from localstack <= 0.13.0.
(An alternative solution is to update your startup logic to accept either running
or available
as the healthy service state - e.g., see details in this issue).
Change Log:
LocalStack release 0.12.20
1. New Features
OUTBOUND_HTTP_PROXY
option for proxies when downloading external resources2. Enhancements
3. Bug Fixes
RequestHandler
interfaceChange Log:
LocalStack release 0.12.19
1. New Features
EXTRA_CORS_ALLOWED_ORIGINS
configuration2. Enhancements
3. Bug Fixes
aws:sns
instead of localstack:sns
Change Log:
LocalStack release 0.12.18
1. New Features
2. Enhancements
<apiId>.execute-api.*
hostnames for API Gateway invocation URLsLAMBDA_CODE_EXTRACT_TIME
to configure max Lambda code extract wait timetestutil.py
to deploy large Lambda zip files via S3InvocationResult
with content instead of wrapping as Flask response for LAMBDA_FORWARD_URL--add-host
argument in LAMBDA_DOCKER_FLAGS
3. Bug Fixes
Change Log:
LocalStack release 0.12.17
1. New Features
2. Enhancements
config.CONFIG_ENV_VARS
to pass them to Docker instance3. Bug Fixes
Change Log:
LocalStack release 0.12.16
1. New Features
THUNDRA_APIKEY
TEST_TARGET=AWS_CLOUD
option to run tests against real AWS2. Enhancements
unparse
with custom XML serializer for AWS responses"${resource.attr.subattr}"
3. Bug Fixes