Set up and manage network address translation with Public NAT

This page shows you how to configure and manage network address translation (NAT) by using a Public NAT gateway. Before setting up Cloud NAT, read the Public NAT overview.

Limitations

  • If you change the network tier of the automatically allocated IP addresses for a Cloud NAT gateway, all connections on the old IP addresses immediately close.

  • If you use manual NAT IP address allocation, and you change the IP addresses that are used for Cloud NAT, all connections on the old IP addresses immediately close. To avoid this, see Drain external IP addresses associated with NAT.

  • If you configure a Cloud NAT gateway with static port allocation, and you reduce the minimum ports per VM, established NAT connections might be broken. For more information, see Reducing ports per VM.

  • If you configure a Cloud NAT gateway with dynamic port allocation, and you make any further configuration changes, established NAT connections might be broken. When the configuration change, the number of ports currently allocated to each VM might be temporarily reset to the minimum number configured. For more information, see Reducing ports per VM.

  • If you configure a Cloud NAT gateway with dynamic port allocation and then turn off dynamic port allocation, all VM connections that use the NAT gateway are closed. For more information, see Switch port allocation method.

  • If Endpoint-Independent Mapping is turned on, you can't configure dynamic port allocation or NAT rules.

  • Cloud NAT does not support IP fragments.

  • A Cloud NAT configuration is tied to a Virtual Private Cloud network. So, the configuration applies to all the resources that belong to the subnets of that network. You can't choose specific VMs to be served by a Cloud NAT gateway.

Before you begin

Complete the following tasks before setting up a Public NAT gateway.

Get IAM permissions

The Compute Network Admin role (roles/compute.networkAdmin) gives you permissions to create a NAT gateway on Cloud Router, reserve and assign NAT IP addresses, and specify subnetworks (subnets) whose traffic should use network address translation by the NAT gateway.

Set up Google Cloud

Before you get started, set up the following items in Google Cloud.

  1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
  2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  3. Make sure that billing is enabled for your Google Cloud project.

  4. Install the Google Cloud CLI.
  5. To initialize the gcloud CLI, run the following command:

    gcloud init
  6. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  7. Make sure that billing is enabled for your Google Cloud project.

  8. Install the Google Cloud CLI.
  9. To initialize the gcloud CLI, run the following command:

    gcloud init

The Google Cloud CLI instructions on this page assume that you have set your project ID before issuing commands.

  1. You can set a project ID with the following command:

    gcloud config set project PROJECT_ID
    
  2. You can also view a project ID that is already set:

    gcloud config list --format='text(core.project)'
    

Create Public NAT configurations

Set up a simple configuration

This configuration automatically allocates the necessary external IP addresses to provide NAT services to a region. VM instances without external IP addresses in any subnet of the region are provided internet access through NAT. This configuration uses static port allocation, which means that each VM is allocated the same number of ports. This configuration also turns on logging for all log types.

When you use automatic NAT IP address allocation, Google Cloud reserves IP addresses in your project automatically. These addresses count against your static IP address quotas in the project.

You can enable or disable Endpoint-Independent Mapping for your gateway. For settings, see Set endpoint mapping.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click Get started or Create NAT gateway.

  3. Enter a Gateway name.

  4. For NAT type, select Public.

  5. Select a VPC network for the NAT gateway.

  6. Set the Region for the NAT gateway.

  7. Select or create a Cloud Router in the region.

  8. Click Advanced configuration.

  9. Under Stackdriver logging, select Translation and errors. This sends all logs to Cloud Logging.

  10. Click Create.

gcloud

  1. Before setting up a Cloud NAT gateway, first create your Cloud Router. You need this Cloud Router to set up your Cloud NAT gateway.

  2. Set up the Cloud NAT gateway:

    gcloud compute routers nats create NAT_CONFIG \
       --router=NAT_ROUTER \
       --region=REGION \
       --auto-allocate-nat-external-ips \
       --nat-all-subnet-ip-ranges \
       --enable-logging
    

    Replace the following:

    • NAT_CONFIG: the name of your NAT configuration.
    • NAT_ROUTER: the name of your Cloud Router.
    • REGION: the region of the NAT to create. If not specified, you might be prompted to select a region (interactive mode only).

