VPC peering
Currently, if your database of some of your services are not accessible to the public internet you can’t access them inside your Trigger.dev tasks (unless you self-host the entire platform).
There are many ways we could solve this. One obvious solution is for us to provide a Bridge Connector that you can run inside your cluster and it would only allow access from your Trigger.dev tasks. We use a tool like this to access our restricted database outside of AWS.
It would be very useful if you can share the kind of private resources you need to use in Trigger.dev and what solutions you would be happy with!
Comments13
Brent Farese
Nov 20, 2025
We absolutely need this at Aline to use RDS Proxy.
Tanawat Tassana
Sep 1, 2024
I have use trigger.dev tasks as a core component of my projects. Most of them using docker private network so the services are connected together inside the network. Without this I cannot migrate my tasks to v3.
Niels
Oct 1, 2024
Without this it’s more difficult to use the cloud based solution together with my Kubernetes cluster. So I’ve went with the self hosting option for now, which is an added complexity. With v2 this wasn’t the problem at all.
An Anonymous User
Jan 14, 2025
@mattaitken is there any work around on this before v2 stopped? Don't want to migrate away from trigger.dev at all but cannot go v3 without this feature.
Younes Barrad
Apr 17, 2025
A simple use case would be something like PlanetScale. Currently, we need to restrict access to our database to specific IP addresses. However, since most of our trigger jobs connect directly to the database, we can't enforce this restriction without breaking their functionality. This feature is therefore essential for our needs. If there's any possibility of addressing this, it would be extremely helpful for us. Thank you!
An Anonymous User
May 13, 2025
We’ll also need this, and the ideal solution would be also to be able to run the workers inside our infra directly.
An Anonymous User
Nov 16, 2025
Is this being done? We have an AWS RDS DB we need to connect to and would like to do that securely.
An Anonymous User
Feb 24
We need this as well to consider trigger.dev as an option in our stack.
Skylar Graika
Mar 4
Yeah, we also need this. This is going to be pretty important for our Enterprise offering.
An Anonymous User
Apr 15
With the v4.4.4 release, has this feature been made available? It seems to be mentioned in the release notes, but I’m not seeing it in Trigger.dev Cloud.