Can I connect a database to iDBQuery over a VPN or private link?

For teams that require databases to stay off the public internet, iDBQuery supports connecting over private networking rather than a public endpoint. The cleanest approach is to run iDBQuery where your data already lives:

• Deploy in your own VPC — iDBQuery sits inside your cloud network and connects to the database over its private IP, using VPC peering or a private link if the database is in another account or region.
• Over a VPN — iDBQuery reaches an on-prem or remote database through your existing site-to-site or client VPN.
• Via a private link / service endpoint — for managed databases, connect over the cloud provider's private connectivity so nothing is publicly exposed.

Because iDBQuery can be deployed in the cloud, in your VPC, on-prem, or fully air-gapped, you choose exactly where it runs and how it reaches your data. Combined with a read-only user and encryption in transit, this keeps analytics access private and least-privilege.

Example: a bank keeps every database inside a private network with no public routes. They deploy iDBQuery in the same VPC, connect over the internal network, and business users get cited answers without a single database being reachable from outside. If your database is only reachable through a jump box, iDBQuery can also tunnel over SSH or a bastion host.