AWS Aurora PostgreSQL as a db backend?
For compliance reasons, we need to self-host. We're an AWS-based shop and would prefer to use AWS Aurora PostgreSQL for our backend instead of a docker or EC2 based Postgres database. The problem is, we don't have access to the postgres user and all the Supabase init scripts assume you are running as that user. We were able to work around that by making some small tweaks to the scripts and preparing an admin-style account on our own ahead of time, but when we try to start up the realtime container, the eval Realtime.Release.migrate portion of the command fails.
1 Reply
The issue seems to be related to pg_stat_statements extension. We already have the extension installed and the admin-style user we're using doesn't have access to change it since Aurora requires you to do that type of things through parameter groups instead of commands. We do not have access to the code in the migration or we could just remove the things that aren't allowed on Aurora, but it's baked into the realtime binary, it seems.