Connecting to your Cluster

To provision a new cluster in Crunchy Bridge, see the Provision an instance section of the Getting Started guide.

Connecting to an instance

Once you’ve created a cluster, you’ll see it listed in the Team Dashboard. Click on the name to view the Cluster page.

In the Cluster page, you can find the Postgres instance credentials on the Connection tab. Select the role and format that work best for you, then you can copy the connection string.

SSL is required

SSL is required to connect to a Crunchy Bridge cluster regardless of firewall settings. This is not currently configurable.

Note that only TLS v1.2 and v1.3 are supported, meaning older clients may not be able to connect despite enabling SSL.

Certificates

For an added layer of security, admins can retrieve a self-signed root certificate, which is available per Team through the Dashboard on the Team Settings page or via the API.

Troubleshooting connection encryption

When connecting clients and applications to your cluster we recommend using SSLMODE=require. Some clients will default to SSLMODE=prefer, which allows the client to fall back an unencrypted connection if SSL connection fails. This will cause errors referring to no encryption since Crunchy Bridge clusters do not allow unencrypted connections.

Node.js

node-postgres requires some configuration in order to get TLS/SSL connections working. You can review the full documentation for connecting either with a cert or a connection string at node-postgres.com.

The connector should be configured with a block similar to the one below:

const sql = postgres(process.env.DATABASE_URL, {
  ssl: {
    require: true,
    rejectUnauthorized: false
  }
})

Connection Pooling

PgBouncer is included for connection pooling, however it must be enabled before it can be used. Check out the PgBouncer how-to guide for details on setting it up and getting connected.