Amazon Aurora PostgreSQL-Compatible Edition is AWS’s high-performance managed Postgres. QueryBear connects over the standard Postgres protocol, giving your AI clients safe, read-only access through QueryBear’s security gateway.Documentation Index
Fetch the complete documentation index at: https://docs.querybear.com/llms.txt
Use this file to discover all available pages before exploring further.
Using Aurora MySQL-Compatible Edition instead? See Aurora MySQL.
Get your Aurora connection details
Aurora clusters expose two endpoints:- Writer (cluster) endpoint — routes to the primary instance.
- Reader endpoint — load-balances across replicas. Use this for QueryBear so AI query load stays off your writer.
Allow QueryBear’s IP
- Get QueryBear’s egress IP from the dashboard under Connections → Network.
- Add an inbound rule to the cluster’s security group for that IP on port
5432. - Ensure the cluster is publicly accessible or reachable via VPC peering / PrivateLink.
Create a read-only role
Use the PostgreSQL read-only role SQL. Run it against the writer endpoint (writes are needed to create the role), then connect QueryBear to the reader endpoint.Add the connection to QueryBear
In the QueryBear dashboard → Connections → New connection → PostgreSQL. Use the reader endpoint, port5432, your querybear role, and SSL mode require.
Aurora-specific notes
- Reader endpoint for reads: Always prefer it for QueryBear — it’s purpose-built for read scaling.
- TLS: Aurora supports the Amazon RDS CA bundle; QueryBear connects over TLS.
- Auto-scaling replicas: The reader endpoint handles new replicas transparently.