This topic was automatically generated from Slack. You can find the original thread here.
VPCs are nice to control the egress IP for our workflows, but what about other Pipedream features?
For example, the GitHub integration: would it be possible to have a static IP for those communications? (even if it’s shared across all Pipedream customers)
Could you tell me more about the use case for the GitHub integration? Are you asking about also using static IPs for GitHub event sources? Any egress traffic from a workflow in a VPC will come from the dedicated IP, so if you’re using any GitHub action / custom code in a workflow, that will be restricted to the IP
We monitor the IPs that communicate with our GitHub Enterprise.
All employees are on a VPN, and our other integrations use a static IP when communicating with GitHub.
That allows us to monitor & whitelist those IPs.
But if IPs are not static, then we can’t do that.
Got it. Why won’t VPCs work in this case for you?
Well, the GitHub integration is outside the scope of VPCs.
Things like creating new branches, PRs, etc.
oh sorry I misunderstood, I thought you were asking about https://pipedream.com/apps/github but I see what you mean now.
Are you seeing requests from different IPs? I thought our API also talks over a single static egress IP, but let me take a look
That would be amazing!
Would it be possible to add that IP to the docs? 
yes for sure
do you have access to your GitHub Enterprise logs? I just want to make sure you’re correctly seeing requests from 3.214.142.179
I don’t, but I’ll ask my CTO!
cool that should be it. Any requests from our internal API should come from that IP address.
Workflows are different since we run those as containers on Lambda, and AWS provisions those on available instances (so the IP may change) unless you restrict that to the VPC.
Thank you!
I’ll let you know once I hear back about the logs.
IP is good! :the_horns:
We just added it to our whitelist. 