You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new clowd storage feature is great but we have our Data on a private s3 compatible storage. There are multiple offerings for such storage on the market and it would be great if those would be usable as well.
Current Behaviour
Currently the AWS S3 cloud storage provider only supports AWS hosted S3 buckets.
Possible Solution
In essence we need a way to configure endpoint_url for the boto3 resource when adding a cloud storage.
The text was updated successfully, but these errors were encountered:
Can you please add parameter endpoint_urlhere (maybe set its default value to s3.amazonaws.com or so ) and 1 more field to the form ? That would enable using minio as an S3 compatible storage 🤗
@Marishka17 I am also looking for this feature, since I use MinIO for storage. @lozhn , Thanks for contributing on this. Is there any timeline on this when this will be implemented ?
My actions before raising this issue
Expected Behaviour
The new clowd storage feature is great but we have our Data on a private s3 compatible storage. There are multiple offerings for such storage on the market and it would be great if those would be usable as well.
Current Behaviour
Currently the AWS S3 cloud storage provider only supports AWS hosted S3 buckets.
Possible Solution
In essence we need a way to configure endpoint_url for the boto3 resource when adding a cloud storage.
The text was updated successfully, but these errors were encountered: