LocalStack Limitations

This page describes known limitations of LocalStack and its services, either due to missing implementations or due to third-party integrations.

Limitations that exist due to missing features in LocalStack.

At the moment only a locally launched LocalStack instance can properly run the DynamoDB service.

Integration Limitations

Limitations that may occur because of third party integrations behavior.

Stacks with validated certificates

By default, stacks with validated certificates may not be deployed using the lambda executor. This originates from the way how CDK ensures the certificate is ready - it creates a single-file lambda function with a single dependency on aws-sdk which is usually preinstalled and available globally in lambda runtime. When this lambda is executed locally from the folder, the package can not be discovered by Node due to the way how Node package resolution works.

For certain LocalStack features it is necessary that the DNS resolves to the local network. For example, LocalStack is using virtual-host based addressing for S3, ElasticSearch, and OpenSearch by default. S3 buckets can be reached via <bucket-name>.s3.<region>.localhost.localstack.cloud and OpenSearch clusters which are created by LocalStack can be reached via . This is handled correctly if you configured your system’s DNS for the transparent execution mode of LocalStack Pro.

You can check if your DNS setup works correctly by resolving a subdomain of localhost.localstack.cloud:

If the the DNS resolves the subdomain to your localhost (127.0.0.1), your setup is working. If not, please check the configuration of your router / DNS if the Rebind Protection is active or .