rust-s3
rust-s3 copied to clipboard
Rust library for interfacing with S3 API compatible services
rust-s3 [docs]
Rust library for working with Amazon S3 or arbitrary S3 compatible APIs, fully compatible with async/await and futures ^0.3
. All async
features can be turned off and sync only implementations can be used.
Support further development
- BTC -
3NtVvyhMQepmcaVmCJURUB54wLBaZzfjci
- ETH -
0xfd2643D1A15787D41e61de2620D351Fd232936Af
Intro
Modest interface towards Amazon S3, as well as S3 compatible object storage APIs such as Backblaze B2, Wasabi, Yandex, Minio or Google Cloud Storage.
Supports: put
, get
, list
, delete
, operations on tags
and location
, well as head
.
Additionally a dedicated presign_get
Bucket
method is available. This means you can upload to S3, and give the link to select people without having to worry about publicly accessible files on S3. This also means that you can give people
a PUT
presigned URL, meaning they can upload to a specific key in S3 for the duration of the presigned URL.
AWS, Yandex and Custom (Minio) Example
Features
There are a lot of various features that enable a wide variety of use cases, refer to s3/Cargo.toml
for an exhaustive list. Below is a table of various useful features as well as a short description for each.
-
default
-tokio
runtime and anative-tls
implementation -
blocking
- generates*_blocking
variant of allBucket
methods, otherwise onlyasync
versions are available -
fail-on-err
-panic
on any error -
no-verify-ssl
- disable SSL verification for endpoints, useful for custom regions -
never-encode-slash
- never encode slashes in paths
With default-features = false
-
with-async-std
-async-std
runtime -
sync
- no async runtime,attohttpc
is used for HTTP requests -
tags
- required forBucket::get_object_tagging
All runtimes support either native-tls
or rustls-tls
, there are features for all combinations, refer to s3/Cargo.toml
for a complete list.
Path or subdomain style URLs and headers
Bucket
struct provides constructors for path-style
paths, subdomain
style is the default. Bucket
exposes methods for configuring and accessing path-style
configuration. blocking
feature will generate a *_blocking
variant of all of the methods listed below.
Buckets
create |
async |
delete |
async |
Presign
PUT |
presign_put |
GET |
presign_get |
DELETE |
presign_delete |
GET
There are a few different options for getting an object. sync
and async
methods are generic over std::io::Write
,
while tokio
methods are generic over tokio::io::AsyncWriteExt
.
async/sync/async-blocking |
get_object |
async/sync/async-blocking |
get_object_stream |
PUT
Each GET
method has a PUT
companion sync
and async
methods are generic over std::io::Read
. async
stream
methods are generic over futures_io::AsyncReadExt
, while tokio
methods are generic over tokio::io::AsyncReadExt
.
async/sync/async-blocking |
put_object |
async/sync/async-blocking |
put_object_with_content_type |
async/sync/async-blocking |
put_object_stream |
List
async/sync/async-blocking |
list |
DELETE
async/sync/async-blocking |
delete_object |
Location
async/sync/async-blocking |
location |
Tagging
async/sync/async-blocking |
put_object_tagging |
async/sync/async-blocking |
get_object_tagging |
Head
async/sync/async-blocking |
head_object |
Usage (in Cargo.toml
)
[dependencies]
rust-s3 = "0.28"