Closed vinaypuppal closed 3 years ago
That's interesting, thanks! I think it may be possible to implement this manually today using the callbacks exposed by @uppy/aws-s3-multipart. Having builtin support would be nice too though.
A PR to use local signing when a credentials
option is given would be rad, if someone wants to do it :) I probably won't have time for a while.
We like this idea and are hoping the community can chime in on this one, so we've marked it as Help Wanted
as well as pinned it to the repo :crossed_fingers:!
Hey there. We need a feature like this for our application--so I am considering tinkering on this. I don't know the Uppy core very well though. Can anyone provide any directions in how this might be implemented?
We also needed to upload files to S3 from JS using credentials provided from server so we created a helper class to perform S3 API requetst on client side. Just instantiate this class with your credentials and set @uppy/aws-s3-multipart
callbacks to corresponding methods on this instance.
We use AWS STS federation token but I guess this should also work with AWS Cognito if it provides you with temporary credentials to access S3 API.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Any news on this feature?
AFAIK this feature is basically getTemporarySecurityCredentials
.
We use AWS Cognito for user authentication so these users get temporary AWS credentials to access AWS resources.
Can
@uppy/aws-s3-multipart
support this feature by providing an optioncredentials
and use it generating URL for uploads instead of proxying uploads to a remote server.Some uploaders which implemented this
It would be nice if uppy can also support these options similar to fineuploader:
And an event
credentialsExpired
so we supply new credentials if credentials get expired while performing uploads.