05 · Connect Storage
Register and manage the object-storage backends where your Delta tables live.
Eddytor works on Delta tables in your own object storage - it never copies your data. Before you can create or read a table, you register at least one storage connection pointing at a bucket or container.
In this section
- How registration works - the
probe, discovery, and the
config_idyou'll reuse. - Amazon S3 - plus MinIO / R2 / Hetzner and any S3-compatible endpoint.
- Google Cloud Storage.
- Azure Blob - access key, SAS, service principal, managed identity, or a linked identity (and OneLake).
- Bundled Garage (evaluation only) - the in-cluster S3 for demos.
- Managing & deleting at the S3 layer - last-resort cleanup of orphaned data.
Good to know
Registering a connection also discovers the tables
already in the bucket - an empty bucket is fine (it just reports 0 tables). You
own the data; Eddytor only connects to it.
Next
- Create your first table once a connection exists.
- Prefer a delegated, per-user link? See Provider linking.