Google AlloyDB for PostgreSQL is wire-compatible with PostgreSQL and connects through the same JDBC PostgreSQL plugin — there is no separate AlloyDB connector to configure.
On this page
How It Connects
AlloyDB (connector type GCP_ALLOYDB) delegates entirely to the JDBC PostgreSQL plugin. Use the same connection fields, authentication methods, SSL modes, and write behaviour documented on the PostgreSQL page.
Networking Requirement
alloydb_host must be a private IP, reachable only from inside the AlloyDB cluster's VPC — for example, a Dataproc Serverless batch running on the same network. A plain TCP connection attempt from the DataKnits backend host itself will correctly fail unless the backend is deployed inside that VPC.
Known Limitations
- There is no dedicated AlloyDB connector plugin — anything not supported by the PostgreSQL plugin (see PostgreSQL: Known Limitations) is also not supported for AlloyDB.
- Because
alloydb_hostmust resolve on a private VPC network, connecting from a DataKnits backend hosted outside that network requires routing through a Dataproc Serverless batch (viagcp_subnetwork/ Private Google Access) or an equivalent network bridge — it is not solvable from connection configuration alone.