docs: Enhance Docs with S3 Examples of Generating Presigned URLs with Original File Names and Client Context Manager #4377
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 improves the documentation for generating presigned URLs with passing the original files' names and extensions. It may be very userful for a common solution is to store anonymized "raw" files like
file.bin
in S3, and the original file names and extensions in a relational database.Also added a small example of creating and using a wrapper via the context manager for an S3 client and managing the releasing of its resources.