tigris-s3-migration
Migrate to Tigris from S3/GCS/Azure
Migrate your object storage to Tigris with zero downtime. Tigris is S3-compatible, so most apps need only an endpoint and credential swap. Shadow buckets enable transparent migration without moving data upfront.
Prerequisites
Before doing anything else, install the Tigris CLI if it's not already available:
tigris help || npm install -g @tigrisdata/cli
If you need to install it, tell the user: "I'm installing the Tigris CLI (@tigrisdata/cli) so we can work with Tigris object storage."
Migration Strategies
More from tigrisdata/skills
tigris-object-operations
Use when working with objects in Tigris Storage - uploading, downloading, deleting, listing, getting metadata, or generating presigned URLs
71tigris-bucket-management
Use when creating, listing, inspecting, or deleting Tigris Storage buckets
68go-table-driven-tests
Write Go table-driven tests following established patterns. Use when writing tests, creating test functions, adding test cases, or when the user mentions "test", "table-driven", "Go tests", or testing in Go codebases.
67tigris-snapshots-forking
Use when needing point-in-time recovery, version control for object storage, or creating isolated bucket copies for testing/experimentation
64conventional-commits
Use when creating git commits, writing commit messages, or following version control workflows
62file-storage
Use when working with Tigris file storage - uploading, downloading, deleting, listing files, presigned URLs, client uploads, or setting up Tigris CLI and SDK. Covers Next.js, Remix, Express, Rails, and Laravel. For Python/Django, see the tigris-python-sdk skill.
43