Supported Databases
| Database | Status | Default Port |
|---|---|---|
| ClickHouse | Available | 8443 |
| PostgreSQL | Available | 5432 |
| Snowflake | Available | Account-based |
| Amazon Redshift | Available | 5439 |
| Google BigQuery | Available | Account-based |
Creating a Connection
Navigate to Connections
Open the sidebar and click Connections under the Data section. Click the New Connection button.
Select the database type
Choose your database type from the dropdown: PostgreSQL, ClickHouse, Snowflake, Redshift, or BigQuery.
Enter connection details
Fill in the connection form:
| Field | Description |
|---|---|
| Name | A friendly label for this connection (e.g., “Production ClickHouse”) |
| Host | Database hostname or IP address |
| Port | Database port (pre-filled with the default for your selected type) |
| Database | Name of the database to connect to |
| Username | A database user with read access |
| Password | The password for the database user |
| Secure (SSL/TLS) | Toggle to enable encrypted connections to your database |
Test the connection
Click Test Connection to verify that Vigilos can reach your database. See the next section for status indicators.
Testing Connections
The Test Connection button sends a lightweight query to your database to verify connectivity and authentication. After testing, the connection shows one of the following status indicators:| Status | Meaning |
|---|---|
| Active | Connection is working and ready to use |
| Testing | A connection test is currently in progress |
| Error | The test failed - check your hostname, port, credentials, and network access |
| Inactive | Connection has been disabled or has not been tested yet |
Security
Vigilos takes connection security seriously:- AES-256 encryption - credentials are encrypted immediately upon submission, before they are stored. No plaintext credentials exist in the database at any point.
- Encrypted at rest - the encrypted credentials are stored with disk-level encryption.
- No credential exposure - connection passwords are never returned in API responses or displayed in the UI after creation. You can update them but never view them.
Even Vigilos platform administrators cannot view your plaintext database credentials. The encryption keys are managed separately from the application database.
Network Requirements
Your database must be reachable from Vigilos’s infrastructure for queries to execute. Depending on your setup:Public databases
Public databases
If your database has a public hostname or IP address, no additional configuration is needed. Ensure that your firewall allows inbound connections on the database port from Vigilos’s IP range.
Private networks
Private networks
For databases behind a VPN or private network, you may need to set up a secure tunnel or allowlist Vigilos’s IP addresses. Contact support for the current IP range.
SSL/TLS recommendations
SSL/TLS recommendations
We strongly recommend enabling the Secure toggle for all connections. This encrypts data in transit between Vigilos and your database, preventing interception of query data and results.Most cloud-hosted databases (AWS RDS, GCP Cloud SQL, ClickHouse Cloud) support SSL/TLS out of the box.