New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't proxy S3 links #14675
Comments
|
MedVideos is willing to make a generous donation in Bitcoin or Monero for volunteers to develop this feature. If developers are interested, just answer here in this issue. Thanks. |
|
Any news on this?? |
|
Well, no one has proposed an actual implementation approach yet to my knowledge. The closest (in word form - not code) was @julienfastre's proposal in duplicate issue #17793, but I'm not sure where that went. There will likely be a lot of side effects and gotchas that will have to be considered and covered, but even rough proof of concepts or experiment results would help things along. As this is a community project, all are encouraged to propose possible approaches, bring up concerns about specific use cases (e.g. see #17793 (comment)), or to do some experimentation (and report back!). Ideally that's what this thread becomes a collection of - if there is truly enough interest in this functionality. |
|
Breadcrumbs for the future: Some consideration was given to this in #9178 when the directdownload endpoint was created, in terms of thinking about how this might be offered by allowing the underlying Storage to bubble up a direct link that would then be offered up:
More work will be required. |
Is your feature request related to a problem? Please describe.
There is a use case for allowing files to be downloaded directly from S3 instead of being proxied by the instance that is running NextCloud. The first and biggest pro for this is cost reduction. The transfer from S3 to the internet is much much lower than from EC2 to the internet. The second pro is speed. S3 will serve the file as fast as possible, while your EC2 instance will server the file at a speed that could vary because of the CPU usage, network usage, instance type, etc...
Describe the solution you'd like
It should be possible to let users access S3 files directly, instead of making the NextCloud download them from S3 and then serve them to the user.
Also, for security reasons, links can be signed with a 1 minute expiration. This way files can be served only to logged in users.
Describe alternatives you've considered
N/A
Additional context
This feature requests is based on the premise that NextCloud is configured to use S3 and that the administrator has turned off end-to-end encryption.
The text was updated successfully, but these errors were encountered: