​

Before you connect

• SELECT on the target database
• SHOW DATABASES to enable database auto-discovery

​

Connection fields

Boolean columns — MySQL’s TINYINT(1) type is interpreted as a boolean by many JDBC drivers. If your queries return true/false instead of 0/1 unexpectedly, add tinyInt1isBit=false to Additional JDBC Parameters.

​

SSH Tunnel fields

​

Finding your connection details

​

Amazon RDS for MySQL

1. Open the RDS Console and select your DB instance.
2. Under Connectivity & security, copy the Endpoint — this is your Host.
3. The default Port is 3306.
4. Ensure the instance’s security group allows inbound TCP on port 3306 from Supaboard’s egress IPs, or route through an SSH tunnel.

​

Amazon Aurora (MySQL-compatible)

1. In the RDS Console, open your Aurora cluster.
2. Use the Writer endpoint as your Host for read/write access; use a Reader endpoint for read-only.
3. Default port is 3306.
4. Add Supaboard IPs to the cluster’s VPC security group.

​

Google Cloud SQL for MySQL

1. Open the Cloud SQL Console and select your instance.
2. Under Connect to this instance, copy the Public IP address as your Host.
3. Under Connections → Authorized networks, add each Supaboard egress IP.
4. Alternatively, use the Cloud SQL Auth Proxy via an SSH tunnel.

​

Azure Database for MySQL

1. Open your server in the Azure Portal.
2. On the Overview page, copy Server name — this is your Host (format: server.mysql.database.azure.com).
3. Under Settings → Connection security, add a firewall rule for each Supaboard egress IP.
4. SSL enforcement is enabled by default on Azure — enable the SSL toggle in Supaboard.

​

SSL

• SSL Certificate — paste the server’s CA certificate in PEM format if your database uses a self-signed or private CA certificate. Leave blank for certificates signed by a public CA.

​

SSH Tunnel

• Your database has no public IP
• You want to avoid adding Supaboard IPs to your database firewall
• Your security policy requires all external connections to go through a jump server

• The bastion server can reach the database host on port 3306
• Supaboard’s egress IPs are allowed on the bastion server’s SSH port (default 22)
• The SSH user has permission to forward connections (no no-port-forwarding in authorized_keys)
• If using a private key, it is in PEM format (OpenSSH format may need conversion with ssh-keygen -p -m PEM)

​

Recommended database user permissions

-- Create a dedicated read-only user (accessible from any host)
CREATE USER 'supaboard'@'%' IDENTIFIED BY 'strong_password_here';

-- Grant SELECT on the target database
GRANT SELECT ON your_database.* TO 'supaboard'@'%';

-- Allow database discovery
GRANT SHOW DATABASES ON *.* TO 'supaboard'@'%';

FLUSH PRIVILEGES;

​

Troubleshooting