Question 1

Does TextQL support both Aurora MySQL and Aurora PostgreSQL?

Accepted Answer

Yes. TextQL auto-detects your Aurora engine type during connection setup and generates the appropriate SQL dialect. You can connect Aurora MySQL and Aurora PostgreSQL instances simultaneously and even ask questions that join data across both engines using TextQL's multi-source query capability.

Question 2

Should I connect TextQL to the writer or reader endpoint?

Accepted Answer

We recommend connecting to the Aurora reader endpoint. This routes TextQL's analytics queries to your read replicas, keeping your writer instance free for application workloads. TextQL only executes SELECT queries, so a reader endpoint provides full functionality with zero impact on production writes.

Question 3

Does TextQL support Aurora Serverless v2?

Accepted Answer

Yes. TextQL connects to Aurora Serverless v2 using the same cluster endpoint and credentials as provisioned Aurora. Serverless v2's automatic scaling works transparently — TextQL adapts to whatever compute capacity your cluster scales to without any configuration changes.

Question 4

Can TextQL connect through a VPC?

Accepted Answer

Yes. TextQL supports private connectivity to Aurora clusters within a VPC. You can use VPC peering, AWS PrivateLink, or an SSH bastion host to establish the connection. This ensures your database endpoint is never exposed to the public internet.

Question 5

How does TextQL handle Aurora's read replica lag?

Accepted Answer

Aurora typically maintains sub-millisecond replica lag, so results from the reader endpoint are near-real-time. TextQL does not add additional caching. If your use case requires absolute consistency, you can connect to the writer endpoint instead — though we recommend reader endpoints for most analytics workloads.