Terraform

You can use a Terraform module to create a Cloud Router with a NAT gateway.

module "cloud_router" {
  source  = "terraform-google-modules/cloud-router/google"
  version = "~> 6.0"
  name    = "my-cloud-router"
  project = var.project_id
  network = module.vpc.network_name
  region  = "us-central1"

  nats = [{
    name                               = "my-nat-gateway"
    source_subnetwork_ip_ranges_to_nat = "LIST_OF_SUBNETWORKS"
    subnetworks = [
      {
        name                     = module.vpc.subnets["us-central1/test-subnet-01"].id
        source_ip_ranges_to_nat  = ["PRIMARY_IP_RANGE", "LIST_OF_SECONDARY_IP_RANGES"]
        secondary_ip_range_names = module.vpc.subnets["us-central1/test-subnet-01"].secondary_ip_range[*].range_name
      }
    ]
  }]
}

The resulting NAT gateway uses the following default values:

enable_endpoint_independent_mapping = true
icmp_idle_timeout_sec               = 30
min_ports_per_vm                    = 0
nat_ip_allocate_option              = "AUTO_ONLY"
source_subnetwork_ip_ranges_to_nat  = "ALL_SUBNETWORKS_ALL_IP_RANGES"
tcp_established_idle_timeout_sec    = 1200
tcp_transitory_idle_timeout_sec     = 30
udp_idle_timeout_sec                = 30
log_config {
    enable = true
    filter = "ALL"
}

Specify IP addresses for NAT

You can manually allocate NAT IP addresses for a NAT gateway. If you choose manual allocation, make sure to allocate enough IP addresses to avoid dropped packets. For more information, see NAT IP addresses.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click Get started or Create Cloud NAT gateway.

  3. Enter a Gateway name.

  4. Select a VPC network.

  5. Set the Region for the NAT gateway.

  6. Select or create a Cloud Router in the region.

  7. Set NAT IP addresses to Manual.

  8. Select or create a static reserved external IP address to use for NAT.

  9. If you want to specify additional IP addresses, click Add IP address, and then select or create an additional static reserved external IP address.

  10. Click Create.

gcloud

gcloud compute routers nats create NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --nat-all-subnet-ip-ranges \
    --nat-external-ip-pool=IP_ADDRESS1,IP_ADDRESS2

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.
  • NAT_ROUTER: the name of your Cloud Router.
  • REGION: the region of the NAT to create. If not specified, you might be prompted to select a region (interactive mode only).
  • IP_ADDRESS1: a static reserved external IP address to use for NAT.
  • IP_ADDRESS2: another static reserved external IP address to use for NAT.

Set up NAT by using IP addresses from a specific network tier

You can create a Cloud NAT gateway by assigning external IP addresses from a specific network tier.

Set up NAT with automatic IP address allocation from a specific network tier

When you create a Cloud NAT gateway with automatic NAT IP address allocation, you can specify the Network Service Tiers (Premium Tier or Standard Tier) from which the Cloud NAT gateway allocates the IP addresses.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click Get started or Create Cloud NAT gateway.

  3. Enter a gateway name.

  4. Select a Virtual Private Cloud (VPC) network for the NAT gateway.

  5. Set the region for the NAT gateway.

  6. Select or create a Cloud Router in the region.

  7. In the Cloud NAT IP addresses list, select Automatic (recommended).

  8. For Network service tier, choose either Premium or Standard.

  9. Click Create.

gcloud

Use the gcloud CLI to run the compute routers nats create command with the flag --auto-network-tier.

