AWS EC2 Correct Inbound/Outbound Rules For Database

[scott]

I had to delete my existing EC2 instance and start over because I was having issues with Traefik.

I remember having a lot of trouble getting Wappler Database Manager and MySQL Workbench to connect to the EC2 instance the last time and forgot to look at the inbound/outbound rules on the AWS website before removing the instance.

Would anyone be able to provide me with guidance on what the proper rules should be to allow both Wappler’s Database Manager and MySQL Workbench to connect?

Server: Nodejs
Database: MySQL
Elastic IP: In Use
MySQL Port: 9906

I created a new security group, associated it with the EC2 instance and currently have an inbound rule set for Custom TCP > 9906 > Custom IP > My IP.

Not sure what else is needed. @Teodor what are your thoughts?

[Apple]

The safest way is to use SSH tunneling

[scott]

Hi @Apple,

I am attempting to do that now without success.

I created a new Key Pair:

Details from the EC2 Instance:

MySQL Workbench:

I then tried the Public IPv4 DNS instead of the Public IPv4 address and got the same error.

I then tried both the Public IPv4 DNS and the Public IPv4 address with the private key listed in Wappler and received the same error.

Having tried all those combinations, I am at a loss…

[scott]

As a side note, the settings created by Wappler when the EC2 instance was created from the Docker Remote > Manage are not connecting to the database.

The EC2 instance is up and running without errors.

[Apple]

@scott

I created a new Key Pair

Please verify if the new key pair is present inside your server at location ~/.ssh/authorized_keys

Sometimes such key pairs are only used for new deployments, not applied on existing servers

[scott]

In the AWS EC2 website, I found this under Network & Security > Key Pairs:

I found this under the EC2 Instance >

I found the Wappler Public and Private key pair on my local machine in ~/.docker/machine/machines/EC2.

I could not find a .ssh folder locally in the ~/.docker folder or any of the subfolders. If I am understanding correctly, I need to create a .ssh folder on the machine, however, I am not certain about that since the key pairs are listed on the AWS website. My question is if I need to create it, where do I create it? Since Wappler created a public and private key pair, I feel I should use that.

I am not familiar with using Terminal and in the past, I mostly have used php on shared servers and have not had to do things like this.

When I look at https://codingfundas.com/ssh-to-aws-servers-using-an-ssh-config-file/index.html, it talks about a .pem file. When I look inside ~/.docker/machine/machines/EC2, I see multiple .pem files:

[Apple]

Make Wappler-Workbench key pair assigned at launch using AWS control panel. And then reboot the server

I’m not familiar with AWS, my assistance may be limited