Need to support more advanced SSL parameters for connecting to remote hosts (ie. AWS)

I cannot get a connection to a remote AWS (Aurora RDS) Postgres DB.
The instance is configured with encryption, so it requires some SSL parameter massaging.

Locally I am able to connect to it and at least download the data (using ie. pg_dump) if I set these ENV variables before calling it:
PGSSLMODE=require PGSSLCERTMODE=disable PGCONNECT_TIMEOUT=10

Similarly, when running node code (using typeorm package, DataSourceOptions object), I have to set this parameter:
ssl: { rejectUnauthorized: false }

Can't seem to get a connection otherwise using this extension.
I tried setting the ssl parameter in the vscode-pgsql config to these other values, to no avail:
true, false, "require", "prefer", "allow", "disable", { rejectUnauthorized: false }, etc...

It tends to throw the error:
"no pg_hba.conf entry for host "<my-ip-address>", user "postgres", database "mydb", no encryption"
It does list the servers on the left vscode-pgsql panel, but won't list their contents (throws the error).

Maybe exposing the underlying PG* env vars would help in scenarios like this.

Start by tracing how the vscode-pgsql configuration's ssl option is passed to the PostgreSQL connection, then compare it with the PGSSLMODE, PGSSLCERTMODE, and PGCONNECT_TIMEOUT settings described in the issue. Reproduce the failure against an encrypted Aurora RDS connection if available. Done means supported SSL settings allow the remote server's contents to load instead of producing the no-encryption error.