Assign static IP addresses for egress traffic

This document shows you how to assign your own enterprise IP addresses, or static Google Cloud IP addresses, that Secure Web Proxy uses for egress traffic.

Before you begin

  • Complete the initial setup steps.

  • Ensure that you have a list of static IPv4 addresses reserved to use for Secure Web Proxy. If you want to reserve IP addresses in Google Cloud, see the gcloud compute addresses create command to create an address resource.

  • Verify that you have the Google Cloud CLI version 406.0.0 or later installed:

    gcloud version | head -n1

    If you have an earlier gcloud CLI version installed, update the version:

    gcloud components update --version=406.0.0

Enable static IP addresses for Secure Web Proxy

Do the following:

  1. Identify the Cloud Router name assigned during Secure Web Proxy provisioning:

    gcloud compute routers list \
      --regions REGION_NAME \
      --filter="network:(NETWORK_NAME) AND name:(swg-autogen-router-*)" \

    Replace the following:

    • REGION_NAME: the region that the Cloud Router is deployed for Secure Web Proxy
    • NETWORK_NAME: the name of your VPC network

    The output is similar to the following:

  2. List the external auto-provisioned IP addresses assigned during Secure Web Proxy provisioning:

    gcloud compute routers get-status ROUTER_NAME  \

    The output is similar to the following:

    kind: compute#routerStatusResponse
      - autoAllocatedNatIps:
        minExtraNatIpsNeeded: 0
        name: swg-autogen-nat
        numVmEndpointsWithNatMappings: 3
  3. Update the Cloud NAT gateway to use your predefined IP range:

    gcloud compute routers nats update swg-autogen-nat  \
        --router=ROUTER_NAME \
        --nat-external-ip-pool=IPv4_ADDRESSES... \

    Replace IPv4_ADDRESSES with the name of the external IPv4 address resource that you intend to use, separated by a comma (,).

    The fixed set of IP addresses assigned by Secure Web Proxy can't be autoscaled. When you provide a list of external IP addresses for Cloud NAT, ensure that enough IP addresses are assigned to process the traffic by Secure Web Proxy. We recommend a minimum of five IP addresses.

    If you expect a significant traffic volume, such as greater than 10k queries per second, we recommend that you start with an auto-assigned configuration and maximum utilization workload. In this case, you can monitor the autoscaled IP address count as a reference for manually configuring your egress IP addresses.

  4. Verify that your IP range is assigned to the Cloud NAT gateway:

    gcloud compute routers nats describe swg-autogen-nat \
      --router=ROUTER_NAME  \

    The output is similar to the following:

    enableEndpointIndependentMapping: false
    icmpIdleTimeoutSec: 30
      enable: false
      filter: ALL
    name: swg-autogen-nat
    natIpAllocateOption: MANUAL_ONLY
    sourceSubnetworkIpRangesToNat: ALL_SUBNETWORKS_ALL_IP_RANGES

What's next?