Google AlloyDB

Google AlloyDB is its own database type in QueryDesk. It speaks the PostgreSQL protocol, so everything that works on PostgreSQL works on AlloyDB, including data protection, peer reviews and the JSON structure action. QueryDesk is tested against AlloyDB Omni 17.

Connect over a public IP

  1. In the Google Cloud console, open your AlloyDB instance and turn on Public IP.
  2. Under Authorized external networks, add the address QueryDesk connects from. For QueryDesk Cloud that is 35.224.237.12/32. A self-hosted QueryDesk uses its own egress address.
  3. In QueryDesk, go to Databases > New database and set Database type to Google AlloyDB. Enter the instance's public IP as Database IP or hostname, leave Port empty (5432) and enter the Database name.
  4. Add a credential with a database user and password, then click Test Connection.

Turn on Enabled in the Encryption section. To verify the server, paste the instance's CA certificate as the Server CA Certificate. Leave Verify server hostname (verify-full) off: you connect by IP address, and the certificate does not name it.

A postgres:// connection string pasted under Update with connection string keeps the Google AlloyDB type.

Connect over a private IP

A private IP is only reachable from inside your VPC, so QueryDesk reaches it through a Tunnel.

  1. Run a Tunnel on a VM or a GKE cluster in the VPC that can reach the AlloyDB instance.
  2. Create the database in QueryDesk as above, using the instance's private IP as Database IP or hostname.
  3. Choose the Tunnel in the Tunnel field, then click Test Connection.

What works differently

  • AlloyDB's own extensions are skipped. Every AlloyDB database comes with google_ml_integration, google_columnar_engine, google_db_advisor and hypopg. The schema sync skips their tables and views: the ai and google_ml schemas, and the g_columnar_*, google_db_advisor_* and hypopg_* views in public.
  • The model registry is a system table. To let a policy's queries read google_ml or ai, add the schema or a table's name under Allowed system tables. See System Tables.
  • Model calls see redacted values. A model call such as ai.generate(email) is sent the redacted value, not the column's. Calls that run SQL or read a table named in their arguments are refused under a policy, such as ai.hybrid_search, ai.forecast with a source query and google_ml.execute_dynamic_queries_read_only.
  • AI read-only refuses model calls. AlloyDB's read-only transaction doesn't stop a model call or a columnar engine change, so with Read only set, QueryDesk refuses any function in ai or google_ml, embedding(), ml_predict_row() and the google_columnar_engine_* and google_db_advisor_* functions. See AI governance.

AlloyDB Auth Proxy and IAM authentication

QueryDesk connects with a database user and password. The AlloyDB Auth Proxy and IAM database authentication are not supported yet. Both need credentials that come from cloud IAM.

Was this page helpful?