Share feedback, ideas and get community help

Updated 4 months ago

Supabase S3 - Error

At a glance

The community member is experiencing an error when using Supabase storage and has provided their configuration settings. The comments suggest that the S3_ENDPOINT value is not correct and should be vzgryrxsmjittvtrnkso.supabase.co instead. Additionally, the community member is receiving a "No API key found in request" error, indicating an authorization issue. The comments suggest that the community member needs to add an Authorization: Bearer header to the file sending request to resolve the authorization issue. Finally, a community member mentions that Typebot uses the Minio JS SDK for S3 operations and suggests that the community member needs to know how to properly initialize the client.

Useful resources
how can i resolve this error to use supabase storage:

I am using the following configuration in env

S3_ACCESS_KEY=

Key


S3_SECRET_KEY=

secretKey


S3_BUCKET=themis-bucket
S3_REGION=sa-east-1
S3_ENDPOINT=https://vzgryrxsmjittvtrnkso.supabase.co/storage/v1/s3
S3_SSL=true
Attachment
image.png
B
y
6 comments
S3_ENDPOINT does not look right
Try vzgryrxsmjittvtrnkso.supabase.co
Plain Text
{message: "No API key found in request", hint: "No `apikey` request header or url param was found."} 
Attachment
image.png
The request actually went through, but there was an authorization issue. How can I add a --header 'Authorization: Bearer to the file sending request?
Typebot uses minio JS SDK for all S3 operations

We need to know how the client should be initialized properly
Add a reply
Sign up and join the conversation on Discord