Skip to content

DOC-406: Document DNS workaround for Cloud Pods S3 remotes on older versions #874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
quetzalliwrites merged 1 commit into from
Aug 19, 2026
+8 −0
Merged

DOC-406: Document DNS workaround for Cloud Pods S3 remotes on older versions #874

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions src/content/docs/aws/developer-tools/snapshots/cloud-pods.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.

Expand Down