1
Support for Distinct Credentials between Read Replica and Primary Database
Source: supabase/supabase#29911 · opened by @stinkymonkeyph
I believe having different passwords between your read replica and primary database is essential.
Enhanced Security: Different passwords for read replicas and primary databases provide an additional layer of security. Users can limit access to read replicas without exposing write permissions, reducing the risk of unauthorized changes.
Access Control: It allows administrators to assign different roles or permissions for read and write operations, helping segregate duties and protect sensitive operations.
Improved Flexibility: Users can better manage different user groups, such as read-only analytics teams, while ensuring that only trusted systems or personnel have write access to the primary database.
Enhanced Security: Different passwords for read replicas and primary databases provide an additional layer of security. Users can limit access to read replicas without exposing write permissions, reducing the risk of unauthorized changes.
Access Control: It allows administrators to assign different roles or permissions for read and write operations, helping segregate duties and protect sensitive operations.
Improved Flexibility: Users can better manage different user groups, such as read-only analytics teams, while ensuring that only trusted systems or personnel have write access to the primary database.
No pledges yet. Be the first to back this.
Comments
Similar requests
Authenticated API Endpoint to Restart / Toggle Database On & Off Remotely
2 votes · 0 comments
How to synchronize databases, documents to vector databases
3 votes · 0 comments
Postegres bank credentials stopped working on my n8n.
1 vote · 0 comments
NoSQL (Document) Database Alternative?
1 vote · 0 comments
# Proposal: Virtual Storage Columns (Seamless DB-to-Storage Mapping)
1 vote · 0 comments
No comments yet.