Start of Main Content

If you’re an Acquia customer or agency running projects on Acquia, you may have noticed that it has upgraded Acquia Cloud environments to Acquia Cloud Next over the last year. Acquia Cloud Next is an enterprise-grade, Kubernetes-native Drupal hosting platform built on Amazon Web Services (AWS) that integrates AWS services such as Amazon’s Elastic Kubernetes Service (EKS), Elastic File Service (EFS), and AWS Aurora Database Services.

The switchover is pretty seamless, and you might not see a change in your day-to-day workflow or performance from your Acquia Cloud Next instance. However one change you may spot is that you can no longer connect to Acquia Cloud databases with JDBC driver–based database tools like MySQL Workbench, DBeaver, JetBrains DataGrip, or JetBrains IDE. 

Looking to make the most of Acquia’s features? Learn about our Acquia experience.

As a Gold Partner, and Acquia Certified Drupal Cloud Practice we’re excited to show you how Acquia can help you deliver great Drupal experiences to your audiences.

The Acquia Cloud Next documentation notes that you can no longer connect with these tools and suggests that you use Sequel Pro instead. The Sequel Pro application is only available for MacOS and is a much less robust tool for developer needs. Sequel Pro does not use JDBC at all to make connections which is why it’s unaffected by the database changes to Acquia Cloud Next. Since we have a mix of developers on Windows, Mac, and Linux, using Sequel Pro is not a full solution for us at Velir. So, it was critical for us to find one.

We do a lot of custom Drupal development, integrations, and Drupal migrations. And occasionally we may need to connect to a database in any of the server environments for analysis, debugging, or to perform maintenance you can only do from a SQL client. Having direct access is critical for that reason, so we were shocked that we could lose a valuable development and debugging method with Acquia’s recent changes. Fortunately, we discovered that you can connect with these tools. Here’s how!

The reason you can’t connect to Acquia Cloud Next instances like before is due to compatibility issues of default JDBC driver settings of MariaDB/MySQL that don’t work for AWS Aurora (what Acquia databases changed to). You can still make connections the way you could before using the credentials supplied on your Acquia Cloud database management page, but you must change two settings in the driver you’re using to make those connections.

The list of possible parameters available and their descriptions are listed here. It’s a long and technical list but there are two settings that aren’t compatible with AWS Aurora: useBatchMultisend and usePipelineAuth. When making a connection, you can see in the driver settings that their default value is “true”. That’s why the connections fail. They must be set to “false”, which is easy to change.

The “Data Sources and Drivers” window when you’re making a connection in Acquia Cloud Next. There is an error stating a connection failed when running a test connection to Amazon Aurora MySQL 2.10.2. It says “[08000][-1] Could not connect to address=(host=localhost)(port=53764)(type=master) : (conn=37377080) could not load system variables [08000][1220] (conn=37377080) Connection is closed.” Under the “Advanced” tab you can see that the “useBatchMultiSend” field is highlighted and doesn’t have a value.

Before you make any adjustment to your connection settings you can see that the connection fails (pictured: JetBrains PHPStorm). By clicking into each setting in the “Advanced” tab you can set useBatchMultisend and usePipelineAuth to “false” and retry your connection. This time, you can see that your connection is successful:

The “Data Sources and Drivers” window when you’re making a connection in Acquia Cloud Next. There is a message stating that a test connection Amazon Aurora MySQL 2.10.2. succeeded. It says “DBMS: MySQL (ver. 5.7.12-log) Case sensitivity: plain=extract, delimited=exact Driver: MariaDB Connector/J (ver. 2.7.3, JDBC4.2) Effective version: Amazon Aurora MySQL (ver. 2.10.2) Ping: 41 ms SSL: no”.  Under the “Advanced” tab you can see that the “useBatchMultiSend” and “usePipelineAuth” fields are highlighted and their value is set to “false”.

Now that your connection is successful, you have access to the database again in Acquia Cloud Next and can keep rolling right along querying data and inspecting tables:

A screenshot which shows a series of database tables you can query in Acquia Cloud Next.

That’s it! Now you can continue to use the database tool(s) that you love. This works for any tool using JDBC drivers and the change is universal. Here is the same solution working in DBeaver:

A screenshot from DBeaver that shows the option to test a connection, where the Server field is set to “MySQL 5.7.12-log” and the Driver field is set to “MariaDB Connector/J 2.7.1” and the rest of the window is grayed out, but you can see that the “Driver Properties” tab behind the connection test has the fields “useBatchMultiSend” and “usePipelineAuth” set to “false”.

These database tools that you can use in Drupal development are compatible with Windows, MacOS, and various Linux distributions. We highly recommend them for your teams:

Need help making the most of Acquia’s robust features for your Drupal website? Reach out to us.


Latest Ideas

Take advantage of our expertise with your next project.