You can now migrate your existing databases to AWS

We're excited to introduce new CLI commands that make it easy to migrate your existing databases from Fly.io to AWS.

If you haven't yet caught up on the details about our new AWS architecture, you can read more about Turso Cloud on AWS, and How We Built a Fully S3-Based Database Architecture.

#We've already migrated free tier users

The good news for free tier users is that there's nothing to do! We've migrated most of our free tier users to AWS already. If you're on a paid plan, you can now also move your databases to AWS, which also means you get a new price if you subscribe to the Developer Plan.

#New CLI commands for AWS migration

We've added three new commands to the Turso CLI to help you manage the migration process:

turso group aws-migration info <group-name>   # Shows status of the group migration process
turso group aws-migration start <group-name>  # Start migration process for selected group
turso group aws-migration abort <group-name>  # Abort migration process for selected group

#Important considerations before migrating

Before you begin the migration process, please note:

Migration is irreversible: Once you migrate to AWS, you cannot migrate your database back to Fly. However, you can abort the process with the turso group aws-migration abort <group-name> command if some databases weren't migrated yet.
Deprecated features: After migrating to AWS, the following features that were available on Fly will no longer work:
- ATTACH between group databases
- Multi-DB Schemas
- Server-side WebSockets (switch from wss:// to libsql://)
- Edge Replicas
Python SDK compatibility: If you're using the Python SDK, we recommend delaying migration until the new client is officially released, as the current version is incompatible with AWS.
Extension support: Some lesser-known extensions (e.g., sqlite-vss, sqlite-geopoly) aren't supported on AWS. Please confirm your required extensions are available before migrating.

#Migration process

All databases from your group will be migrated to the closest region to the group primary. During migration, databases remain online for read-only access. Writes are paused until the transfer completes—typically under a minute, but it may take longer for large databases (1 GB+).

After migration, we recommend updating the URL for all migrated databases of the group. You can get the new URL with the turso db show <db-name> command.

Ready to make the move? Try out the new commands today!