rclone S3 Connection Fails with SignatureDoesNotMatch Error (Status 403)
Description:
When attempting to list the contents of an S3 bucket (configured as sdd:) using rclone in a RunPod container environment, I encounter the following error:
Expected Outcome:
To be able to access the S3 bucket normally using rclone.
9 Replies
Are you certain you're using the right credentials to access the s3 api? http://docs.runpod.io/serverless/storage/s3-api
Runpod Documentation
S3-compatible API - Runpod Documentation
Use Runpod's S3-compatible API to access and manage your network volumes.
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
I tried to use the red section as you mentioned. I created a s3-api and go to secrets tab to get the id. but it failed too D:
here is my config:
[runpod]
type = s3
provider = Other
access_key_id = user_2xxxxxxxxxxx
secret_access_key = rps_Cxsdsxxxxxxxxxxxxxxvvmt
region = EU-RO-1
endpoint = https://s3api-eu-ro-1.runpod.io

I've followed this document to create s3 api key but it showed error message like:
2025/06/13 16:56:19 ERROR : : error listing: operation error S3: ListBuckets, https response error StatusCode: 403, RequestID: , HostID: , api error SignatureDoesNotMatch: Unable to authenticate request: signature does not match any shared API key for specified user ID
2025/06/13 16:56:19 NOTICE: Failed to lsd with 2 errors: last error was: operation error S3: ListBuckets, https response error StatusCode: 403, RequestID: , HostID: , api error SignatureDoesNotMatch: Unable to authenticate request: signature does not match any shared API key for specified user ID
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
When I create a config through rclone config, there is no bucket id option.
How do you set the bucket id?
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
I'm also experiencing this issue.
rlone is not compatible for now use boto3