@uppy/companion: Expose option to provide s3 provider options on runtime (key, secret, bucket, region) on runtime

Hello everyone, Currently, the companion app can connect to only a single S3 compatible endpoint which is initialized once per run. While this works for most scenarios, it doesn’t work in cases where the uploads can be routed to different buckets in S3 compatible storages with different access_key/access_secret(s).

This happens in cases where the upload [bucket/accessKey/accessSecret] is defined by information stored inside a DB. This can be implemented by exposing a function getProviderConfig similar to how getKey is exposed. This would internally construct a new S3 client object using the config returned by getProviderConfig func and use that to generate presigned URL instead of the default one.

[amitrajput1992]

Thanks for the update and effort. I ended up writing an uppy plugin that does this exact same thing. Keep up the good work!!

[goto-bus-stop]

@ifedapoolarewaju might be able to correct me when he’s back from vacation in a few days, but I think for remote providers it was going to be worked on next month (October) already. We had some Transloadit customers ask about it as well.

For regular S3 uploads with @uppy/aws-s3, I think a custom signing endpoint is actually the best approach. But for S3 Multipart uploads with @uppy/aws-s3-multipart, this feature would be required to support importing files from other providers.