MySQL DAM and ProxySQL

Andrew Stolarz stolarz at
Tue Sep 29 10:01:47 EDT 2020


I used to have a few AWS RDS>MySQL in the past and had no issues connecting
from Omnis (was using Studio 6 and 8).

I'm not familiar with Sequel Pro (only been using MySQL Workbench), but if
you connected using SSH, it would be different ports VS. what Omnis
default would be using (and mysql default), which is port 3306. Try
using Sequel Pro with port 3306 to make the connection and not SSH. (and
make sure that port is open on the firewall / VPC). I believe you are
behind the AWS VPC with the RDS databases.

You need to VPN into your VPC if you want to use the local IP address of
the MySQL database (secure).

You can also use the public address/domain for the MySQL database they
provide once you open the MySQL port (insecure).


On Tue, Sep 29, 2020 at 6:21 AM Reg Paling <Reg_Paling at> wrote:

> Hi all,
> I have to connect to a MySQL database on AWS which uses a bastion
> server, presumably running ProxySQL.  I have credentials and keys for
> the SSH tunnel and database access.  I can connect from Sequel Pro just
> by filling in the connection details using the SSH option, but haven't
> had success from Omnis.  The issue seems to be that the host address is
> relative to the bastion server* and I can't see that I have any way of
> telling the MySQL DAM that the host is relative to the bastion server.
> *The hostname is for a machine on AWS, and it resolves to a 10.x.x.x
> address, so it has to be relative to the bastion and can only be
> accessed from the bastion which is on the same local network.
> Is there a trick, for getting the MySQL DAM to work with this setup?
> Thanks,
> Reg
> _____________________________________________________________
> Manage your list subscriptions at
> Start a new message -> mailto:omnisdev-en at

More information about the omnisdev-en mailing list