Migrating a production project to another region (ap-southeast-2 → us-east-1) with Auth + Storage — lowest-downtime approach? #47248
-
|
I need to move a live production project from ap-southeast-2 (Sydney) to us-east-1 (N. Virginia) to co-locate it with my backend (AWS EC2 in us-east-1). Right now every DB call crosses the Pacific, so API requests are ~700ms (should be ~150-200ms co-located) and direct Postgres pooler connects take ~2s. My understanding is that a project's region can't be changed in place — you create a new project in the target region and migrate into it. I'd like to confirm that and learn the cleanest path. My stack:
It's a live project with real customers, so I want minimal downtime and zero data loss.
Any battle-tested runbook or scripts appreciated. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
I have not done the migration so will only confirm that is the only way. You are not missing some secret way. The migration guide https://supabase.com/docs/guides/platform/migrating-within-supabase/backup-restore covers how to copy the storage data with a js script. Auth should just transfer as password will work. Users will have to login though. 2 is a good idea basically prove you know what to do, don't have steps missing or some config you need to make sure you set up. |
Beta Was this translation helpful? Give feedback.
I have not done the migration so will only confirm that is the only way. You are not missing some secret way.
The migration guide https://supabase.com/docs/guides/platform/migrating-within-supabase/backup-restore covers how to copy the storage data with a js script. Auth should just transfer as password will work. Users will have to login though.
2 is a good idea basically prove you know what to do, don't have steps missing or some config you need to make sure you set up.