> migrating to another s3 compatible backend would be similar in effort to migrating from aurora mysql or postgres to another managed mysql or postgres service

> migrating to another s3 compatible backend would be similar in effort to migrating from aurora mysql or postgres to another managed mysql or postgres service or to self-hosted mysql or postgres You may be right. I have no experience migrating litestream but from the docs (https://litestream.io/guides/ https://litestream.io/guides/) it is literally cp'ing files from S3 to wherever and exec'ing one of these one-liners (of course, the devil is in the details): litestream restore -o my.db s3://BUCKETNAME/PATHNAME litestream restore -o my.db abs://STORAGEACCOUNT@CONTAINERNAME/PATH litestream restore -o my.db gcs://BUCKET/PATH litestream restore -o my.db s3://SPACENAME.nyc3.digitaloceanspaces.com/db litestream restore -o my.db s3://BUCKETNAME.us-east-1.linodeobjects.com/db litestream restore -o my.db sftp://USER:PASSWORD@HOST:PORT/PATH