Migrate Lovable and Supabase-based SaaS to AWS
Budget: $250 – $750 USD
## Job Title
**Full-Stack Cloud Engineer: Migrate Lovable and Supabase-based SaaS to AWS (Postgres, Auth, Edge Functions)**
## Project Overview
We are looking for an experienced Cloud Migration Specialist to move our existing application from **Supabase Cloud** to a self-managed **AWS infrastructure**.
Our service is a digital vault and asset management platform ("Relay") built with **React (Vite), TypeScript, and Tailwind CSS**. The current backend logic relies heavily on Supabase-specific features, and we need to replicate this functionality 1:1 within the AWS ecosystem to improve scalability and allow for custom domain branding (specifically for Google OAuth).
---
## Current Status
* **Frontend:** React (Vite) / TypeScript / shadcn/ui.
* **Database:** PostgreSQL (Supabase) with ~10 tables including `profiles`, `assets`, and `beneficiaries`.
* **Auth:** Supabase Auth (Email + Google OAuth).
* **Serverless Logic:** ~8 Deno-based Supabase Edge Functions (e.g., asset encryption, email triggers, incident notifications).
* **Storage:** Supabase Storage for user-uploaded asset metadata.
---
## Required Outcome & AWS Services
The goal is a complete "de-bundling" of Supabase into the following AWS services:
1. **Database:** Migrate Postgres schema and data to **Amazon RDS (PostgreSQL)**.
2. **Authentication:** Replace Supabase Auth with **Amazon Cognito**. This must include:
* Migrating existing user records.
* Configuring Google OAuth with a **custom domain callback URL**.
3. **Storage:** Migrate files to **Amazon S3**.
4. **Edge Functions:** Port existing TypeScript/Deno logic to **AWS Lambda** (Node.js).
5. **API Layer:** Implement **Amazon API Gateway** to route frontend requests to the new Lambda functions.
6. **CI/CD:** Ensure the deployment pipeline is updated (using GitHub Actions or AWS Amplify).
---
## Key Responsibilities
* **Data Migration:** Export current Supabase data and import into RDS without data loss.
* **Auth Refactor:** Update the frontend `AuthContext` and Supabase client calls to use the **AWS Amplify SDK** or **Amazon Cognito Identity SDK**.
* **Function Porting:** Rewrite/adapt Deno Edge Functions to run as Node.js Lambda functions.
* **Security:** Map current Row Level Security (RLS) logic to application-level authorization within Lambda or IAM policies.
---
## Candidate Requirements
* **Proven Experience:** At least 2 successful Supabase-to-AWS or Firebase-to-AWS migrations.
* **Stack Mastery:** Expert-level Node.js/TypeScript, PostgreSQL, and React.
* **AWS Expertise:** Strong knowledge of **Cognito, RDS, S3, and Lambda**.
* **Communication:** Ability to provide a clear migration plan and document the new environment variables and architecture.
---
## To Apply
Please start your proposal with the word **"RELAY"** so I know you’ve read the full description.
Include:
1. A brief summary of a similar migration you’ve performed.
2. Your estimated timeline for a project of this scale (10 tables, 8 functions).
3. Your preference for infrastructure management (Console, Terraform, or AWS CDK).
**Full-Stack Cloud Engineer: Migrate Lovable and Supabase-based SaaS to AWS (Postgres, Auth, Edge Functions)**
## Project Overview
We are looking for an experienced Cloud Migration Specialist to move our existing application from **Supabase Cloud** to a self-managed **AWS infrastructure**.
Our service is a digital vault and asset management platform ("Relay") built with **React (Vite), TypeScript, and Tailwind CSS**. The current backend logic relies heavily on Supabase-specific features, and we need to replicate this functionality 1:1 within the AWS ecosystem to improve scalability and allow for custom domain branding (specifically for Google OAuth).
---
## Current Status
* **Frontend:** React (Vite) / TypeScript / shadcn/ui.
* **Database:** PostgreSQL (Supabase) with ~10 tables including `profiles`, `assets`, and `beneficiaries`.
* **Auth:** Supabase Auth (Email + Google OAuth).
* **Serverless Logic:** ~8 Deno-based Supabase Edge Functions (e.g., asset encryption, email triggers, incident notifications).
* **Storage:** Supabase Storage for user-uploaded asset metadata.
---
## Required Outcome & AWS Services
The goal is a complete "de-bundling" of Supabase into the following AWS services:
1. **Database:** Migrate Postgres schema and data to **Amazon RDS (PostgreSQL)**.
2. **Authentication:** Replace Supabase Auth with **Amazon Cognito**. This must include:
* Migrating existing user records.
* Configuring Google OAuth with a **custom domain callback URL**.
3. **Storage:** Migrate files to **Amazon S3**.
4. **Edge Functions:** Port existing TypeScript/Deno logic to **AWS Lambda** (Node.js).
5. **API Layer:** Implement **Amazon API Gateway** to route frontend requests to the new Lambda functions.
6. **CI/CD:** Ensure the deployment pipeline is updated (using GitHub Actions or AWS Amplify).
---
## Key Responsibilities
* **Data Migration:** Export current Supabase data and import into RDS without data loss.
* **Auth Refactor:** Update the frontend `AuthContext` and Supabase client calls to use the **AWS Amplify SDK** or **Amazon Cognito Identity SDK**.
* **Function Porting:** Rewrite/adapt Deno Edge Functions to run as Node.js Lambda functions.
* **Security:** Map current Row Level Security (RLS) logic to application-level authorization within Lambda or IAM policies.
---
## Candidate Requirements
* **Proven Experience:** At least 2 successful Supabase-to-AWS or Firebase-to-AWS migrations.
* **Stack Mastery:** Expert-level Node.js/TypeScript, PostgreSQL, and React.
* **AWS Expertise:** Strong knowledge of **Cognito, RDS, S3, and Lambda**.
* **Communication:** Ability to provide a clear migration plan and document the new environment variables and architecture.
---
## To Apply
Please start your proposal with the word **"RELAY"** so I know you’ve read the full description.
Include:
1. A brief summary of a similar migration you’ve performed.
2. Your estimated timeline for a project of this scale (10 tables, 8 functions).
3. Your preference for infrastructure management (Console, Terraform, or AWS CDK).
Related categories:
Linux
NoSQL Couch & Mongo
Amazon Web Services
Node.js
PostgreSQL
Frontend Development
Aws Lambda
Amazon S3
AWS Amplify
CI/CD