title: GCP: How to associate Cloud Function egress with a europe-north1 IP address?
body: <p><strong>Goal</strong></p>
  <p>I'm using Google Cloud Functions for running my application logic and need to associate egress network traffic with an IP address in region <code>europe-north1</code>.</p>
  <p><strong>The problem</strong></p>
  <p>Cloud Functions are not available in region <code>europe-north1</code> so I need to keep them in some other, supported region. If I set up an external static IP address in region <code>europe-north1</code>, Cloud Function egress doesn't seem to work at all anymore; the network traffic is blocked.</p>
  <p><strong>What I've tried</strong></p>
  <p>My Cloud Functions run just fine in region <code>europe-west1</code>, and I have been able to associate egress traffic with a static IP address in region <code>europe-west1</code> successfully by following <a href="https://cloud.google.com/functions/docs/networking/network-settings#associate-static-ip" rel="nofollow noreferrer">this GCP guide</a>. This is what the setup looks like:</p>
  <pre><code>[Cloud Function] -- [Serverless VPC Access connector]
                            |
                      [VPC network]
                            |
                      [Cloud NAT gateway] -- [Cloud Router] -- [static IP address]
  </code></pre>
  <p>In this setup I have all the resources in the same region, <code>europe-west1</code>, but that's not what I want, I need the static IP in region <code>europe-north1</code>.</p>
  <p>If I get a static IP address from region <code>europe-north1</code>, the Cloud Router as well as the Cloud NAT gateway need to be in that region, too, and then egress is blocked.</p>
  <p>I've tried both of the VPC network Dynamic routing modes, regional and global, to no avail.</p>
  <p>Serverless VPC Access connectors are supported in <code>europe-north1</code> but they can't be connected to Cloud Functions in other regions (and CFs aren't supported in that region).</p>
  <p>I even started setting up a forward proxy on a VM instance but soon realised it's likely not going to work with HTTPS traffic...</p>
  <p>How can I route the traffic from Cloud Functions to a static IP in <code>europe-north1</code>?</p>