Download Aurora MySql JDBC Driver

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

About the Aurora MySql JDBC driver

A JDBC driver is a Java .jar library that lets applications connect to Aurora MySql. 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 MySql driver uses its own syntax — see the connection details below.

The Aurora MySql JDBC driver

Amazon Aurora MySQL is AWS's MySQL-compatible relational database engine rebuilt for the cloud, offering up to 5× the throughput of standard MySQL with automated storage scaling, multi-AZ failover, and read replica support. It is fully compatible with MySQL 5.7 and 8.0 applications.

The Aurora MySQL JDBC URL

• Required File(s): mysql-connector-java-nn-bin.jar
• Java Driver Class: com.mysql.jdbc.Driver
• JDBC URL: jdbc:mysql://HOST[:PORT][/DB]
• Website: MySQL

Download Aurora MySQL JDBC Driver

The driver archive is a zip file. Extract it and load the .jar files using DbSchema's Driver Manager. The Aurora driver is also available at https://github.com/threadly/auroraArc.

Connecting to an Aurora MySQL Cluster

An Aurora cluster sits inside a VPC, so the settings that matter are on the AWS side. There is no my.cnf to edit — parameter groups replace it, and none of them control reachability.

1. Allow your address in the security group. Add an inbound rule for TCP 3306 with your IP or CIDR block as the source. The cluster's security group is listed on the Connectivity & security tab in the RDS console.
2. Turn on public accessibility. Without it the endpoint resolves to a private address that is meaningless outside the VPC, and it also needs a public subnet routed to an internet gateway. Where exposing the cluster is not allowed, tunnel through a bastion host instead.
3. Take the right endpoint. The cluster (writer) endpoint follows failover and is the one for schema work. The reader endpoint spreads read-only queries over the replicas and rejects any change you generate.
4. Grant the user access from your host. Aurora keeps MySQL's user-plus-host accounts, so the account must permit the address you connect from — often '%' on a cluster reached from outside AWS.
5. Open port 3306 in the server's firewall. The database listens on port 3306 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.
6. 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 offers an AWS Advanced JDBC Wrapper entry in the Connection Mode combo, which reads Aurora's topology and follows a failover without waiting for DNS to catch up.

• 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 MySQL

Aurora MySQL uses the same wire protocol as MySQL, so DbSchema connects using the standard MySQL Connector/J. Use DbSchema's ER diagrams to visualize Aurora schemas and the Schema Synchronization feature to compare schemas between Aurora clusters.