From 51b2ed5063eff344ff10c62e76e8d528463280ee Mon Sep 17 00:00:00 2001 From: Giovanni Grano Date: Thu, 12 Jun 2025 18:30:11 +0200 Subject: [PATCH 1/4] add troubleshooting section for s3 remote --- .../index.md | 2 +- .../state-management/cloud-pods/index.md | 24 +++++++++++++++++++ 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md b/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md index 7d8c90e381..79fb5b954b 100644 --- a/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md +++ b/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md @@ -1,6 +1,6 @@ --- title: "Serverless RDS Proxy with API Gateway, Lambda, and Aurora RDS" -description: "Serverless RDS Proxy demonstrates how Aurora cluster can be accessed with and without using a proxy." +description: "Serverless RDS Proxy demonstrates how Aurora cluster can be accessed with and without using a proxy, deployed using Serverless Application Model on LocalStack" hide_feedback: true hide_readingtime: true type: applications diff --git a/content/en/user-guide/state-management/cloud-pods/index.md b/content/en/user-guide/state-management/cloud-pods/index.md index 6a8248dd4e..47a9a9e2ae 100644 --- a/content/en/user-guide/state-management/cloud-pods/index.md +++ b/content/en/user-guide/state-management/cloud-pods/index.md @@ -437,6 +437,30 @@ Full S3 remotes support is available in the CLI from version 3.2.0. If you experience any difficulties, update your [LocalStack CLI]({{< ref "/getting-started/installation/#updating" >}}). {{< /callout >}} +#### Troubleshooting + +You might encounter an error like the following: + +{{< command >}} +An error occurred (InvalidAccessKeyId) when calling the CreateBucket operation: The AWS Access Key Id you provided does not exist in our records. +{{< / command >}} + +This means that you are likely using temporary AWS credentials and the the S3 remote configuration is missing the `AWS_SESSION_TOKEN` environment variable. +To fix the issue, first export `AWS_SESSION_TOKEN` into your environment. +Then, be sure to add the `access_token` placeholder to the URL of the `pod remote add` command: + +{{< command >}} +$ 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}' +{{< / command >}} + +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.,: + +```bash +DNS_NAME_PATTERNS_TO_RESOLVE_UPSTREAM=ls-pods-bucket-test.s3.amazonaws.com/ +``` + +For more info, browse the [Skip LocalStack DNS Resolution]({{< ref "/user-guide/tools/dns-server/#skip-localstack-dns-resolution" >}}) section of our docs. + ### ORAS remote storage The ORAS remote enables users to store Cloud Pods in OCI-compatible registries like Docker Hub, Nexus, or ECS registries. From 4e21f66ee8e78a7eb3e7cad869c2102dfbd49b57 Mon Sep 17 00:00:00 2001 From: Giovanni Grano Date: Thu, 12 Jun 2025 18:32:45 +0200 Subject: [PATCH 2/4] remove file --- .../index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md b/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md index 79fb5b954b..7d8c90e381 100644 --- a/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md +++ b/content/en/applications/serverless-rds-proxy-with-api-gateway-lambda-and-aurora-rds/index.md @@ -1,6 +1,6 @@ --- title: "Serverless RDS Proxy with API Gateway, Lambda, and Aurora RDS" -description: "Serverless RDS Proxy demonstrates how Aurora cluster can be accessed with and without using a proxy, deployed using Serverless Application Model on LocalStack" +description: "Serverless RDS Proxy demonstrates how Aurora cluster can be accessed with and without using a proxy." hide_feedback: true hide_readingtime: true type: applications From 9d7be45acf57409a5adb0b76cdc69430bdc9bc86 Mon Sep 17 00:00:00 2001 From: Giovanni Grano Date: Thu, 12 Jun 2025 18:55:09 +0200 Subject: [PATCH 3/4] fix typo --- content/en/user-guide/state-management/cloud-pods/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/user-guide/state-management/cloud-pods/index.md b/content/en/user-guide/state-management/cloud-pods/index.md index 47a9a9e2ae..67b32f0412 100644 --- a/content/en/user-guide/state-management/cloud-pods/index.md +++ b/content/en/user-guide/state-management/cloud-pods/index.md @@ -447,10 +447,10 @@ An error occurred (InvalidAccessKeyId) when calling the CreateBucket operation: This means that you are likely using temporary AWS credentials and the the S3 remote configuration is missing the `AWS_SESSION_TOKEN` environment variable. To fix the issue, first export `AWS_SESSION_TOKEN` into your environment. -Then, be sure to add the `access_token` placeholder to the URL of the `pod remote add` command: +Then, be sure to add the `session_token` placeholder to the URL of the `pod remote add` command: {{< command >}} -$ 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}' +$ localstack pod remote add s3-storage-aws 's3://ls-pods-bucket-test/?access_key_id={access_key_id}&secret_access_key={secret_access_key}&session_token={session_token}' {{< / command >}} 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.,: From ff8b5d25bebb024fdee5c403b685abc7a6d64da1 Mon Sep 17 00:00:00 2001 From: komarkovich Date: Fri, 13 Jun 2025 11:06:16 +0200 Subject: [PATCH 4/4] Update index.md removed duplicated "the" --- content/en/user-guide/state-management/cloud-pods/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/user-guide/state-management/cloud-pods/index.md b/content/en/user-guide/state-management/cloud-pods/index.md index 67b32f0412..2cd856dc04 100644 --- a/content/en/user-guide/state-management/cloud-pods/index.md +++ b/content/en/user-guide/state-management/cloud-pods/index.md @@ -445,7 +445,7 @@ You might encounter an error like the following: An error occurred (InvalidAccessKeyId) when calling the CreateBucket operation: The AWS Access Key Id you provided does not exist in our records. {{< / command >}} -This means that you are likely using temporary AWS credentials and the the S3 remote configuration is missing the `AWS_SESSION_TOKEN` environment variable. +This means that you are likely using temporary AWS credentials and the S3 remote configuration is missing the `AWS_SESSION_TOKEN` environment variable. To fix the issue, first export `AWS_SESSION_TOKEN` into your environment. Then, be sure to add the `session_token` placeholder to the URL of the `pod remote add` command: