selected "PostgreSQL" for the "Type" column, which caused the values of "TCP" and "5432" to populate the "Protocol" and "Port range" columns respectively, entered my machine's IP address ("123.456.789.012/32"-no quotes and no parentheses), and left "Description - optional" blank, because, well, it's optional.įinally, I guess I'd forgotten to explicitly name the database, and so my attempts to enter what for me was ostensibly the database's name (that is, "database-1") resulted in a connection error indicating that "database-1" does not exist.clicked the "Add rule" button, which caused a table row containing the following columns: "Type", "Protocol," "Port Range," "Source," "Description - optional".clicked the "Edit inbound rules" button which directed me to the "Edit inbound rules" screen.
clicked the security group link related to my database, which directed me to that group's detail page.clicked (what for me was the one and only) link beneath the "VPC security groups" of the database's dashboard, which directed me to the EC2 Security Groups screen.To do this, from the database detail screen in AWS, I: First off, B was right-the issue was that I hadn't yet made the database itself publicly accessible via the VPC security group of which it was a member.
0 kommentar(er)
