HumanSignal / HumanSignal/label-studio

Cloud Storage S3 ignores custom endpoint when using prefix

Open
#3,995 2 comments 1 reaction 2 assignees Claimed by @nikitabelonogov View on GitHub
import problem storages
Dominant language
TypeScript
Stars
28.3k
Forks
3.7k
Avg merge
14h
Merged PRs (30d)
15

Description

I have an object storage at scaleway and try to use it as source storage in LS. The custom endpoint for my bucket is something like `https://bucketname.s3.nl-ams.scw.cloud`. While probing for the correct credentials, I filled the `Bucket Prefix` field and suddently LS reports the error, that it could not connect to the endpoint `https://s3.nl-ams.amazonaws.com/bucketname?list-type=2&prefix=Test&max-keys=1&encoding-type=url`

Steps to reproduce the behavior:
1. Add Source Storage
2. Choose AWS S3
3. Fill in bucket name, Bucket Prefix and custom S3 Endpoint
4. See error

Regardless of whether my own S3 service supports the prefix, the custom endpoint should be taken into account.

- OS: Ubuntu
- Label Studio Version 1.7.2

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.