Skip to content

Supabase Storage S3 Configuration

  • S3 Endpoint: https://syxlwkmnfuwgdvgnpcar.storage.supabase.co/storage/v1/s3
  • Region: us-west-2
  • You may need to create an access key in the Supabase dashboard for programmatic S3 access.
  • For client-side uploads via the Supabase JS SDK, access keys are not required if your bucket policies allow public or authenticated writes.
  • If you use the S3 protocol directly (e.g., with AWS SDK or CLI), you must generate an access key and secret in the Supabase dashboard and use them as your S3 credentials.
  • The bucket name for uploads is: medias
  • Subfolders (e.g., avatars/) do not need to be created manually; they are created automatically on upload.
  • If you encounter 400/401 errors, check your bucket's RLS (Row Level Security) and public/private settings.

Example .env.local additions

SUPABASE_STORAGE_S3_ENDPOINT=https://syxlwkmnfuwgdvgnpcar.storage.supabase.co/storage/v1/s3 SUPABASE_STORAGE_S3_REGION=us-west-2 SUPABASE_STORAGE_BUCKET=medias

SUPABASE_STORAGE_S3_KEY=your-access-key (if using S3 protocol directly)

SUPABASE_STORAGE_S3_SECRET=your-secret-key (if using S3 protocol directly)