Tigris
Connect Tigris object storage to BucketMate Web with a Tigris access key
BucketMate Web connects to Tigris through its S3-compatible endpoint. Make sure the companion browser extension is connected before testing the connection.
Prerequisites
- Tigris account, or a Fly.io organization with Tigris storage
- Access key ID, starting with
tid_ - Secret access key, starting with
tsec_ - Bucket
- BucketMate browser extension
Endpoint and region
Use this endpoint:
https://t3.storage.dev
The region is always auto. The older https://fly.storage.tigris.dev endpoint still works.
Connection steps
- Open the Tigris console at console.storage.dev. Fly.io users can sign in with Fly.io.
- Go to Access Keys and create a key.
- Give the key access to the buckets you want to browse.
- Copy the access key ID and secret access key. If you created the bucket with
fly storage create, you can use the keys it printed instead. - Open BucketMate Web.
- Confirm the extension shows Connected in Settings > Advance.
- Choose Add connection.
- Select Tigris.
- Enter
https://t3.storage.dev. - Keep the region
auto. - Enter the access key ID and secret access key.
- Use Test Connection.
- Choose Save Connection.
Common issues and fixes
Access denied
The access key has no role on the bucket. In the Tigris console, open Access Keys and give the key access to the bucket.
Invalid access key
The key was deleted, or the key and secret were swapped. Access key IDs start with tid_ and secrets start with tsec_.
SignatureDoesNotMatch
The secret is wrong or the region isn't auto. Set the region to auto and paste the secret again.
Virtual-hosted requests
New Tigris buckets only accept virtual-hosted style requests, such as https://<bucket>.t3.storage.dev/<key>. BucketMate Web uses virtual-hosted style for Tigris endpoints automatically.
Buckets do not load
If the key can only access some buckets, add bucket names in Explicit buckets.