Tasmanian Cloud documentation
Object storage
S3-compatible object storage inside the Tasmanian Cloud boundary
Tasmanian Cloud provides S3-compatible object storage for backups, artifacts, uploads, reports, and application data. The object API is familiar. The storage boundary and access policy remain part of the platform design.
Use familiar tools
Existing S3 clients, SDKs, and backup jobs can connect to the object endpoint. Use the API and portal for bucket and access configuration. Use an S3 client for object operations.
Keep object state explicit
Buckets can use the object features the workload needs:
- object versioning for recovery from an overwrite or delete
- lifecycle rules for expiration and retention workflows
- access keys scoped to the bucket or application that uses them
- immutable retention where the workload requires an object not to be changed during a defined period
The available feature set depends on the current service configuration. Confirm the scope before treating a feature as a guarantee.
Keep storage separate from compute
Object storage is a good boundary for backups, build artifacts, uploads, and reports. It is not a database or a block device. Use a VM, container, or managed data service when the application needs transactional or low-latency state.
Access and secrets
Do not copy long-lived object credentials through application repositories or shared .env files. Use the secret and capability path where available, and scope a key to the workload that needs it.