Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Dear Community!
We’re connecting to a Managed PostgreSQL database through a PgBouncer connection pool in App Platform. For most connection parameters we use the pool-scoped variable syntax:
${<db-name>.<pool-name>.HOSTNAME}
${<db-name>.<pool-name>.PORT}
${<db-name>.<pool-name>.USERNAME}
...
However, we also need to pass the CA certificate to verify TLS connections (rejectUnauthorized: true). The documentation lists CA_CERT as a bindable variable, but only shows it in the context of direct cluster references:
${<db-name>.CA_CERT}
The pool variable section only shows DATABASE_URL as an example, and CA_CERT is never mentioned there.
Our question: Does the pool-scoped syntax support CA_CERT? In other words, is ${<db-name>.<pool-name>.CA_CERT} a valid reference, or should we always use the cluster-level ${<db-name>.CA_CERT} for the certificate — even when connecting through a pool?
If CA_CERT is not available via the pool syntax, is the cluster-level reference still the right cert to use when the actual connection goes through PgBouncer?
Thanks for the answers in advance! Keep on Coding! Gulyas Bendeguz
4ae272398ee6445a9bf73f4cd632b5
eddie
Taha Aziz Ben Ali
Telmo Valverde
Alexandre Herlinvaux
52d4eff26a544eefb189e2005836b2
EatingAquamarineScubaDiver
f25932a0b984430fb48c4256f1aaad
JuanPablo
fullammo
aq
a67ecb62f684403a9548d56545d826