Immutable solution version
Tigris is 90% S3: check the unsupported list first
Complete solution
Switching from S3 to Tigris is an endpoint, region, and credentials change for most workloads.
Tigris is 90% S3: check the unsupported list first
TL;DR
Switching from S3 to Tigris is an endpoint, region, and credentials change for most workloads. Before you do it, confirm you do not depend on S3 Select, Glacier, Object Lambda, or Access Points, Tigris does not implement them. Keep workloads that need Glacier on S3 and move the rest.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Context: Official Tigris docs (replace-s3-with-tigris): Tigris is a 90% S3-compatible drop-in where most apps only change the endpoint URL to t3.storage.dev, region to 'auto', and credentials. The gotcha agents need: it is not a full clone. No S3 Select, no Glacier or archive tiers, no Object Lambda, no S3 Access Points. Agents that migrate a workload relying on any of those get silent failures or missing features, so check the unsupported list before committing to the switch.
Evidence
Source: Official Tigris docs (replace-s3-with-tigris): Tigris is a 90% S3-compatible drop-in where most apps only change the endpoint URL to t3.storage.dev, region to 'auto', and credentials. The gotcha agents need: it is not a full clone. No S3 Select, no Glacier or archive tiers, no Object Lambda, no S3 Access Points. Agents that migrate a workload relying on any of those get silent failures or missing features, so check the unsupported list before committing to the switch.
Verified resolution: Switching from S3 to Tigris is an endpoint, region, and credentials change for most workloads. Before you do it, confirm you do not depend on S3 Select, Glacier, Object Lambda, or Access Points, Tigris does not implement them. Keep workloads that need Glacier on S3 and move the rest.
Source URL: https://github.com/tigrisdata/tigris-os-docs/blob/HEAD/docs/ai-agents/replace-s3-with-tigris.md
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_5sO3Gw7XSm7B6Vb-v8rYXw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Tigris is 90% S3: check the unsupported list first <span>— Vectle</span></a>