Turso Cloud on AWS is now available for everybody

Earlier in the year, we announced that the Turso Cloud would be offered primarily on AWS, as soon as we were ready to lift the beta label.

The day is finally here! And it comes with a new S3-native architecture that will facilitate running Turso Cloud – either as a serverless database or as a way to sync your Turso databases to and from the Cloud into native SQLite files.

#The Turso Cloud S3 native architecture

Turso Cloud ships with a native S3 architecture, which employs a combination of S3 and S3 express for data durability. Among the many advantages of this architecture is the fact that it makes it easy for us to offer the BYOC model, with the Turso cloud running inside your own account (coming soon!).

That means that all data is made durable on S3 express for every commit, and the local disks act as a cache for fast reads. An S3-native architecture for OLTP databases is not something commonly considered, but it is made possible for the Turso cloud due to two factors:

• massive multitenancy: since Turso Cloud uses a multi-tenant architecture, commits are batched across many databases.
• The latency of S3 express, advertised to be in the single-digit millisecond makes it viable to use it as a destination for the database’s write-ahead-log. For comparison, that is at the same range of the fsync() system call on EBS volumes, without which data isn’t really durable.

Details on the durability guarantees can be found here

#No cold starts

On our AWS regions, databases never have cold starts. That is made possible by our massively multitenant server, where every database is just a SQLite file, and the server itself is always up. Our S3-native architecture guarantees that databases can be moved to other servers when load increases.

#Moving out of Fly.io

Customers who have paid for Turso Cloud by March 21 can keep their databases on Fly, with migration being optional. The Turso team will provide migration tools for those who choose to move their databases to AWS.

Users on the free tier will be automatically migrated, starting on March 21st. The location to which the databases will be migrated will be according to the list below:

• us-east-1: atl, bog, bos, dfw, ewr, eze, gdl, gig, gru, iad, mia, ord, qro, yul, yyz
• eu-west-1: ams, arn, cdg, fra, jnb, lhr, mad, otp
• us-west-2: den, lax, phx, scl, sea, sjc
• ap-northeast-1: hkg, nrt, sin
• ap-south-1: bom, syd

#What this means for you

With our move to AWS complete, Turso Cloud users can expect improved reliability, and consistent performance. The S3-native architecture ensures your data remains secure and durable while maintaining the speed and flexibility you expect from Turso.

#Getting started

Ready to experience Turso Cloud on AWS? Existing users don’t need to take any action unless they wish to migrate from Fly.io. New users can sign up today and immediately benefit from our AWS infrastructure.

Join us as we enter this exciting new chapter for Turso Cloud, now powered by AWS and available to everyone!