feat: add support for S3 presigned URLs (GET and PUT) #15
+242
−12
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for generating S3 Presigned URLs using AWS Signature Version 4. This allows users to grant temporary access to private objects for both reading (GET) and writing (PUT).
Why this is needed
Currently, the bucket library requires the application to handle all object streaming via its own backend. In many web architectures—specifically when building APIs that serve files to client browsers—it is more efficient and secure to:
This feature was missing, so I implemented a builder pattern to make generating these URLs straightforward.
Changes