This topic was automatically generated from Slack. You can find the original thread here.
Hey, if you aren’t using VPC will the IP address of the workflows always be the AWS us-east-1 region? I was testing the workflow in build mode in Pipedream and I checked the IP address and its not one of these IP address (us-east-1). Issue is I am trying to connect to an FTP server that whitelists IP addresses that it can accept requests from.
Yes, we spin up a dedicated VPC with a dedicated egress IP, accessible only to your workspace. That VPC lives in AWS us-east-1.
Those IP address you linked to look like egress IPs for the AWS Developer Tools console product specifically. The full range of IPs is much broader.
If you aren’t using a VPC, we’ll still send requests from us-east-1
But the set of us-east-1 IPs is broad — on the order of millions of IP addresses. This is why we recommend spinning up a dedicated Pipedream VPC if you need to talk to a service that requires whitelisting IPs. You can also connect to your own bastion host / proxy server and route traffic through that
Thanks for quick response . I see. Will the IP address that is spun up for the workspace change? For example, can I get the IP address for requests made by the workspace and then add this to my whitelist?
If you create a Pipedream VPC, you’ll get a dedicated, static IP address that will not change. Any requests from workflows sent from that VPC will come from that IP address. So as long as you’re using that same VPC, the IP address won’t change
ah I see, so if you aren’t using pipedream VPC then IP address will change but with pipedream VPC it won’t change. Thanks. 
that’s correct!