From 6bfe527ec0977a9c4cf3a2522c6609673eb0e43d Mon Sep 17 00:00:00 2001 From: David Myriel Date: Fri, 24 Jul 2026 14:56:31 +0000 Subject: [PATCH] docs(services/s3): update Tigris endpoint and enrich compatible service entry - Update the Tigris endpoint from the legacy fly.storage.tigris.dev to the current t3.storage.dev (legacy endpoint noted as still working) - Document credential configuration via standard S3 access keys / AWS env vars - Note single global endpoint, no egress fees, and zero-copy snapshots/forks with links to the relevant Tigris docs Signed-off-by: David Myriel --- core/services/s3/src/compatible_services.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/core/services/s3/src/compatible_services.md b/core/services/s3/src/compatible_services.md index 0fdfa4ef9755..258b6277e52d 100644 --- a/core/services/s3/src/compatible_services.md +++ b/core/services/s3/src/compatible_services.md @@ -89,18 +89,26 @@ To connect to COS, we need to set: [Tigris](https://www.tigrisdata.com/) is a globally distributed S3-compatible object storage service. +> Tigris serves data from the region nearest to the requester through a single global endpoint, and charges no egress fees. + To connect to Tigris, we need to set: -- `endpoint`: The endpoint of Tigris, for example: `https://fly.storage.tigris.dev` +- `endpoint`: The endpoint of Tigris: `https://t3.storage.dev` - `region`: The region of Tigris. Please set it to `auto`. - `bucket`: The bucket name of Tigris. +Credentials are standard S3 access keys, provided via `access_key_id`/`secret_access_key` or the `AWS_ACCESS_KEY_ID`/`AWS_SECRET_ACCESS_KEY` environment variables. See [Tigris S3 SDK docs](https://www.tigrisdata.com/docs/sdks/s3/) for details. + ```rust,ignore -builder.endpoint("https://fly.storage.tigris.dev"); +builder.endpoint("https://t3.storage.dev"); builder.region("auto"); builder.bucket(""); ``` +> `https://fly.storage.tigris.dev` is a legacy endpoint that still works, but `https://t3.storage.dev` is the current one. + +Tigris buckets support zero-copy [snapshots and forks](https://www.tigrisdata.com/docs/snapshots-and-forks/). A forked bucket is a regular bucket, so it can be read and written through OpenDAL like any other — useful for testing against production data without copying it. + ### Wasabi Object Storage [Wasabi](https://wasabi.com/) is a s3 compatible service.