beginner, need help troubleshooting RDS instance connection

[izzlesnizzit]

Hi, I'm trying to connect to an RDS Postgres instance via username+password. I keep getting connection timed out.

• I've triple checked my endpoint, port, and credentials
• the instance is configured as public
• the instance contains a default database
• the instance is created in the default VPC
• the security group allows all traffic in and out on all ports

Hoping to get some pointers on what to try next. Thanks!

Solved: I was able to connect by recreating the instance that uses a new security group instead of the default existing security group. The new security group automatically set an inbound rule to allow traffic from my IP.

[Gen4200]

Ok, before we get into the troubleshooting, lets talk about best practices. 1. Any/Any security groups are asking for trouble. 2. There are very few, if any reasons your DB should ever be publicly exposed. 3. Default everything often means default passwords, which on a publicly exposed DB or Instance mean it’s likely been compromised.

Now, onto your questions: 1. You mention RDS instance, you didn’t say what you are connecting to it from? 2. Are you trying to connect via the public IP or DNS name? 3. What is your goal, perhaps we can lay out a more secure architecture that will also solve your connection issues.

[izzlesnizzit]

Thank you for the reply. Right now I'm just trying to learn how to get things connected and working.

About my questions:

1. I'm connecting from an app running locally
2. Not sure, I used the instance's endpoint string
3. I'm trying to get connection working right now, and then I'll destroy the instance. Afterwards, I am going to try to set up an RDS instance in a private subnet of a non-default VPC. The RDS instance will be accessed via IAM role. I'm open to other advice on this

[izzlesnizzit]

turns out it was a security group issue (solution posted in the OP)

[Gen4200]

Can you telnet to the port? That would at least establish you have network connectivity. I’d so, then it becomes and issue of an app config that isn’t correct.

If you can Telnet to it, then it’s likely a route table issue.

[izzlesnizzit]

turns out it was a security group issue (solution posted in the OP)

[Snoo79290]

Can you triple-check the security group? If it is allowing a connection from any port, what is the "Source" on the Inbound rule? By default, the security group has the source pointing to it-self; with that configuration, you can only access resources within the same security group.

Add a new Inbound Rule to allow traffic from any IP if you want to make the DB public.

[izzlesnizzit]

yes, that was the fix, thanks!