Replies: 2 comments 1 reply
|
If you can implement it and want to do so, feel free. I guess nobody has anything against this idea in principle, except maybe that it leaks metadata to Amazon… (and if this feature exists on Amazon S3 – a link to the docs from them instead of only the mermaid sequence diagram would be helpful. However, note that such storages like the S3 storage are purely community contributions and we cannot provide feature maintenance for them: Thus, I'd ping previous contributors to that S3 topic: @fenak (Felix J. Ogris as the original contributor seems to have deleted his GitHub account) Also BTW, to gather more interest discussions may not be thing. If you want, create an issue from it. At the right side on GitHub you should have a button to do that: Create issue from discussion |
|
Relevant links: |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I think it would be great if, instead of uploading encrypted data to privatebin which then uploads it again to S3, we could have privatebin use Pre-signed URL so that the client uploads directly to S3, e.g.:
sequenceDiagram WebUI->>+WebUI: User clicks on create button WebUI->>+PrivateBin: WebUI requests pre-signed URL PrivateBin->>+S3: Creates a pre-signed URL S3->>-PrivateBin: Returns a pre-signed URL PrivateBin->>-WebUI: Returns a S3 pre-signed URL WebUI->>S3: Uploads encrypted data to pre-signed URLThe point of this is to be able to upload large files which don't have to travel through PHP and the memory limits it may have.
Regards.
All reactions