docs(services/s3): update Tigris endpoint and enrich compatible servi…#7946
Merged
Merged
Conversation
…ce 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 <davidmyriel@gmail.com>
dosubot
Bot
added
size:S
Member
|
Hey @davidmyriel , nice to meet you again |
Xuanwo
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Tigris section of the S3 compatible services doc pointed at the legacy fly.storage.tigris.dev endpoint.
This updates it to the current
https://t3.storage.devendpoint (legacy still works and is noted), documents credential configuration via standard S3 access keys / AWS environment variables, and adds brief notes on Tigris behavior relevant to OpenDAL users.Follow-up to #7639.
edit - nice to cross paths again @Xuanwo :) Hope you're good!