Skip to content
This repository was archived by the owner on Aug 7, 2025. It is now read-only.

Commit 51b2ed5

Browse files
committed
add troubleshooting section for s3 remote
1 parent 28d91fa commit 51b2ed5

File tree

2 files changed

+25
-1
lines changed
  • content/en
    • applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds
    • user-guide/state-management/cloud-pods

2 files changed

+25
-1
lines changed

content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Serverless RDS Proxy with API Gateway, Lambda, and Aurora RDS"
3-
description: "Serverless RDS Proxy demonstrates how Aurora cluster can be accessed with and without using a proxy."
3+
description: "Serverless RDS Proxy demonstrates how Aurora cluster can be accessed with and without using a proxy, deployed using Serverless Application Model on LocalStack"
44
hide_feedback: true
55
hide_readingtime: true
66
type: applications

content/en/user-guide/state-management/cloud-pods/index.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -437,6 +437,30 @@ Full S3 remotes support is available in the CLI from version 3.2.0.
437437
If you experience any difficulties, update your [LocalStack CLI]({{< ref "/getting-started/installation/#updating" >}}).
438438
{{< /callout >}}
439439

440+
#### Troubleshooting
441+
442+
You might encounter an error like the following:
443+
444+
{{< command >}}
445+
An error occurred (InvalidAccessKeyId) when calling the CreateBucket operation: The AWS Access Key Id you provided does not exist in our records.
446+
{{< / command >}}
447+
448+
This means that you are likely using temporary AWS credentials and the the S3 remote configuration is missing the `AWS_SESSION_TOKEN` environment variable.
449+
To fix the issue, first export `AWS_SESSION_TOKEN` into your environment.
450+
Then, be sure to add the `access_token` placeholder to the URL of the `pod remote add` command:
451+
452+
{{< command >}}
453+
$ localstack pod remote add s3-storage-aws 's3://ls-pods-bucket-test/?access_key_id={access_key_id}&secret_access_key={secret_access_key}&access_token={access_token}'
454+
{{< / command >}}
455+
456+
If you are experiencing issues connecting to the S3 bucket, you might need to add the S3 URL to the list of URLs that it resolved upstream, e.g.,:
457+
458+
```bash
459+
DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM=ls-pods-bucket-test.s3.amazonaws.com/
460+
```
461+
462+
For more info, browse the [Skip LocalStack DNS Resolution]({{< ref "/user-guide/tools/dns-server/#skip-localstack-dns-resolution" >}}) section of our docs.
463+
440464
### ORAS remote storage
441465

442466
The ORAS remote enables users to store Cloud Pods in OCI-compatible registries like Docker Hub, Nexus, or ECS registries.

0 commit comments

Comments
 (0)