Can iDBQuery connect to a database using IAM or cloud authentication?

Cloud databases often support authentication beyond a static password — IAM database authentication, managed identities, or short-lived tokens. iDBQuery connects using the credentials and connection method your database is configured to accept, and any secrets you give it are stored encrypted.

The recommended, most secure setup:

• Deploy iDBQuery in your own VPC so it authenticates to the database from inside your network, using the same private path your other services use.
• Use a dedicated, read-only account — whether that's an IAM-mapped database role or a scoped database user — so iDBQuery can query but never write or delete.
• Keep secrets in your environment — credentials are encrypted, and with on-prem or air-gapped deployment they never leave your walls at all.

This architecture-first approach is how iDBQuery handles sensitive data generally: least-privilege access, encryption in transit and at rest, and query-in-place so your data isn't force-copied out.

Example: a team on AWS grants a read-only IAM-mapped role on their RDS instance, runs iDBQuery inside the same VPC, and business users start asking cited questions immediately — with database access governed by their existing IAM policies rather than a new set of shared passwords. If your provider issues rotating credentials, you supply the connection details iDBQuery needs and it authenticates accordingly.