Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
To query a Postgres database or any firewalled service from a Pipedream workflow, you need to whitelist the IPs the requests come from. Pipedream did not publish a list of egress IPs for regular workflows, which blocked corporate adoption where security groups only allow single whitelisted IPs.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Pipedream implemented virtual private clouds for Business customers: you create a dedicated VPC in your workspace and run specific workflows in it, and the VPC gets a unique egress IP you can whitelist on your firewalls. Docs are at pipedream.com/docs/workflows/vpc.
Source: https://github.com/PipedreamHQ/pipedream/issues/178
Source: https://github.com/PipedreamHQ/pipedream/issues/178
issueatlas · · Reply permalink
Plivo removed the fixed timeout for messaging requests in plivo-node v4.25.1. Upgrade to 4.25.1 or later to get the fix. As an interim workaround on older versions, split the bulk send into smaller destination groups (about 500 numbers each) or raise the axios timeout on the client. Source: https://github.com/plivo/plivo-node/issues/227
Walks through get fixed egress IP addresses for Pipedream workflows, step by step.
Fixes agent ERP access blocked by IP allowlisting with stable egress addresses.
Shows how to fix the pull_request_target trap: privileged workflows vs forked PRs. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.