gcloud compute routers nats create NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --nat-all-subnet-ip-ranges \
    --auto-allocate-nat-external-ips \
    --auto-network-tier=AUTO_NETWORK_TIER 

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.

  • NAT_ROUTER: the name of your Cloud Router.

  • REGION: the region of the NAT to create. If not specified, you might be prompted to select a region (interactive mode only).

  • AUTO_NETWORK_TIER: the network tier to use when automatically allocating IP addresses for the Cloud NAT gateway. The allowed values are PREMIUM and STANDARD. If not specified, then the current project-level default tier is associated with the Cloud NAT gateway.

Set up NAT with manual IP address assignment from a specific network tier

When creating a Cloud NAT gateway, you can choose to manually assign NAT IP addresses from either Premium Tier or Standard Tier or both, subject to certain conditions.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click Get started or Create Cloud NAT gateway.

  3. Enter a gateway name.

  4. Select a Virtual Private Cloud network for the NAT gateway.

  5. Set the region for the NAT gateway.

  6. Select or create a Cloud Router in the region.

  7. In the Cloud NAT IP addresses list, select Manual.

  8. For Network service tier, choose either Premium or Standard.

  9. Select or create a static reserved external IP address to use for NAT.

  10. If you want to specify additional IP addresses, click Add IP address, and then select or create an additional static reserved external IP address.

  11. Click Create.

gcloud

To create a NAT gateway by manually assigning external IP addresses from a specific network tier, use the --nat-external-ip-pool field of the gcloud compute routers nats create command.

For information about manually assigning NAT IP addresses, see Specify IP addresses for NAT.

Set up NAT with dynamic port allocation

This configuration uses dynamic port allocation with automatic NAT IP address allocation. You can also configure dynamic port allocation with manual NAT IP address allocation.

Using dynamic port allocation lets the NAT gateway allocate different numbers of ports to each VM based on usage.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click Get started or Create Cloud NAT gateway.

  3. Enter a Gateway name.

  4. Select a VPC network.

  5. Set the Region for the NAT gateway.

  6. Select a Cloud Router, or click Create new router to create a new router.

  7. Click Advanced configuration.

  8. Select Enable Dynamic Port Allocation.

  9. Select the Minimum ports per VM instance. The default value is 32.

  10. Select the Maximum ports per VM instance. The default value is 65536.

  11. Click Create.

gcloud

gcloud compute routers nats create NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --auto-allocate-nat-external-ips \
    --nat-all-subnet-ip-ranges \
    --enable-dynamic-port-allocation \
    [ --min-ports-per-vm=MIN_PORTS ] \
    [ --max-ports-per-vm=MAX_PORTS ]

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.

  • NAT_ROUTER: the name of your Cloud Router.

  • REGION: the region of the NAT to create. If not specified, you might be prompted to select a region (interactive mode only).

  • MIN_PORTS: the minimum number of ports to allocate for each VM. If dynamic port allocation is turned on, MIN_PORTS must be a power of 2, and can be between 32 and 32768. Default is 32.

  • MAX_PORTS: the maximum number of ports to allocate for each VM. MAX_PORTS must be a power of 2, and can be between 64 and 65536. MAX_PORTS must be greater than MIN_PORTS. Default is 65536.

Specify subnet ranges for NAT

By default, NAT works for all primary and secondary IP ranges for all subnets in the region for the given VPC network. You can restrict which primary and secondary subnet ranges can use NAT.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click Get started or Create Cloud NAT gateway.

  3. Enter a Gateway name.

  4. Select a VPC network.

  5. Set the Region for the NAT gateway.

  6. Select or create a Cloud Router in the region.

  7. Under NAT mapping, set Source to Custom.

  8. Select a subnet.

  9. In the IP ranges drop-down list, select the subnet IP ranges to include.

  10. Click OK.

  11. If you want to specify additional ranges, click Add subnet and IP range.

  12. Click Create.

gcloud

