Trigger.dev @triggerdev.bsky.social · May 15 Your tasks can now connect to private resources in your AWS VPC. RDS, ElastiCache, internal APIs, self-hosted services. No public endpoint, no IP allowlist, no VPN. Over AWS PrivateLink ↓
0 likes 1 replies
?
Replies
Three steps to wire it up: 1. Create an NLB + VPC Endpoint Service in your AWS account, pointing at the resource 2. Add Trigger.dev as an allowed principal 3. We provision a VPC Endpoint on our side Your tasks get a private IP. Use it as the hostname in your connection string.