Overview
Connect Plumi to PostgreSQL databases, including:- Self-hosted PostgreSQL
- Amazon RDS for PostgreSQL
- Azure Database for PostgreSQL
- Google Cloud SQL for PostgreSQL
- Supabase
- Neon
Connection Details
| Field | Description | Example |
|---|---|---|
| Host | Database server address | db.example.com |
| Port | PostgreSQL port (default: 5432) | 5432 |
| Database | Database name | myapp_production |
| Username | Database user | plumi_readonly |
| Password | User password | ******** |
| SSL Mode | SSL connection mode | require |
SSL Modes
| Mode | Description |
|---|---|
disable | No SSL (not recommended) |
require | SSL required, no certificate verification |
verify-ca | SSL with CA certificate verification |
verify-full | SSL with full certificate verification |
Setting Up a Read-Only User
Create a dedicated read-only user for Plumi:Cloud Provider Setup
Amazon RDS
- Ensure your RDS instance is publicly accessible or use VPC peering
- Add Plumi’s IP to your security group inbound rules
- Use the RDS endpoint as the host
Azure Database
- Enable “Allow access to Azure services” or add firewall rules
- Use the server name as the host (e.g.,
yourserver.postgres.database.azure.com) - Username format:
username@servername
Google Cloud SQL
- Enable public IP or configure private IP access
- Add Plumi’s IP to authorized networks
- Use the Cloud SQL public IP as the host
Troubleshooting
”No pg_hba.conf entry”
Your database isn’t configured to accept remote connections. Updatepg_hba.conf to allow connections from Plumi’s IP.