Re:I discovered thousands of open databases on AWS
by noduerme on Tuesday February 01, 2022 @11:40PM
(#30173779)
This wouldn't be efficient in my case. I'm testing a frontend that's served on localhost:80 and connects to a local backend also on localhost:80 that makes DB calls to some remote database on 3306. I'd have to modify the backend code to connect through the proxy port every time I wanted to test it. As it is the backend code on my computer is a mirror of the production environment. Normally if I tunnel I have it set up to forward everything through the tunnel except localhost.
Re:I discovered thousands of open databases on AWS
by nkozyra on Tuesday February 08, 2022 @12:07PM
(#30261049)
In this case you'd simply do the tunnel for 3306:3306.
Your frontend and backend code would run locally and connect to MySQL through the proxy. You wouldn't have to change any backend configuration.
But if your ec2 service has security group access to multiple things it's extremely useful because you can hit localhost:xxxx for postgres, localhost:yyyy for elasticsearch, etc.