run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-07-18 15:54:38 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

Need help to migrate from self-hosted Supabase on AWS to Supabase SaaS #529

New Issue
Open
opened 2026-02-16 00:18:09 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 00:18:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @gllona on GitHub (Sep 5, 2025).

Hello,

We run a self-hosted Supabase instance installed on AWS using the CloudFormation repo https://github.com/gllona/supabase-on-aws , which I forked from https://github.com/supabase-community/supabase-on-aws (and did some minor changes trying to revive the Studio).

We are using Supabase mainly for auth purposes.

However, the mentioned repo from supabase-community is no longer maintained, which is risky for us due to lack of bug patches. Also, AWS has announced its end of support for Lambda functions running nodejs v18.x, which the Supabase components in the mentioned repo use.

Then I need to migrate my current Supabase on AWS instance to Supabase SaaS (new project in EU region). In this migration, I need to preserve all the current PostgreSQL database data, including everything related to the auth module, existing users, etc.

What could be the best migration strategy? I think I can not simply create a new Supabase SaaS instance, and replace the content of the "auth" schema with our current content from Supabase on AWS, because there could be schema differences due to Supabase version changes.

These are the Supabase components versions I use on AWS:

  • public.ecr.aws/supabase/gotrue:v2.139.1
  • public.ecr.aws/supabase/postgrest:v12.0.2
  • public.ecr.aws/supabase/realtime:v2.25.61
  • public.ecr.aws/supabase/storage-api:v0.46.5
  • public.ecr.aws/supabase/imgproxy:v1.2.0
  • public.ecr.aws/supabase/postgres-meta:v0.75.0

Any help is greatly appreciated.

Thank you,

Gorka Llona

Originally created by @gllona on GitHub (Sep 5, 2025). Hello, We run a self-hosted Supabase instance installed on AWS using the CloudFormation repo https://github.com/gllona/supabase-on-aws , which I forked from https://github.com/supabase-community/supabase-on-aws (and did some minor changes trying to revive the Studio). We are using Supabase mainly for auth purposes. However, the mentioned repo from `supabase-community` is no longer maintained, which is risky for us due to lack of bug patches. Also, AWS has announced its end of support for Lambda functions running nodejs v18.x, which the Supabase components in the mentioned repo use. Then I need to migrate my current Supabase on AWS instance to Supabase SaaS (new project in EU region). In this migration, I need to preserve all the current PostgreSQL database data, including everything related to the auth module, existing users, etc. What could be the best migration strategy? I think I can not simply create a new Supabase SaaS instance, and replace the content of the "auth" schema with our current content from Supabase on AWS, because there could be schema differences due to Supabase version changes. These are the Supabase components versions I use on AWS: - public.ecr.aws/supabase/gotrue:v2.139.1 - public.ecr.aws/supabase/postgrest:v12.0.2 - public.ecr.aws/supabase/realtime:v2.25.61 - public.ecr.aws/supabase/storage-api:v0.46.5 - public.ecr.aws/supabase/imgproxy:v1.2.0 - public.ecr.aws/supabase/postgres-meta:v0.75.0 Any help is greatly appreciated. Thank you, Gorka Llona
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#529
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?