Closed Gyde04 closed 3 years ago
same for me while using with amazon aws
Hey, I was also having this same issue when I tried to connect with aws rds, but the actual problem was in the inbound rules defined for the database instance. I changed my inbound rules and I got connected to the aws rds through sqlelectron.
P.S: If you cannot connect using sqlelectron, then try connecting using terminal, in my case there also I got an error that leads me to the StackOverflow and eventually to my inbound rules set for the database instance created in aws rds.
Hey, I was also having this same issue when I tried to connect with aws rds, but the actual problem was in the inbound rules defined for the database instance. I changed my inbound rules and I got connected to the aws rds through sqlelectron.
P.S: If you cannot connect using sqlelectron, then try connecting using terminal, in my case there also I got an error that leads me to the StackOverflow and eventually to my inbound rules set for the database instance created in aws rds.
Thank you Aryaman. You helped me really much!
rightly said by aryaman, if you have used default VPC do allow traffic from internet or allow all traffic from security group in aws
Hi, if you are using custom VPC. then make sure that in the route table all internet traffic is going to Internet gateway. so edit inbound rules and change the route table.
In your RDS -> Select your database and check if its publicity accessible.
But if I want restrict to certain IP addresses that can access my RDS? Publicly accessible is not the best option , right?
Tried to test mySQL connections and it gives me this error message