This topic was automatically generated from Slack. You can find the original thread here.
Hi. I’m sending HTTP requests to Pipedream’s request bins, but working from a server behind a firewall. I need to whitelist Pipedream’s servers. I’ve been told that simply allowing all traffic to *.pipedream.net is unacceptable due to firewall performance reasons, so I could do with an IP address range instead. All I can find is documentation about traffic from Pipedream, rather than to it.
Hi , by default, any network request you make from Pipedream will originate from the us-east-1 region of AWS.
AWS publishes the IP address range for all regions, but Pipedream shares this range with other services using AWS.
You can find the AWS IP address range here
if you need a specific single outbound IP address for workspaces, with our Business tier you can run your own workflows in a single private VPC
Hi it’s more for requests to Pipedream’s servers, rather than from 
Apologize, I see. In this case I think you can whitelist only the webhook url you have created on Pipedream. Unfortunately there’s no static IP for you to whitelist
oof. Ok, understand
is there, by any chance, an alternative URL format that could be used, e.g. instead of https://eo8v9ejqfey5zqf.m.pipedream.net it could be https://m.pipedream.net/eo8v9ejqfey5zqf? So I could ask to whitelist m.pipedream.net and this would work for any request bin URL?
unfortunately that is not possible 
… but a cool idea, no? 
admittedly for maybe a small use case!
Actually there’s a ticket tracking that effort here, basically it will allow you use custom domain
so there is. Thanks Leo
Hi , we have also released VPCs for workflows for just this use case:
You can assign multiple workflows to use the same static outbound IP address for database connections, HTTP requests, etc:
