Back to articles

Storage / Tasmanian Cloud

S3 compatibility without moving the boundary

Use familiar object APIs while the storage plane remains hosted in Tasmania.

S3 object storage boundary diagramTasmanian Cloud s3 object storage boundary diagram.TASMANIAN CLOUD STORAGE PLANES3 CLIENTrcSDKS3 APIcompatibleauth and policyRUSTFSobjectsversionsPOLICYlifecyclereplicationS3 compatibility at the edge. Sovereign storage behind it.

Keep the client

S3 compatibility lets existing command-line tools, SDKs, backup jobs, and application libraries use a familiar object model. The customer does not need to replace every object client to use the Tasmanian storage plane.

Keep the boundary

The compatibility endpoint is not the same as outsourcing the storage decision. The storage service, access policy, lifecycle rules, and data location remain part of the Tasmanian Cloud operating boundary.

Object state is operational state

Versioning, lifecycle policy, retention, and access keys affect how an application behaves. They belong in the same resource model as the bucket instead of being left as undocumented settings in a console.

Use it where it fits

S3 storage is useful for backups, artifacts, uploads, reports, and application objects. It is not a replacement for a database or a block device. The API and SDK surface should make that distinction clear.

Need the implementation details?

Read the Tasmanian Cloud documentation ↗