Download Aurora PostgreSQL JDBC Driver

Download the Aurora PostgreSQL JDBC driver, copy the JDBC URL into DbSchema, and start designing schemas with ER diagrams — free Community Edition.

About the Aurora PostgreSQL JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to Aurora PostgreSQL. DbSchema uses JDBC to reverse engineer schemas, run SQL, and generate documentation. Driver files are usually published by the database vendor or an open-source project.

JDBC URL format

Host, port, database name, and SSL options are passed in a URL starting with jdbc:. Each Aurora PostgreSQL driver uses its own syntax — see the connection details below.

The Aurora PostgreSQL JDBC driver

Amazon Aurora PostgreSQL is AWS's PostgreSQL-compatible relational database engine, offering up to 3× the throughput of standard PostgreSQL. It supports automatic scaling, global databases, and Babelfish for SQL Server compatibility — ideal for cloud-native workloads migrating from on-prem PostgreSQL.

The Aurora PostgreSQL JDBC URL

• Required File(s): postgresql-nn.jdbc3.jar
• Java Driver Class: org.postgresql.Driver
• JDBC URL: jdbc:postgresql://HOST[:PORT]/DB
• Website: PostgreSQL

If you want to connect to Heroku Postgresql web-based database, please edit the JDBC driver URL ( in Driver Manager dialog ) and append ?ssl=true&sslfactory=org.postgresql.ssl.NonValidatingFactory in the end.

Download Aurora PostgreSQL JDBC Driver

The driver archive is a zip file. Extract it and load the .jar files using DbSchema's Driver Manager.

Connecting to an Aurora PostgreSQL Cluster

An Aurora cluster lives inside a VPC. Two settings decide whether a machine outside AWS can reach it, and both are on the AWS side — there is no postgresql.conf to edit.

1. Allow your address in the security group. Add an inbound rule for TCP 5432 whose source is your IP or CIDR block. The cluster's security group is on the Connectivity & security tab in the RDS console.
2. Turn on public accessibility. Without it the cluster resolves to a private address that means nothing outside the VPC. It also requires a public subnet with a route to an internet gateway. Where policy forbids exposing the cluster, tunnel through a bastion host in the VPC instead.
3. Take the right endpoint. The Connectivity & security tab lists several. The cluster (writer) endpoint follows failover and is the one to use for schema work; the reader endpoint load-balances read-only queries and will refuse any change you generate.
4. Open port 5432 in the server's firewall. The database listens on port 5432 unless it was installed with a different one. A host firewall on the server blocks incoming connections on that port until a rule allows them. The firewall guide has the commands for Windows, ufw, firewalld and iptables.
5. Connect from DbSchema. In the Connection Dialog choose Remote computer or custom port, fill in the server host and the port, then press Test Connection to check that the server answers before you connect.

DbSchema also ships an AWS Advanced JDBC Wrapper entry in the Connection Mode combo. It uses Aurora's own topology to follow a failover faster than a DNS change would.

• Or reach the server through SSH. When the database port is deliberately closed to the internet, press Setup SSH Tunnel... in the Connection Dialog and connect through a host that is exposed. The database host and port are then the ones seen from the SSH host — often localhost. See the SSH tunnel guide.

DbSchema and Aurora PostgreSQL

Aurora PostgreSQL uses the standard PostgreSQL wire protocol, so DbSchema connects using the PostgreSQL JDBC driver. Use DbSchema's Schema Documentation feature to generate navigable HTML docs for your Aurora PostgreSQL schemas across multiple schemas and databases.