gcloud compute routers nats create NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --auto-allocate-nat-external-ips \
    --nat-custom-subnet-ip-ranges=SUBNETS_RANGES_LIST

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.
  • NAT_ROUTER: the name of your Cloud Router.
  • REGION: the region of the NAT to create. If not specified, you might be prompted to select a region (interactive mode only).
  • SUBNETS_RANGES_LIST: a comma-separated list of subnet names. For example:
    • SUBNET_NAME_1,SUBNET_NAME_2: includes only the primary subnet range of SUBNET_NAME_1 and SUBNET_NAME_2.
    • SUBNET_NAME:SECONDARY_RANGE_NAME: includes the secondary range SECONDARY_RANGE_NAME of subnet SUBNET_NAME. It does not include the primary range of SUBNET_NAME.
    • SUBNET_NAME_1,SUBNET_NAME_2:SECONDARY_RANGE_NAME: includes the primary range of SUBNET_NAME_1 and the specified secondary range SECONDARY_RANGE_NAME of subnet SUBNET_NAME_2.

Configure logging

To add (turn on), modify, or remove logging for an existing Public NAT gateway, see Configuring logging.

View NAT configuration

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. To view NAT gateway details, mapping information, or configuration details, click the name of your NAT gateway.

  3. To view NAT status, see the Status column for your NAT gateway.

gcloud

You can view the NAT configuration details by running the following commands:

  • View the Public NAT gateway configuration.

    gcloud compute routers nats describe NAT_CONFIG \
       --router=NAT_ROUTER \
       --region=REGION
    

    Replace the following:

    • NAT_CONFIG: the name of your NAT configuration.
    • NAT_ROUTER: the name of your Cloud Router.
    • REGION: the region of the NAT to describe. If not specified, you might be prompted to select a region (interactive mode only).
  • View the mapping of the IP:port-ranges allocated to each VM's interface.

    gcloud compute routers get-nat-mapping-info NAT_ROUTER \
      --region=REGION
    
  • View the status of the Public NAT gateway.

    gcloud compute routers get-status NAT_ROUTER \
      --region=REGION
    

View NAT IP addresses assigned to a gateway

To view NAT IP addresses that were automatically added, see the list of static external IP addresses. These addresses count toward per-project quotas.

Console

In the Google Cloud console, go to the IP addresses page and then click External IP addresses.

Go to IP addresses

gcloud

  • To list all allocated NAT IP addresses, use the following command:

    gcloud compute routers get-nat-ip-info NAT_ROUTER \
      --region=REGION
    

    For more examples, see gcloud compute routers get-nat-ip-info.

Update NAT configuration

After you set up your Public NAT gateway, you can update the gateway configuration based on your requirements. The following sections list the tasks that you can perform to update your Public NAT gateway.

Change subnets and IP address resources associated with NAT

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click your NAT gateway.

  3. Click Edit.

  4. Under NAT mapping, set Source to Custom.

  5. Select a subnet.

  6. In the IP ranges drop-down list, select the subnet IP ranges to include.

  7. If you want to specify additional ranges, click Add subnet and IP range.

  8. Click the NAT IP addresses drop-down list, and then select Automatic or Manual.

  9. If you select Manual, specify an external IP address.

  10. For high availability with manual IP addresses, click Add IP address, and then add a second address.

  11. Click Save.

gcloud

