30

Short description: AWS RDS connecting server to PgAdmin 4, PostgreSQL 11

Done: I have done similar to this guy or to this aws guide but at the end when I click save it does not accept it for me. instead gives the following

ERROR: 

Error saving properties 
Unable to connect to server: 
timeout expired

What I have tried to solve the problem:

  • The instance is active it is 2 hours after creation
  • I have also allowed to access database with outside of AWS database client "YES"
  • this stack overflow answer does not deliver results https://stackoverflow.com/a/37903485/10270590 actually after refreshing my security group like the guide says my whole database disappeared
  • I have home wi-fi so there are no corporate firewalls or any of those issues https://serverfault.com/q/705312/535406
  • while reading the pervious server fault post I looked up my
    • RDS/Databases: what was empty
    • RDS/Security groups: empty and I have this message:
Your account does not support the EC2-Classic Platform in this region. 
DB Security Groups are only needed when the EC2-Classic Platform is supported. 
Instead, use VPC Security Groups to control access to your DB Instances.
sogu
  • 2,738
  • 5
  • 31
  • 90

1 Answers1

79

Edit inbound rules Type have to be turned to: all traffic and my IP. than it works

enter image description here

sogu
  • 2,738
  • 5
  • 31
  • 90
  • 5
    You have not mentioned in AWS management console, how one can arrive at the above location. – Asif Sep 16 '20 at 01:00
  • 9
    AWS => Services => RDS => Databases => Choose your db. In the "Security group role" section, choose the rule and edit as mentioned above. – Beu Sep 17 '20 at 13:45
  • 1
    It is important to note that a Serverless instance cannot be assigned a public IP, and so you cannot connect one outside of a VPC, as described here https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless.html#aurora-serverless.requirements. – nikojpapa Feb 08 '21 at 19:11
  • 3
    is it safe to allow all traffic? – alexrogo Mar 03 '21 at 13:30
  • 4
    I've the same issue. Tried the above solution but didn't work for me. – Firdous bhat Oct 03 '21 at 05:03
  • 1
    one reason could be that when creating the db you should NOT select the default security group but choose the create new sg option. This worked fine for me, – Jawad May 28 '22 at 16:48