Component 06
Private S3 object storage for Rizoma Mesh.
RizomaOS gives applications an S3-compatible storage endpoint reachable only through the mesh. Teams get bucket/object workflows, multipart uploads, quotas, policies, and erasure-coded storage without placing an object store on the public internet.
Storage loop
endpoint = mesh IP port 9000, scope = 100.64.0.0/10 only
client = AWS CLI, S3 SDK, internal service, Webpanel
controls = bucket policy, quota, lifecycle, notifications
resilience = 4+2 erasure coding with BLAKE3 integrity
Object storage that belongs to the private network.
Architecture
Object storage that belongs to the private network.
The storage service is not a public S3 clone. Applications connect through mesh identity, the S3 API terminates on a private RizomaOS endpoint, and objects are placed across storage nodes as erasure-coded shards.
Access
AWS CLI, S3 SDKs, internal services, and Webpanel workflows target a mesh endpoint instead of a public bucket URL.
S3 API
Bucket, object, multipart, range, metadata, copy, and lifecycle operations on port 9000.
Erasure coding
Objects encoded into data and parity shards, distributed across mesh storage nodes, verified with BLAKE3.
Governance
Bucket policies, quotas, lifecycle rules, versioning, and notifications under platform control.
Security model
Private by network design, not perimeter filtering.
Storage should not need a public endpoint to be useful. Rizoma S3 keeps object storage inside the private mesh with service identity, policy controls, encryption, and integrity verification.
No public endpoint
Private by default
The S3 API binds to mesh addresses with no public DNS target or internet-facing listener.
Mesh identity
Authenticated requests
Requests arrive through mesh-authenticated paths, then bucket policies define access.
Encryption
SSE-S3 and SSE-C
Server-side encryption modes for workloads that require object-level encryption.
Integrity
BLAKE3 + healing
Shard metadata and checksums detect corruption; erasure coding allows reconstruction.
Deploy storage
Storage that belongs on your mesh, not on the public cloud.
Use Rizoma S3 when your applications need object storage that stays inside your infrastructure.