gcloud compute routers nats update NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --nat-external-ip-pool=IP_ADDRESS2,IP_ADDRESS3 \
    --nat-custom-subnet-ip-ranges=SUBNETS_RANGES_LIST

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.
  • NAT_ROUTER: the name of your Cloud Router.
  • REGION: the region of the NAT to update. If not specified, you might be prompted to select a region (interactive mode only).
  • IP_ADDRESS2: a manual external IP address
  • IP_ADDRESS3: another manual external IP address
  • SUBNETS_RANGES_LIST: a comma-separated list of subnet names. For example:
    • SUBNET_NAME_1,SUBNET_NAME_2: includes only the primary subnet range of SUBNET_NAME_1 and SUBNET_NAME_2.
    • SUBNET_NAME:SECONDARY_RANGE_NAME: includes the secondary range SECONDARY_RANGE_NAME of subnet SUBNET_NAME. It does not include the primary range of SUBNET_NAME.
    • SUBNET_NAME_1,SUBNET_NAME_2:SECONDARY_RANGE_NAME: includes the primary range of SUBNET_NAME_1 and the specified secondary range SECONDARY_RANGE_NAME of subnet SUBNET_NAME_2.

Delete subnets associated with Public NAT

You can remove specific subnets from the NAT gateway that are no longer in use.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click your NAT gateway.

  3. Click Edit.

  4. Delete the subnet that you want to remove from NAT mapping.

  5. Click Save.

Change external IP addresses associated with Public NAT

You can change the list of external IP addresses for a given gateway or switch from manual to automatic IP allocation. When you do, Google Cloud removes the old addresses and adds the new ones. Any existing connections on the old IP addresses immediately close. To let existing connections continue while preventing new connections on those IP addresses, see Drain external IP addresses associated with NAT.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click your NAT gateway.

  3. Click Edit.

  4. Click the NAT IP addresses drop-down list, and then select Automatic or Manual.

  5. If you select Manual, specify an external IP address.

  6. For high availability, click Add IP address, and then add a second address.

  7. Click Save.

gcloud

gcloud compute routers nats update NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --nat-external-ip-pool=IP_ADDRESS2,IP_ADDRESS3

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.
  • NAT_ROUTER: the name of your Cloud Router.
  • REGION: the region of the NAT to update. If not specified, you might be prompted to select a region (interactive mode only).
  • IP_ADDRESS2: a manual external IP address.
  • IP_ADDRESS3: another manual external IP address.

Update NAT by using external IP addresses from a different network tier

You can update an existing Cloud NAT gateway by changing the network tier of the external IP addresses associated with the gateway.

Update NAT by changing the network tier of automatically allocated external IP addresses

When you change the network tier of automatically allocated external IP addresses associated with an existing NAT gateway, Google Cloud removes the old addresses and adds new ones from the specified network tier. Any existing connections on the old IP addresses immediately close.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click your NAT gateway name that has automatically allocated IP addresses.

  3. Click Edit.

  4. For Network service tier, choose either Premium or Standard.

  5. Click Save.

gcloud

Use the gcloud CLI to run the compute routers nats update command with the flag --auto-network-tier.

gcloud compute routers nats update NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --auto-allocate-nat-external-ips
    --auto-network-tier=AUTO_NETWORK_TIER 

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.

  • NAT_ROUTER: the name of your Cloud Router.

  • REGION: the region of the NAT to create. If not specified, you might be prompted to select a region (interactive mode only).

  • AUTO_NETWORK_TIER: the network tier to use when automatically allocating IP addresses for the Cloud NAT gateway. The allowed values are PREMIUM and STANDARD. If not specified, then the current project-level default tier is associated with the Cloud NAT gateway.

Update NAT by changing the network tier of manually assigned IP addresses

You can update an existing NAT by manually specifying external IP addresses from a different tier. You can assign external IP addresses from either Standard Tier or Premium Tier or both, subject to certain conditions. Before you specify external IP addresses from a different tier, first drain the existing IP addresses to let existing connections continue and prevent new connections on the existing IP addresses.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click your NAT gateway name that has manually assigned IP addresses.

  3. Click Edit.

  4. To specify IP addresses from a tier that is different from the currently selected tier, either delete all the existing IP addresses or enable draining for all the existing IP addresses.

    You cannot change the network tier if draining is disabled for an existing IP address.

  5. For Network service tier, choose either Premium or Standard.

  6. Select an external IP address from the list of active, available IP addresses.

  7. Optional: To add more IP addresses, click Add IP addresses.

  8. Click Save.

