← 返回首页
Overview | DocsSkip to content
Docs
Search
Select themeDarkLightAutoGet Started for Free
MenuAWSSnowflakeAzure
Select themeDarkLightAutoGet Started for Free
On this page

On this page

Overview

Copy page

If you’re having trouble connecting your application to LocalStack, you’re likely running into a networking mismatch. This section helps you identify the right troubleshooting path based on where your code is running.

Networking Troubleshooting

Section titled “Networking Troubleshooting”

Choose the scenario below that best describes your networking layout. Whether you’re running code on your host machine, in a container, or across multiple hosts, simply follow the corresponding guide to resolve common connection issues.

LocalStack only binds to IPv4 addresses (e.g. 127.0.0.1). Make sure you’re not trying to access LocalStack over IPv6.

Using the endpoint URL

Section titled “Using the endpoint URL”

For example, setting the endpoint_url parameter with an AWS SDK.

From the same computer
From a container LocalStack created
From your container
From a separate host

TLS certificates for localhost.localstack.cloud support only certain AWS regions. See TLS Certificate Coverage for details.

Using transparent endpoint injection

Section titled “Using transparent endpoint injection”

For example, you have a Lambda function that needs to access LocalStack resources.

From your host
From a lambda function

Accessing a resource created by LocalStack

Section titled “Accessing a resource created by LocalStack”

For example, you have created an OpenSearch cluster and are trying to access that resource by its URL.

From your host
From a container LocalStack created
From your container
From a separate host
Was this page helpful?
YesNo
Edit page