Infrastructure & Migration

Supabase blocked in India? Here's how we migrated to AWS/GCP without rewriting the app

By GPT India  ·  March 2026

If your app relies on Supabase and you're seeing failures in India — auth breaking, DB timeouts, storage not working — you're probably affected by the domain-level blocking of supabase.com.

The good news: Supabase is open-source and can be deployed on your own infrastructure — including AWS or Google Cloud — without rebuilding your app.

We recently migrated multiple projects. Here's exactly how it works.

✦ ✦ ✦

Why This Is Possible

Supabase is built on open, composable components:

  • PostgreSQL
  • PostgREST
  • GoTrue (Auth)
  • Realtime
  • Storage service

Because of this architecture, you're not locked into the hosted platform. You can deploy your own Supabase stack on:

  • AWS (EC2 / ECS)
  • Google Cloud (Compute Engine / Cloud Run)
  • Any Docker-capable VM
💡
Your frontend code stays the same. You only change environment variables.
✦ ✦ ✦

How to Install Supabase on AWS or Google Cloud

Step 1 — Create a VM

On AWS

  • Launch EC2 (Ubuntu 22.04 recommended)
  • Open ports 80, 443, and required API ports

On GCP

  • Create Compute Engine VM
  • Allow HTTP/HTTPS traffic

Minimum recommendation: 2 vCPU · 4 GB RAM (more for production workloads)

Step 2 — Install Docker
sudo apt update
sudo apt install docker.io docker-compose -y
sudo systemctl enable docker
Step 3 — Deploy Supabase (Self-Hosted)
git clone https://github.com/supabase/supabase
cd supabase/docker
cp .env.example .env

Update in .env:

  • JWT secret
  • DB password
  • Site URL
  • SMTP settings

Then start:

docker compose up -d

This launches: PostgreSQL · Auth (GoTrue) · Realtime · PostgREST · Storage · Kong (API gateway)

✅
You now have a fully working Supabase backend running on your own cloud.
✦ ✦ ✦

Steps We Followed for Migration

1️⃣ Database Export

  • Dump schema
  • Dump data
  • Ensure extensions included
  • Preserve RLS policies
  • Backup functions & triggers

2️⃣ Import into New Instance

  • Restore schema
  • Restore data
  • Re-enable RLS
  • Validate constraints & indexes

3️⃣ Auth Migration

  • Export auth.users
  • Preserve password hashes
  • Reconfigure JWT
  • Test login/signup
🔐
No password resets required — hashes are carried over intact.

4️⃣ Storage Migration

  • Sync bucket files
  • Reconfigure storage path
  • Validate public/private access

5️⃣ Edge Functions & AI

If using:

  • Supabase Edge Functions
  • AI workflows
  • OpenClaw-based pipelines
  • Webhooks
  • No-code tools
  • Vibe coding stacks

We redeploy functions and update service keys accordingly.

6️⃣ Update App Configuration

Replace:

SUPABASE_URL SUPABASE_ANON_KEY SUPABASE_SERVICE_ROLE_KEY

Redeploy app. Test:

  • Login
  • CRUD operations
  • Realtime
  • File uploads
🎉
Done. Your app is now running on your own cloud, accessible from India without any domain-level restrictions.
✦ ✦ ✦

What We Need to Begin 🚀

To start the migration smoothly, we typically need:

🔐
Project access
📦
Database size estimate
⚙️
Current environment configuration
🌍
Hosting details (AWS / GCP / other)

From there, we handle the rest.

📩
If you're stuck mid-migration or want guidance:

Reach out at hi@gptindia.pro and we'll get your backend back online.