Able to setup Accelerate, unable to setup Pulse. AWS RDS Postgres.
The error : "Prisma Pulse could not reach the specified datasource db url. This could be caused by an incorrect datasource URL or database firewall rules, or certificate issues. This is probably not a problem with Prisma Pulse. The network error was: "Postgres client.connect() is unresponsive."
With the connection string, I can connect using other pgTools from my own computer. My Prisma ORM is using the same connection string and is able to function with Accelerate.
I have followed the instructions in (https://www.prisma.io/docs/pulse/database-setup/aws-rds) and set the rds.logical_replication to 1 (true).
The necessary inbound rules in VPC Security Group has been adjusted (and hence the Accelerate is able to function well).
Anything else that I might have missed?
Prisma Pulse: AWS RDS | Prisma Documentation
Instructions to use AWS RDS with Prisma Pulse
7 Replies
Hi @leokid 👋
Can you please provide me with your Github handle? Also, can you try adding
sslmode=require to your connection string and try again?My github handle is dr-msr
I have tried adding the sslmode=require but it still didnt work.
On a related setting, my AWS RDS parameter group includes the parameter rds.force_ssl 0 (false). Do you think this might be related?
Thanks for your time, appreciate it.
I assume your database is not publicly accessible, right?
Are only certain specific IPs allowed to connect to your database?
The database is set to be publicly accessible. The security group access also has been set to allow all traffic inbound from anywhere.
@leokid - Since you're able to connect to RDS with other tools it seems like you might be missing ipv6 access in your SG. As ipv4 is allowed from anywhere and you're able to connect with pgTools. Pulse might be using ipv6 and as that's not allowed it would eventually time out because of the rules in your SG.
Thank you for the response.
I see, that might be a problem because due to the nature of the data, i am using AWS Data Center region that currently not supporting IPv6. Hmm 🤔
If this ipv6 issue is really the case, It is either i have to change my database provider, or explore different solution.
Just wondering So in security group you are not seeing option Anywhere-IPv6 ?