Which destination?:

CloudSQL PostgreSQL destinations

Additional details:

Description of the Problem: Currently, Fivetran allows users to upload a Client Certificate and Client Private Key when configuring PostgreSQL as a Source. However, these exact same configuration fields are missing when configuring PostgreSQL as a Destination.

When attempting a Direct Connection to a Google Cloud SQL PostgreSQL destination configured with "Require trusted client certificates" (mTLS), the connection instantly fails with: Unable to validate certificate. FATAL: connection requires a valid client certificate

Business Impact & Why Workarounds are Unacceptable: Because Fivetran lacks parity between its Source and Destination configurations, we are forced to choose between two unacceptable options:

1. Degrade Cloud Security: Disable the "Require trusted client certificates" setting on our Cloud SQL instance, violating our internal security and compliance postures.

2. Build Custom Infrastructure: Spin up and maintain compute instances to run the Cloud SQL Auth Proxy over an SSH tunnel. This completely defeats the value proposition of paying for a fully managed, zero-maintenance SaaS pipeline.

Proposed Solution: Achieve feature parity by adding the "Client Certificate" and "Client Private Key" upload fields to the PostgreSQL Destination setup UI, allowing Fivetran to successfully authenticate via mTLS just as it already does for PostgreSQL Sources.