Skip to main content

Object Storage

Object Storage, previously known as Datasets (EOS), is backed by a bucket in E2E Object Storage (EOS), an S3-compatible store. Use it for training data, checkpoints, and artifacts that need to grow without a fixed size, be read by several workloads at once, or be reached from outside TIR with an S3 CLI or SDK.

In the TIR portal it lives under Storage > Object Storage. Each bucket has a bucket name, which is what EOS knows it as, and an alias, its name inside TIR.

S3-Compatible EOS BucketObject VersioningObject Lock (WORM)Lifecycle RulesPresigned URLsRead-Only Mounts

Where it is used​

Buckets always mount read-only. Where the bucket appears depends on what you attach it to:

Buckets are also the destination for Data Syncer transfers and the store behind fine-tuning data.

API Reference​

REST API

</>Object Storage API Reference

Create and manage buckets, objects, versioning, locks, and replication.

Explore REST APIs
Authentication & Endpoints
Request and Response Schemas
Open API Reference →
tir.e2enetworks.com / api / v1
POST/datasets/Create Object Storage
GET/datasets/List Object Storage
GET/datasets/{Dataset_Id}/objects/List Data Objects
PUT/datasets/{Dataset_Id}/versioning/Enable or Suspend Versioning
PUT/datasets/{Dataset_Id}/lock/Set Bucket Lock Configuration
POST/datasets/{Dataset_Id}/presigned-urlGenerate Presigned URL
POST/datasets/{Dataset_Id}/replication/Create Replication Rule
PUT/datasets/{Dataset_Id}/objects/empty/Empty Bucket
DELETE/datasets/{Dataset_Id}/Delete Object Storage

Billing & Plans​

Billing & Credits

Object Storage is billed on peak usage per calendar month, plus data transfer.

View Billing Docs →

Peak Usage

Charged on the highest storage reached during the month.

No Fixed Size

Capacity grows with your data; nothing to pre-allocate.

Pricing Page

Slab rates, worked examples, and a Block Storage comparison.

Last updated on October 19, 2026.