Different credentials for PostgreSQL Read Replicas
M
Marc Köhlbrugge
Right now replicas have the same credentials as the primary database.
This limits its usefulness as a way to provide certain people or applications with read-only access.
In addition to that, it means the Replica database is incompatible with Ruby on Rails's native "multiple database" functionality as it requires having a distinct user for each database:
>> Second, the username for the writers and replicas should be different, and the replica user's database permissions should be set to only read and not write.
I expect few customers needing to specify their own credentials. Anything that is different from the primary database should suffice both use cases.
Log In
S
Sean Yu
Really want this as well. Want to give read access to a third party for analytics. Right now, the access I'd give would also give that third party access to our primary with writes, which is very unsafe. Makes that entire workflow for us impossible.
This means having different authentication credentials, as well as it's own separate ip whitelisting for access control
c
colin
Upvoting, we want to give read only access to a third party, and this is currently impossible. Would be great if a member of the Render team could provide some feedback on this feature request.
In addition, it'd be nice if the external access controls could be set differently for the replica. There's no way to define a different set of IP addresses for the replica to the primary database.
M
Marc Köhlbrugge
Ok turns out I was wrong about the Rails part and it's actually possible to get it working using the same credentials.