AWS RDS Postgresql Pgadmin-服务器不'；我不听

我遵循aws教程找到的

在通过pgadmin连接到postgresql实例之前，一切都进展顺利

我输入了适当的用户/pw信息，并适当地复制/粘贴了数据库的地址

我的aws仪表板上的端口确实是5432

我收到以下错误消息：

Server doesn't listen
The server doesn't accept connections: the connection library reports 
could not connect to server: Operation timed out Is the server running on host "my_database_name.some_stuff.us-west-2.rds.amazonaws.com" (52.10.228.18) and accepting TCP/IP connections on port 5432? 
If you encounter this message, please check if the server you're trying to contact is actually running PostgreSQL on the given port. Test if you have network connectivity from your client to the server host using ping or equivalent tools. Is your network / VPN / SSH tunnel / firewall configured correctly? 
For security reasons, PostgreSQL does not listen on all available IP addresses on the server machine initially. In order to access the server over the network, you need to enable listening on the address first. 
For PostgreSQL servers starting with version 8.0, this is controlled using the "listen_addresses" parameter in the postgresql.conf file. Here, you can enter a list of IP addresses the server should listen on, or simply use '*' to listen on all available IP addresses. For earlier servers (Version 7.3 or 7.4), you'll need to set the "tcpip_socket" parameter to 'true'. 
You can use the postgresql.conf editor that is built into pgAdmin III to edit the postgresql.conf configuration file. After changing this file, you need to restart the server process to make the setting effective. 
If you double-checked your configuration but still get this error message, it's still unlikely that you encounter a fatal PostgreSQL misbehaviour. You probably have some low level network connectivity problems (e.g. firewall configuration). Please check this thoroughly before reporting a bug to the PostgreSQL community. 

步骤1 你得到的对话和我在上面看到的一样。废话

步骤2 去你的房间

步骤3 去你的房间

步骤4 如果您的帐户与我的帐户相同，您将看到以下文本：

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. 
Go to the EC2 Console to view and manage your VPC Security Groups. 
For more information, see AWS Documentation on Supported Platforms and Using RDS in VPC.

步骤5返回并检查您的RDS安全组名称（RDS->instances右键单击您的实例）。您将看到与此DB实例关联的VPC安全组列表

您将看到如下内容：

默认值（sg-********）（活动）

步骤6在数据库中查找与数据库匹配的

sg-******

。右击那个。编辑入站/出站规则以添加postgresql

尝试再次连接

这解决了我的问题

---

如果这不能解决您的问题，我非常抱歉，但我希望本文档会给我带来一些调试方面的麻烦。

转到安全组中的AWS服务，单击安全组id。从“操作”按钮单击“编辑入站角色”，然后将“源”更改为“我的ip”

---

检查您为RDS实例选择的安全组。将端口5432添加到该安全组，以允许从network@VaoTsun安全组设置为默认值，当我转到“安全组设置”时，它为入站连接端口选择了“全部”。如果使用向导，它会自动创建

rds启动向导

安全组，该组允许从当前外部IP进入边界。