Issue
In AWS I have a VPC set up with a Bastion Host. The bastion host is a single EC2 instance with a public address trough which you can SSH to any other server on the VPC.
I have created an RDS MySQL instance within the VPC and I would like to connect to it using MySQL workbench. I have followed the steps detailed here, however in "Step 6: Setting up remote SSH Configuration", it asks me to "Provide the Public DNS of the Amazon EC2 instance" (i.e. the bastion host).
MySQL workbench then does checks for certain MySQL resources on that server. However, this is not correct in my opinion as I have provided the bastion host's address, which does not have MySQL installed. As a result, the last two checks for "Check location of start/stop commands" and "Check MySQL configuration file" then fail.
I have then tried using the endpoint address of the RDS MySQL instance but with no success (as it is in the private subnet so is not publicly addressable).
It seems that many people have this up and running, but what am I doing wrong here?
Solution
I've been struggling with something similar for weeks now. Just figured it out a few minutes ago.
- In mysql workbench, create a new server instance.
- For the remote host address, enter your endpoint address (i.e. xxxxxx.us-east-1.rds.amazonaws.com)
- For connection method, select "Standard TCP/IP over SSH"
- The SSH Hostname is the public DNS of your EC2 instance
- I specified ec2-user (I believe it varies by EC2 Instance type) as the username and then specified the downloaded key file corresponding to the key pair the instance was using.
- The mysql hostname is the endpoint of the RDS instance.
- The username is the username for the RDS instance (i.e. ebroot)
Using that I was able to connect. However, I did not utilize VPC in my setup. Hope this helps. Good luck!
Answered By - AndrewSmiley Answer Checked By - Dawn Plyler (WPSolving Volunteer)