Accelerate cannot connect to Postgres RDS inside of VPC with static IPs configured
Using latest version of Prisma on a node server and Postgres 13 in AWS RDS.
We're seeing the error
Accelerate was not able to connect to your database. The underlying error is: Health Check of Query Engine timed out.
We have an RDS instance inside of a VPC and allowed the static IPs to connect inbound to our database. Do you have any recommendations on how to troubleshoot? Are there internal logs from prisma side that can help us debug?9 Replies
Howdy, friend! I'm the Prisma AI Help Bot — fast answers from me, or slow, hand-crafted wisdom from a dev? Choose wisely, adventurer.
Hey @ethan 👋
I responded to your support ticket 🙂
We can continue conversation here if you like.
I checked with our team and it seems that the error occurs because Accelerate is not able to connect to your database
They recommended checking if static IPs are configured correctly
hey nurul! thanks - yeah they are definitely configured correctly i triple checked
our DB is private though with a NAT gateway
hmm! are you able to connect to the database via a GUI tool like pgAdmin or similar? This error usually occurs if database is not reachable for some reason
we connect to our database from our web applications that live within our VPC
we set up inbound rules on the security group to accept requests from your static IPs
Okay!
Do the RDS or Postgres logs show any attempted connections from Accelerate? If there are no log entries at all, we can assume the connection never reached the DB (likely a networking/firewall issue)
hm i didnt see anything specific other than something about connection peer being closed
Is the RDS publicly accessible or private‐only?
private-only