- 최신
- 최다 투표
- 가장 많은 댓글
The fact that you’re trying a 172.x address raises the question is your RDS really publicly accessing?
A 172.16.0.0/12 network range is an RFC1918 address space. I’m going to assume the IP address returned via a dns lookup is a 172.31.x.x which is the default VPC CiDR range. You will never be able to connect to this address over the public internet.
Connecting via dns name or its ip will always result in the same issue.
A few things you need to check.
- The Rds instance is in a public subnet.
- the RDS instance does have Public accessible set
- The public subnet default routes to an IgW
- The security group on the RDS allows your PUBLIC ip and not the private IP of your home machine.
- NACLs allow connectivity to and from the postgress port and ip address
Thank you. Could you please look at my rules, what is wrong there: GroupId,GroupName,Type,IpProtocol,FromPort,ToPort,IpRanges,Ipv6Ranges,PrefixListIds,UserIdGroupPairs sg-06517,default,Inbound/Ingress,'-1,,,0.0.0.0/0,,, sg-06517,default,Inbound/Ingress,'-1,,,,::/0,, sg-06517,default,Inbound/Ingress,'-1,,,,,,sg-06517 sg-065*17,default,Outbound/Egress,'-1,,,0.0.0.0/0,,,
Rules look fine. Does the dns name return a 172.31 ip address?
nslookup 12121212.eu-west-2.rds.amazonaws.com DNS request timed out. timeout was 2 seconds. Server: UnKnown Address: fe80::b669:.... DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. *** Request to UnKnown timed-out
Looks like now you have dns resolution issues with dns timeouts.
Hi, it's probably a routing issue: If you connect via the dns name, try to run nslookup (windows) to get the ip address and then try to connect via this ip instead of dns.
Another way to check the root of your problem it to telnet to the dns name / ip + port to see if you get the tcp session properly established. For that, see https://netbeez.net/blog/telnet-to-test-connectivity-to-tcp/
Telnet: Connecting To ***.eu-west-2.rds.amazonaws.com...Could not open connection to the host, on port 5432: Connect failed
Also, Microsoft Telnet> open 172...** 5432 Connecting To 172...** ...Could not open connection to the host, on port 5432: Connect failed
관련 콘텐츠
AWS 공식업데이트됨 2년 전
Please provide more information to how your trying to connect to the Rds instance and what your network connectivity looks like
Please see above I have edited my question. Also, I use pgAdmin on my computer, it shows me an INTERNAL SERVER ERROR: unable to connect etc