What is tigrbl_engine_s3fs?
tigrbl_engine_s3fs is a standalone Tigrbl object-storage engine backed by
the synchronous s3fs.S3FileSystem interface. It supports AWS S3 and S3-
compatible endpoints accepted by s3fs.
Why use tigrbl_engine_s3fs?
Use it when an application already uses the fsspec/s3fs ecosystem or needs a filesystem-shaped adapter over S3 object storage.
When should I install tigrbl_engine_s3fs?
Install it for object-native Tigrbl workloads that should share s3fs configuration and client behavior.
Who is tigrbl_engine_s3fs for?
It is for application developers and data engineers integrating Tigrbl with S3 through the fsspec family.
Where does tigrbl_engine_s3fs fit?
It is a layer-90 standalone engine package and depends on the public tigrbl
facade plus s3fs.
How does tigrbl_engine_s3fs work?
Its plugin builds an S3FSEngine and S3FSSession; sessions translate strict
logical object keys into bucket/prefix paths on an S3FileSystem.
Install
uv add tigrbl_engine_s3fs
Surface Coverage
The engine exposes object-oriented session methods rather than pretending that S3 is a relational database:
put_object(key, data),get_object(key),delete_object(key)object_exists(key),head_object(key),list_objects(prefix="")- optional
put_cas(data),get_cas(address),cas_exists(address)
What It Owns
This package owns s3fs-backed object I/O, logical key normalization, local
session staging, and optional SHA-256 content-addressed storage. Its engine
implements the canonical EngineBase contract while retaining this
object-specific surface.
Public API and Import Surface
S3FSEngineS3FSSessions3fs_engine()ands3fs_capabilities()register()under thetigrbl.engineentry-point group
Usage Examples
Configuration
from tigrbl import EngineSpec
engine, make_session = EngineSpec.from_any(
{
"kind": "s3fs",
"bucket": "documents",
"prefix": "tenant-a",
"endpoint_url": "http://localhost:9000",
"key": "minioadmin",
"secret": "minioadmin",
"cas": True,
}
).build()
For custom clients and tests, pass an existing filesystem as mapping["fs"].
All keys are bucket-relative and reject absolute paths and traversal segments.
Content-addressed storage
CAS is opt-in with "cas": True. put_cas(payload) returns a
sha256:<hex> address. Objects are stored below .cas/sha256 by default and
retrieval verifies that the stored bytes still match the requested digest.
Override the physical CAS prefix with cas_prefix or disable read verification
with verify_cas=False only when verification is performed at another layer.
Transactions are reported as non-atomic because S3 has no multi-object commit.
A session opened with begin() stages changes until commit() and supports
local rollback, but a remote failure during commit can leave a partial batch.
How To Choose This Package
Choose this package for the s3fs/fsspec interface. Choose tigrbl_engine_s3
when direct access to the boto3 S3 API and its request options is preferable.
Related Packages
tigrbltigrbl_engine_s3
Documentation Links
Support
Package-local Boundary
This README is the package-local distribution entry point for
tigrbl_engine_s3fs. Cross-package claims and release status remain governed
by the repository docs and .ssot/registry.json.
Certification Status
The implementation has package-scoped fake-backend tests and build validation. It does not claim live AWS or S3-compatible service conformance yet.
License
Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.
Metadata
Release files for tigrbl_engine_s3fs 0.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| tigrbl_engine_s3fs-0.4.5.tar.gz | 11.9 kB | Without provenance | Details for tigrbl_engine_s3fs-0.4.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_engine_s3fs-0.4.5-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_engine_s3fs-0.4.5-py3-none-any.whl |
Total release size: 24.3 kB
Release files / tigrbl_engine_s3fs-0.4.5.tar.gz
| Download URL | tigrbl_engine_s3fs-0.4.5.tar.gz |
|---|---|
| Size | 11.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e6139d8873115fe2127e7c116ba49b3d7cb35ca8be866a8478a8c7a4dbb952d2
|
|
BLAKE2b-256 checksum How to use checksums |
8d7c1632c5ab0425c798d42e71e2e6fc8bf15c787e2cd7d9dfcfe51b91d5b0e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tigrbl_engine_s3fs-0.4.5-py3-none-any.whl
| Download URL | tigrbl_engine_s3fs-0.4.5-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b61c6ab30cfcadd19180a9491e90e75131250922bc29ddf0026e81d4fbdc010e
|
|
BLAKE2b-256 checksum How to use checksums |
7f03a330ed8ca20f00644e0590bf178474e4c54cd1c96a032998ba55ee4eb9ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tigrbl_engine_s3fs 0.4.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.