- Newest
- Most votes
- Most comments
Hello.
If you are running the "psql" command from the same EC2, I don't think it will be blocked by the VPC endpoint security group.
Just to be sure, why not configure the inbound rules of the VPC endpoint security group to allow all communications and try connecting?
I think it would be a good idea to enable VPC flow logs and investigate where communication is being blocked.
https://docs.aws.amazon.com/vpc/latest/userguide/working-with-flow-logs.html#create-flow-log
Also, from where to where is the connection causing the timeout error?
If a timeout error occurs when connecting to EC2, there may be a problem with the EC2 security group.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/eice-security-groups.html#resource-security-group-rules
Relevant content
- Accepted Answerasked a year ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hi thank you for your help, I succeeded in making the connection work at my home, that's mean that the security groups are configured correctly. The problem starts at the office... I use Terraform to deploy the resources so they are exactly the same. The only thing that has changed is the internet connection to my computer, but it doesn’t make sense because the connection is made from the EC2 instance to the RDS instance threw the AWS global network