From a87074e888e247a0cb5dd1dcca75ff0d01bdc5e6 Mon Sep 17 00:00:00 2001 From: LocalStack Bot Date: Tue, 18 Aug 2026 21:07:38 +0000 Subject: [PATCH] DOC-406: automated docs update --- .../docs/aws/developer-tools/snapshots/cloud-pods.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/content/docs/aws/developer-tools/snapshots/cloud-pods.mdx b/src/content/docs/aws/developer-tools/snapshots/cloud-pods.mdx index 14b43118e..db2ea2da5 100644 --- a/src/content/docs/aws/developer-tools/snapshots/cloud-pods.mdx +++ b/src/content/docs/aws/developer-tools/snapshots/cloud-pods.mdx @@ -414,6 +414,14 @@ export AWS_SECRET_ACCESS_KEY=... A possible option is to obtain credentials via [AWS SSO CLI](https://github.com/synfinatic/aws-sso-cli). +:::note +**LocalStack v2026.08 or later:** Cloud Pods can be saved to and loaded from real AWS S3 buckets while [Transparent Endpoint Injection](/aws/customization/networking/transparent-endpoint-injection/) is enabled (the default configuration). + +**LocalStack versions before v2026.08:** If you encounter TLS certificate validation errors when saving Cloud Pods to a real S3 bucket, disable the DNS server by setting `DNS_ADDRESS=0` and restart LocalStack. +This workaround disables transparent endpoint injection application-wide. +For more details, see [DNS Server configuration](/aws/customization/networking/dns-server/#dns-server-bind-address). +::: + Next, we establish a new remote specifically designed for an S3 bucket. By running the following command, we create a remote named `s3-storage-aws` responsible for storing Cloud Pod artifacts in an S3 bucket called `ls-pods-bucket-test`.