The S3 door (retired) and the Files API
Relata DB 3.0
This page describes Relata DB 3.0, the current release. The 2.5.8 line still serves the S3-compatible door described in earlier versions of this page.
In 3.0 Relata no longer serves an S3-compatible API to clients. boto3, the aws CLI, rclone and MinIO clients cannot be pointed at it. Stored S3Object and S3Bucket rows and their provenance are kept. Relata's internal S3-compatible object-store backend (for blobs, backups and storage) is separate and unaffected.
Use the HTTP Files API
| Operation | Route |
|---|---|
| List objects in a logical bucket | GET /v1/files |
| Upload or replace an object | PUT /v1/files/content?key=... |
| Download an object | GET /v1/files/content?key=... |
| Delete one exact key | DELETE /v1/files/content?key=... |
| Create a folder marker | POST /v1/files/folders |
| Large uploads | POST /v1/files/uploads, PUT /v1/files/uploads/{upload_id}, POST /v1/files/uploads/{upload_id}/complete |
Every file operation runs through the same governed path as the rest of the API: ACL, tenant scoping, provenance and audit.
It is not an S3-compatible endpoint. Clients must migrate:
- request signing (SigV4) to a registry bearer token;
- multipart upload semantics to the
uploadsroutes; - versioning, bucket management and event notifications, which have no equivalent (history is bi-temporal in the engine instead);
- prefix and delimiter listing behaviour, which should be validated on representative data.
For objects already in an external S3 bucket, read them with your own ETL client (OpenETL) and write them with PUT /v1/files/content, or hand prepared extracted rows to POST /v1/ingest/bulk.