You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/aws/configuration/config/arm64-support.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Since LocalStack 2.0, Lambda functions execute in Docker containers with th
32
32
depending on the [instruction set architecture](https://docs.aws.amazon.com/lambda/latest/dg/foundation-arch.html) configured for the function (`x86_64` by default or `arm64`).
33
33
This behavior can lead to errors if the host system, the Docker image, or the code/layer of the function do not support the target architecture.
34
34
35
-
If you prefer to execute Lambda functions on your native platform architecture, you can set the [Lambda configuration](https://docs.localstack.cloud/aws/capabilities/config/configuration/#lambda) variable to `LAMBDA_IGNORE_ARCHITECTURE=1`.
35
+
If you prefer to execute Lambda functions on your native platform architecture, you can set the [Lambda configuration](https://docs.localstack.cloud/aws/configuration/config/configuration/#lambda) variable to `LAMBDA_IGNORE_ARCHITECTURE=1`.
36
36
Example scenario: I have an amd64 machine and want to run a an arm64 Lambda function. I know that the Lambda function runs on both architectures (i.e., no architecture specific code or dependencies).
37
37
38
38
Host systems with [multi-architecture support](https://docs.docker.com/build/building/multi-platform/) can run containers for different Linux architectures using emulation.
Copy file name to clipboardExpand all lines: src/content/docs/aws/configuration/config/configuration.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,24 +31,24 @@ Options that affect the core LocalStack system.
31
31
|`LOCALSTACK_HOST`|`localhost.localstack.cloud:4566` (default) | This is interpolated into URLs and addresses that are returned by LocalStack. It has the form `<hostname>:<port>`. |
32
32
|`GATEWAY_LISTEN`|`0.0.0.0:4566` (default in Docker mode), `127.0.0.1:4566` (default in host mode) | Configures the bind addresses of LocalStack. It has the form `<ip address>:<port>(,<ip address>:<port>)*`. LocalStack for AWS adds port `443`. |
33
33
|`USE_SSL`|`0` (default) | Whether to return URLs using HTTP (`0`) or HTTPS (`1`). Changed with 3.0.0. In earlier versions this was toggling SSL support on or off. |
34
-
|`PERSISTENCE`|`0` (default) | Enable persistence. See [Persistence Mechanism](/aws/developer-tools/snapshots/persistence) and [Filesystem Layout](/aws/capabilities/config/filesystem). |
34
+
|`PERSISTENCE`|`0` (default) | Enable persistence. See [Persistence Mechanism](/aws/developer-tools/snapshots/persistence) and [Filesystem Layout](/aws/configuration/config/filesystem). |
35
35
|`MAIN_CONTAINER_NAME`|`localstack-main` (default) | Specify the main docker container name |
36
36
|`LS_LOG`|`trace`, `trace-internal`, `debug`, `info`, `warn`, `error`, `warning`| Specify the log level. Currently overrides the `DEBUG` configuration. `trace` for detailed request/response, `trace-internal` for internal calls, too. |
37
-
|`EXTERNAL_SERVICE_PORTS_START`|`4510` (default) | Start of the [External Service Port Range](/aws/capabilities/networking/external-port-range) (inclusive). |
38
-
|`EXTERNAL_SERVICE_PORTS_END`|`4560` (default) | End of the [External Service Port Range](/aws/capabilities/networking/external-port-range) (exclusive). |
37
+
|`EXTERNAL_SERVICE_PORTS_START`|`4510` (default) | Start of the [External Service Port Range](/aws/configuration/networking/external-port-range) (inclusive). |
38
+
|`EXTERNAL_SERVICE_PORTS_END`|`4560` (default) | End of the [External Service Port Range](/aws/configuration/networking/external-port-range) (exclusive). |
39
39
|`EAGER_SERVICE_LOADING`|`0` (default) \|`1`| Boolean that toggles lazy loading of services. If eager loading is enabled, services are started at LocalStack startup rather than their first use. Be aware that eager loading increases the LocalStack startup time. |
40
-
|`SERVICES`|`s3,sqs`| A comma-delimited string of services. Check the [internal health endpoint](/aws/capabilities/networking/internal-endpoints#localstack-endpoints)`/_localstack/health` for valid service names. If `SERVICES` is set LocalStack will only load the listed services. All other services will be disabled and cannot be used. |
40
+
|`SERVICES`|`s3,sqs`| A comma-delimited string of services. Check the [internal health endpoint](/aws/configuration/networking/internal-endpoints#localstack-endpoints)`/_localstack/health` for valid service names. If `SERVICES` is set LocalStack will only load the listed services. All other services will be disabled and cannot be used. |
41
41
|`ALLOW_NONSTANDARD_REGIONS`|`0` (default) | Allows the use of non-standard AWS regions. By default, LocalStack only accepts [standard AWS regions](https://docs.aws.amazon.com/general/latest/gr/rande.html). |
42
42
|`PARITY_AWS_ACCESS_KEY_ID`|`0` (default) | Enables the use production-like access key IDs. By default, LocalStack issues keys with `LSIA...` and `LKIA...` prefix, and will reject keys that start with `ASIA...` or `AKIA...`. |
43
-
|`LOCALSTACK_RESPONSE_HEADER_ENABLED`|`1` (default) \|`0`| Whether LocalStack adds the [`x-localstack` response header](/aws/capabilities/networking/internal-endpoints#x-localstack-response-header) to every AWS API response. The header value is the LocalStack version and lets client tools detect LocalStack and its version. |
43
+
|`LOCALSTACK_RESPONSE_HEADER_ENABLED`|`1` (default) \|`0`| Whether LocalStack adds the [`x-localstack` response header](/aws/configuration/networking/internal-endpoints#x-localstack-response-header) to every AWS API response. The header value is the LocalStack version and lets client tools detect LocalStack and its version. |
44
44
45
45
## CLI
46
46
47
47
These options are applicable when using the CLI to start LocalStack.
48
48
49
49
| Variable | Example Values | Description |
50
50
| - | - | - |
51
-
|`LOCALSTACK_VOLUME_DIR`|`~/.cache/localstack/volume` (on Linux) | The location on the host of the LocalStack volume directory mount. See [Filesystem Layout](/aws/capabilities/config/filesystem#using-the-cli)|
51
+
|`LOCALSTACK_VOLUME_DIR`|`~/.cache/localstack/volume` (on Linux) | The location on the host of the LocalStack volume directory mount. See [Filesystem Layout](/aws/configuration/config/filesystem#using-the-cli)|
52
52
|`CONFIG_PROFILE`|| The configuration profile to load. See [Profiles](#profiles)|
53
53
|`CONFIG_DIR`|`~/.localstack`| The path where LocalStack can find configuration profiles and other CLI-specific configuration |
54
54
@@ -262,8 +262,8 @@ Please consult the [migration guide](/aws/services/lambda#migrating-to-lambda-v2
262
262
|`BUCKET_MARKER_LOCAL`|`hot-reload` (default) | Magic S3 bucket name for [Hot Reloading](/aws/developer-tools/lambda-tools/hot-reloading). The S3Key points to the source code on the local file system. |
263
263
|`HOSTNAME_FROM_LAMBDA`|`localstack`| Endpoint host under which APIs are accessible from Lambda containers (optional). This can be useful in docker-compose stacks to use the local container hostname if neither IP address nor container name of the main container are available (e.g., in CI). Often used in combination with `LAMBDA_DOCKER_NETWORK`.|
264
264
|`LAMBDA_DISABLE_AWS_ENDPOINT_URL`|`0` (default) \|`1`| Whether to disable injecting the environment variable `AWS_ENDPOINT_URL`, which automatically configures [supported AWS SDKs](https://docs.aws.amazon.com/sdkref/latest/guide/feature-ss-endpoints.html). |
265
-
|`LAMBDA_DISABLE_JAVA_SDK_V2_CERTIFICATE_VALIDATION`|`1` (default) | Whether to disable the certificate name validation for [AWS Java SDK v2](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/home.html) calls when using [transparent endpoint injection](/aws/capabilities/networking/transparent-endpoint-injection).|
266
-
|`LAMBDA_DOCKER_DNS`|`""` (default) | Optional custom DNS server for the container running your Lambda function. Overwrites the default LocalStack [DNS Server](/aws/capabilities/dns-server). Hence, resolving `localhost.localstack.cloud` requires additional configuration. |
265
+
|`LAMBDA_DISABLE_JAVA_SDK_V2_CERTIFICATE_VALIDATION`|`1` (default) | Whether to disable the certificate name validation for [AWS Java SDK v2](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/home.html) calls when using [transparent endpoint injection](/aws/configuration/networking/transparent-endpoint-injection).|
266
+
|`LAMBDA_DOCKER_DNS`|`""` (default) | Optional custom DNS server for the container running your Lambda function. Overwrites the default LocalStack [DNS Server](/aws/configuration/dns-server). Hence, resolving `localhost.localstack.cloud` requires additional configuration. |
267
267
|`LAMBDA_DOCKER_FLAGS`|`-e KEY=VALUE`, `-v host:container`, `-p host:container`, `--add-host domain:ip`| Additional flags passed to Docker `run`\|`create` commands. Supports environment variables (also with `--env-file`, but the file has to be mounted into the LocalStack container), ports, volume mounts, extra hosts, networks, DNS servers, labels, ulimits, user, platform, and privileged mode. The `--env-file` argument for Docker `run` and Docker Compose have different feature sets. To provide both, we support the `--env-file` for environment files with the docker run syntax, while `--compose-env-file` supports the full docker compose features, like placeholders with `${}`, replacing quotes, etc. |
268
268
|`LAMBDA_DOCKER_NETWORK`|`bridge` (Docker default) |[Docker network driver](https://docs.docker.com/network/) for the Lambda and ECS containers. Needs to be set to the network the LocalStack container is connected to. Limitation: `host` mode currently not supported. |
269
269
|`LAMBDA_DOWNLOAD_AWS_LAYERS`|`1` (default, pro) | Whether to download public Lambda layers from AWS through a LocalStack proxy when creating or updating functions. |
@@ -415,8 +415,8 @@ To learn more about these configuration options, see [Cloud Pods](/aws/developer
415
415
416
416
| Variable | Example Values | Description |
417
417
| - | - | - |
418
-
|`EXTENSION_AUTO_INSTALL`|| Install a list of extensions automatically at startup. Comma-separated list of extensions directives which will be installed automatically at startup (see [managing extensions](/aws/capabilities/extensions/managing-extensions#automating-extensions-installation))|
419
-
|`EXTENSION_DEV_MODE`|`0` (default) \|`1`| Enables development mode for extensions. Refer to the [Extensions Development Guide](/aws/capabilities/extensions/developing-extensions) for more information. |
418
+
|`EXTENSION_AUTO_INSTALL`|| Install a list of extensions automatically at startup. Comma-separated list of extensions directives which will be installed automatically at startup (see [managing extensions](/aws/configuration/extensions/managing-extensions#automating-extensions-installation))|
419
+
|`EXTENSION_DEV_MODE`|`0` (default) \|`1`| Enables development mode for extensions. Refer to the [Extensions Development Guide](/aws/configuration/extensions/developing-extensions) for more information. |
420
420
421
421
## Miscellaneous
422
422
@@ -442,21 +442,21 @@ To learn more about these configuration options, see [Cloud Pods](/aws/developer
442
442
443
443
## DNS
444
444
445
-
To learn more about these configuration options, see [DNS Server](/aws/capabilities/dns-server).
445
+
To learn more about these configuration options, see [DNS Server](/aws/configuration/dns-server).
446
446
447
447
| Variable | Example Values | Description |
448
448
| - | - | - |
449
449
| `DNS_ADDRESS` | `0.0.0.0` (default) | Address the LocalStack should bind the DNS server on (port 53 tcp/udp). Value `0` to disable.
450
450
| `DNS_SERVER` | Default upstream DNS or `8.8.8.8` (default) | Fallback DNS server for queries not handled by LocalStack.
451
451
| `DNS_RESOLVE_IP` | `127.0.0.1` (default) | IP address the DNS server should return as A record for queries handled by LocalStack. If customized, this value will be returned in preference to the DNS server response.
452
-
| `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM` | `([^.]+\.)*(ecr\|lambda)\.[^.]+\.amazonaws\.com` (example) | List of domain names that should *NOT* be redirected by the LocalStack DNS to the LocalStack container, but instead always forwarded to the upstream resolver. This will *NOT* redirect requests made to LocalStack due to manual endpoint configuration. Comma-separated list of Python-flavored regex patterns. See [the DNS server documentation](/aws/capabilities/dns-server#skip-localstack-dns-resolution) for more details.
452
+
| `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM` | `([^.]+\.)*(ecr\|lambda)\.[^.]+\.amazonaws\.com` (example) | List of domain names that should *NOT* be redirected by the LocalStack DNS to the LocalStack container, but instead always forwarded to the upstream resolver. This will *NOT* redirect requests made to LocalStack due to manual endpoint configuration. Comma-separated list of Python-flavored regex patterns. See [the DNS server documentation](/aws/configuration/dns-server#skip-localstack-dns-resolution) for more details.
453
453
| `DNS_LOCAL_NAME_PATTERNS` | `([^.]+\.)*(ecr\|lambda)\.[^.]+\.amazonaws\.com` (example) | **Deprecated since 3.0.2** List of domain names that should *NOT* be redirected by the LocalStack DNS to the LocalStack container, but instead always forwarded to the upstream resolver. This will *NOT* redirect requests made to LocalStack due to manual endpoint configuration. Comma-separated list of Python-flavored regex patterns. **Renamed to `DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM`**
454
454
455
455
## Transparent Endpoint Injection
456
456
457
457
| Variable | Example Values | Description |
458
458
| - | - | - |
459
-
| `DISABLE_TRANSPARENT_ENDPOINT_INJECTION` | `0` (default in Pro) \|`1` | Whether to disable DNS resolution of AWS hostnames to the LocalStack container. Pro feature. (see [Transparent Endpoint Injection](/aws/capabilities/networking/transparent-endpoint-injection))
459
+
| `DISABLE_TRANSPARENT_ENDPOINT_INJECTION` | `0` (default in Pro) \|`1` | Whether to disable DNS resolution of AWS hostnames to the LocalStack container. Pro feature. (see [Transparent Endpoint Injection](/aws/configuration/networking/transparent-endpoint-injection))
460
460
461
461
## LocalStack for AWS
462
462
@@ -522,9 +522,9 @@ These configurations have already been removed and **won't have any effect** on
522
522
|`DATA_DIR`| 2.0.0 | blank (disabled/default), `/tmp/localstack/data`| Local directory for saving persistent data. Use `PERSISTENCE` instead. |
523
523
| `DISABLE_TERM_HANDLER` | 2.0.0 | `""` (default) \|`1` | Whether to disable signal passing to LocalStack when running in docker. Enabling this will prevent an orderly shutdown when running inside LS in docker. Setting this to anything else than an empty string will disable it.
524
524
|`HOST_TMP_FOLDER`| 2.0.0 |`/some/path`| Temporary folder on the host that gets mounted as `$TMPDIR/localstack` into the LocalStack container. Required only for Lambda volume mounts when using `LAMBDA_REMOTE_DOCKER=false.`|
525
-
|`INIT_SCRIPTS_PATH`| 2.0.0 |`/some/path`| Before 1.0, this was used to configure the path to the initializing files with extensions `.sh` that were found in `/docker-entrypoint-initaws.d`. This has been replaced by the [init-hook system](/aws/capabilities/config/initialization-hooks/). |
526
-
|`LEGACY_DIRECTORIES`| 2.0.0 |`0` (default) | Use legacy method of managing internal filesystem layout. See [Filesystem Layout](/aws/capabilities/config/filesystem). |
527
-
|`LEGACY_INIT_DIR`| 2.0.0 |`1`\|`0`(default) | Used with `INIT_SCRIPTS_PATH`. This has been replaced by the [init-hook system](/aws/capabilities/config/initialization-hooks). |
525
+
|`INIT_SCRIPTS_PATH`| 2.0.0 |`/some/path`| Before 1.0, this was used to configure the path to the initializing files with extensions `.sh` that were found in `/docker-entrypoint-initaws.d`. This has been replaced by the [init-hook system](/aws/configuration/config/initialization-hooks/). |
526
+
|`LEGACY_DIRECTORIES`| 2.0.0 |`0` (default) | Use legacy method of managing internal filesystem layout. See [Filesystem Layout](/aws/configuration/config/filesystem). |
527
+
|`LEGACY_INIT_DIR`| 2.0.0 |`1`\|`0`(default) | Used with `INIT_SCRIPTS_PATH`. This has been replaced by the [init-hook system](/aws/configuration/config/initialization-hooks). |
0 commit comments