gcloud

To update an existing gateway by manually changing the existing external IP addresses with new ones from a different network tier, use the --nat-external-ip-pool field of the compute routers nats update command.

For more information about manually changing the existing external IP addresses, see Change external IP addresses associated with NAT.

Drain external IP addresses associated with NAT

Before you remove a manually configured IP address, you can drain it so that existing connections aren't disrupted. When an IP address is drained, all existing connections are allowed to continue until they expire naturally. You can view the logs to check the status of existing connections.

No new connections are accepted on the drained IP addresses. However, the IP address stays associated with the NAT configuration.

You must have at least one active address in a NAT configuration, which means that you cannot drain all IP addresses in a configuration.

To see the state of your NAT IP addresses, you can Show NAT status.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click your NAT gateway.

  3. Click Edit.

  4. For NAT IP addresses, set the IP draining value next to the IP address to On.

  5. Click Save.

gcloud

To drain an address, you must move it from the active pool to the drain pool in the same command. If you remove it from the active pool without adding it to the drain pool in a single command, the IP address is deleted from service and existing connections are terminated immediately.

If you move an IP address from the drain pool to the active pool, you undrain the IP address. If you remove a NAT IP address from both pools, you disconnect it from the NAT configuration.

This command leaves the other fields in the NAT configuration unchanged.

gcloud compute routers nats update NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    --nat-external-ip-pool=IP_ADDRESS3 \
    --nat-external-drain-ip-pool=IP_ADDRESS2

Where:

  • --nat-external-ip-pool=IP_ADDRESS3: updates the active pool to omit IP_ADDRESS2
  • --nat-external-drain-ip-pool=IP_ADDRESS2: adds IP_ADDRESS2 to the drain pool

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.
  • NAT_ROUTER: the name of your Cloud Router.
  • REGION: the region of the NAT to update. If not specified, you might be prompted to select a region (interactive mode only).
  • IP_ADDRESS3: an IP address.
  • IP_ADDRESS2: another IP address.

Set endpoint mapping

You can enable or disable Endpoint-Independent Mapping for your gateway. By default, it is disabled. Switching Endpoint-Independent Mapping from enabled to disabled (or from disabled to enabled) does not interrupt existing connections.

You cannot enable Endpoint-Independent Mapping if your NAT gateway uses NAT rules or dynamic port allocation.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Click your NAT gateway.

  3. Click Edit.

  4. Click Advanced configurations.

  5. To enable Endpoint-Independent Mapping, select the Enable Endpoint-Independent Mapping checkbox. To disable Endpoint-Independent Mapping, clear the checkbox.

  6. Click Save.

gcloud

gcloud compute routers nats update NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION \
    [--enable-endpoint-independent-mapping | --no-enable-endpoint-independent-mapping]

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.
  • NAT_ROUTER: the name of your Cloud Router.
  • REGION: the region of the NAT to update. If not specified, you might be prompted to select a region (interactive mode only).

Delete NAT configuration

Deleting a gateway configuration removes the NAT configuration from a Cloud Router. It does not delete the router itself.

Console

  1. In the Google Cloud console, go to the Cloud NAT page.

    Go to Cloud NAT

  2. Select the checkbox next to the gateway configuration that you want to delete.

  3. On the Menu, click Delete.

gcloud

gcloud compute routers nats delete NAT_CONFIG \
    --router=NAT_ROUTER \
    --region=REGION

Replace the following:

  • NAT_CONFIG: the name of your NAT configuration.
  • NAT_ROUTER: the name of your Cloud Router.
  • REGION: the region of the NAT to delete. If not specified, you might be prompted to select a region (interactive mode only).

Quotas and limits

For quota and limit information, see the quotas page.

Example setups

These examples show you how to test Cloud NAT with Google Cloud:

What's next