Tasmanian Cloud documentation

S3 object storage

Store objects through a familiar API inside the Tasmanian Cloud boundary

S3-compatible object storage gives applications and tools a familiar object interface while the storage service remains inside the Tasmanian Cloud operating boundary.

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

Good uses

Use object storage for:

  • backups and restore inputs
  • build artifacts and release bundles
  • customer uploads and generated files
  • reports, exports, and event archives

Use a database or block storage when the workload needs transactions, record locking, or a mounted filesystem.

Object lifecycle

Object state includes more than the current bytes. Plan the bucket with the workload's recovery and retention needs:

  • enable versioning when an earlier object state must be recoverable
  • use lifecycle rules when old objects or versions should expire
  • use immutable retention when a defined period must prevent changes
  • create scoped access credentials for applications and automation

The customer should choose these controls as part of the application design. They are not a substitute for a backup and restore test.

Client boundary

Use the portal or API to manage storage resources. Use standard S3 clients and SDKs to upload and read objects. The portal, CLI, SDK, REST API, and GraphQL API remain client surfaces over the same resource state.

Credentials

Keep object credentials behind the platform secret path where available. Avoid putting long-lived keys in source control, generated support bundles, or AI context windows.

Related