Crates.io | s3s-test |
lib.rs | s3s-test |
version | |
source | src |
created_at | 2024-10-11 13:59:32.144023 |
updated_at | 2024-10-11 13:59:32.144023 |
description | s3s test suite |
homepage | |
repository | https://github.com/Nugine/s3s |
max_upload_size | |
id | 1405355 |
Cargo.toml error: | TOML parse error at line 17, column 1 | 17 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
size | 0 |
S3 Service Adapter
crate | version | docs |
---|---|---|
s3s | ||
s3s-aws | ||
s3s-fs |
This experimental project intends to offer an ergonomic adapter for building S3-compatible services.
s3s
implements Amazon S3 REST API in the form of a generic hyper service. S3-compatible services can focus on the S3 API itself and don't have to care about the HTTP layer.
s3s-aws
provides useful types and integration with aws-sdk-s3
.
s3s-fs
implements the S3 API based on file system, as a sample implementation. It is designed for integration testing, which can be used to mock an S3 client. It also provides a binary for debugging. Play it!
The diagram above shows how s3s
works.
s3s
converts HTTP requests to operation inputs before calling the user-defined service.
s3s
converts operation outputs or errors to HTTP responses after calling the user-defined service.
The data types, serialization and deserialization are generated from the smithy model in aws-sdk-rust repository. We apply manual hacks to fix some problems in smithy server codegen and make s3s
ready to use now.
S3Service
and other adapters in this project have no security protection. If they are exposed to the Internet directly, they may be attacked.
It is up to the user to implement security enhancements such as HTTP body length limit, rate limit and back pressure.
We have a reward funds pool for contributors: https://github.com/Nugine/s3s/issues/174
If my open-source work has been helpful to you, please sponsor me.
Every little bit helps. Thank you!