Unable to connec to to RDS Proxy

Has anyone been able to configure Jets to use an RDS Proxy?

I have followed the tutorials, attached the lambdas to a VPC according to https://rubyonjets.com/docs/considerations/vpc/ and even manually added the proxy on the Lambda Configuration tab but it just does not connect. I keep receiving timeout on any lambda func but the connection is fine when using an EC2 instance on the same VPC.

With a bit more testing I found out that when using the VPC configuration provided in https://rubyonjets.com/docs/considerations/vpc/ the lambdas stop working altogether, even with the standard RDS.
As soon as I remove the VPC in Lambda>Functions>Fname>Configuration>VPC>Edit it comes back to life again (if using standard RDS)

I was able to work with lambdas and VPC by using VPC Endpoints but only with RDS. As soon as I change the endpoint to an RDS proxy, I get the following error message:
“errorMessage”: “could not connect to server: No such file or directory\n\tIs the server running locally and accepting\n\tconnections on Unix domain socket “/var/run/postgresql/.s.PGSQL.5432”?\n”,
“errorType”: “FunctionActiveRecord::ConnectionNotEstablished

Final update for the day :slight_smile:
I have managed to use RDS Proxy with Lambda but it is not really straightforward. NAT seems to not work and we have to manually insert many services as VPC Endpoints (lambda, cloudformation, sqs, rds, etc).
Moreover, the original proxy endpoint would not resolve at all. I had to use an EC2 instance and try to ping the endpoint. It did not work the first time, but later I got a related endpoint name from the ec2 instance and used this new name instead of the one provided by the proxy dashboard. It finally worked.