AWS Server Framework (ASF) and parity tooling
LocalStack completes the rollout of the AWS Server Framework, a server-side framework that works directly with the AWS API specifications.
- ASF generates providers from AWS API specs to reduce protocol-related issues, and enables features such as Extensions and parity reporting.
- New framework for testing, analyzing, and reporting parity with AWS, including integration tests that can use custom snapshots to cover more API surface.
- Now supports over 80 AWS services across the Community and Pro versions.
Unified filesystem hierarchy and persistence
A single LocalStack volume replaces the previous set of directory configurations.
- Mount any host directory into
/var/lib/localstack; the CLI defaults to <cache>/localstack/volume. All state, extensions, logs, and third-party packages live in the volume. TMPDIR, HOST_TMP_PATH, and DATA_DIR are no longer needed.- Rebuilt persistence (Pro) replaces the deprecated record-and-replay approach; enable it with
PERSISTENCE=1 instead of DATA_DIR.
Multi-account setups and Extensions
- Revamped multi-account system (experimental) runs multi-tenant setups on a single instance with resources namespaced by AWS account ID, enabled with
MULTI_ACCOUNTS=1, removing the need for one instance per account. - LocalStack Extensions (experimental) let you extend LocalStack with pluggable Python distributions that hook into lifecycle phases or add custom routes to the HTTP gateway.
IAM enforcement for all services
- IAM enforcement is now supported across all AWS services, activated with
ENFORCE_IAM=1. - Explainable IAM reports which declarations are missing from your policies.
Cloud Pods and stack analytics
- Reworked Cloud Pods add state file handling, integrated storage and versioning, and merging of pod state into a running instance.
- Stack Insights instruments LocalStack to report AWS API usage telemetry to your LocalStack Team account, showing which APIs and operations are used and which services produce the most errors. Event logging can be turned off with
DISABLE_EVENTS=1.
New logging output and error reporting
- AWS requests are logged at
INFO level in the form AWS <service>.<operation> => <http-status> (<error type>). LS_LOG=trace appends request and response objects plus HTTP headers to each log line.- With
DEBUG=1, full stack traces for internal errors are returned to the client.
