Skip to main content

tigrbl_engine_s3

Discord community for tigrbl_engine_s3 Apache 2.0 license Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl_engine_s3

What is tigrbl_engine_s3?

tigrbl_engine_s3 is a standalone Tigrbl object-storage engine that calls the S3 API directly through a boto3-compatible client. It supports AWS S3 and S3- compatible services such as MinIO or R2 when configured with an endpoint URL.

Why use tigrbl_engine_s3?

Use it when an application needs direct S3 request semantics, credential-chain behavior, endpoint configuration, or server-side upload options.

When should I install tigrbl_engine_s3?

Install it for object-native Tigrbl workloads that should communicate through a boto3-compatible S3 client.

Who is tigrbl_engine_s3 for?

It is for application developers and platform engineers integrating Tigrbl with AWS S3 or an S3-compatible service.

Where does tigrbl_engine_s3 fit?

It is a layer-90 standalone engine package and depends on the public tigrbl facade plus boto3.

How does tigrbl_engine_s3 work?

Its plugin builds an S3Engine and S3Session; sessions translate strict logical object keys into direct put_object, get_object, and related calls.

Install

uv add tigrbl_engine_s3

Surface Coverage

The session API is object-native:

  • 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 direct S3 object I/O, logical key normalization, local session staging, upload options, 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

  • S3Engine
  • S3Session
  • s3_engine() and s3_capabilities()
  • register() under the tigrbl.engine entry-point group

Usage Examples

Configuration

from tigrbl import EngineSpec

engine, make_session = EngineSpec.from_any(
    {
        "kind": "s3",
        "bucket": "documents",
        "prefix": "tenant-a",
        "region_name": "us-east-1",
        "endpoint_url": "http://localhost:9000",
        "cas": True,
        "put_options": {"ServerSideEncryption": "AES256"},
    }
).build()

Credentials follow boto3's normal provider chain. Explicit access_key, secret_key, and session_token mappings are also accepted. Tests and custom integrations can inject an existing client as mapping["client"].

Content-addressed storage

CAS is opt-in with "cas": True. The returned address is sha256:<hex> and the physical object is sharded below .cas/sha256 by default. Retrieval hashes the received bytes and fails if they do not match the requested address.

S3 is not a multi-object transactional store. begin() provides local staging and rollback before upload, but commit() is a sequence of remote S3 calls and can be partially applied if a later request fails.

How To Choose This Package

Choose this package for direct boto3-compatible S3 calls. Choose tigrbl_engine_s3fs when the fsspec/s3fs filesystem interface is preferable.

  • tigrbl
  • tigrbl_engine_s3fs

Support

Package-local Boundary

This README is the package-local distribution entry point for tigrbl_engine_s3. 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_s3 0.4.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for tigrbl_engine_s3 0.4.5
File Size Uploaded Provenance Actions
tigrbl_engine_s3-0.4.5.tar.gz 12.2 kB Without provenance Details for tigrbl_engine_s3-0.4.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tigrbl_engine_s3 0.4.5
File Interpreter ABI Platform Actions
tigrbl_engine_s3-0.4.5-py3-none-any.whl Python 3 none any Details for tigrbl_engine_s3-0.4.5-py3-none-any.whl

Total release size: 24.9 kB

Release files / tigrbl_engine_s3-0.4.5.tar.gz

Download URL tigrbl_engine_s3-0.4.5.tar.gz
Size 12.2 kB
Tags Source
SHA-256 checksum
How to use checksums
89dacfd8510715f09087d3a9ae2c2311d0bddea035af8530de3c3e54301ecf36
BLAKE2b-256 checksum
How to use checksums
f2c35600ade7e92f8ec3410c970df4bdff4505f7dcbb4b6719dad1e0b558a489
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_s3-0.4.5-py3-none-any.whl

Download URL tigrbl_engine_s3-0.4.5-py3-none-any.whl
Size 12.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c7e0740b2bdef248cda3dcf3d0bc6c28ce9eb4abba7ca55a22fa96072603d760
BLAKE2b-256 checksum
How to use checksums
098a67caf3bc51cf74049285aad9f9df2d45eddb146f71a3cf9e865021f82694
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_s3 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.

Release history Release notifications | RSS feed

This release

0.4.5 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page