Set up a managed instance group backend

Console

1. In the Google Cloud console, go to the VPC networkspage.

   Go to VPC networks

2. Click Create VPC network.

3. Enter a Namefor the network.

4. For the Subnet creation mode, choose Custom.

5. In the New subnetsection, configure the following fields:

   1. Provide a Namefor the subnet.
   2. Select a Region.
   3. For IP stack type, select IPv4 (single-stack).
   4. Enter an IP address range. This is the primary IPv4 range for the subnet.

6. Click Done.

7. To add a subnet in a different region, click Add subnetand repeat the previous steps.

8. Click Create.

gcloud

1. Create the custom mode VPC network:

   gcloud compute networks create NETWORK 
   \
       --subnet-mode=custom

2. Within the network, create a subnet for backends:

   gcloud compute networks subnets create SUBNET 
   \
       --network= NETWORK 
   \
       --stack-type=IPV4_ONLY \
       --range=10.1.2.0/24 \
       --region= REGION 
   

   Replace the following:

   • NETWORK : a name for the VPC network.

   • SUBNET : a name for the subnet.

   • REGION : the name of the region.

Console

To support IPv4 traffic, use the following steps:

1. In the Google Cloud console, go to the Instance templatespage.

   Go to Instance templates

2. Click Create instance template.

3. For Name, enter lb-backend-template .

4. Ensure that the Boot disk is set to a Debian image, such as Debian GNU/Linux 10 (buster). These instructions use commands that are only available on Debian, such as apt-get .

5. Expand Advanced options.

6. Expand Networkingand configure the following fields:

   1. For Network tags, enter allow-health-check .
   2. In the Network interfacessection, click edit Editand make the following changes:
      • Network: NETWORK
      • Subnet: SUBNET
      • IPv4 traffic: IPv4 (single-stack)
   3. Click Done.

7. Expand Management. In the Startup scriptfield, enter the following script:

   #! /bin/bash
   apt-get update
   apt-get install apache2 -y
   a2ensite default-ssl
   a2enmod ssl
   vm_hostname="$(curl -H "Metadata-Flavor:Google" \
   http://metadata.google.internal/computeMetadata/v1/instance/name)"
   echo "Page served from: $vm_hostname" | \
   tee /var/www/html/index.html
   systemctl restart apache2

8. Click Create.

gcloud

To support IPv4 traffic , run the following command:

gcloud compute instance-templates create TEMPLATE_NAME 
\
  --region= REGION 
\
  --network= NETWORK 
\
  --subnet= SUBNET 
\
  --stack-type=IPV4_ONLY \
  --tags=allow-health-check \
  --image-family=debian-10 \
  --image-project=debian-cloud \
  --metadata=startup-script='#! /bin/bash
    apt-get update
    apt-get install apache2 -y
    a2ensite default-ssl
    a2enmod ssl
    vm_hostname="$(curl -H "Metadata-Flavor:Google" \
    http://metadata.google.internal/computeMetadata/v1/instance/name)"
    echo "Page served from: $vm_hostname" | \
    tee /var/www/html/index.html
    systemctl restart apache2'

Terraform

To create the instance template, use the google_compute_instance_template resource .

 resource "google_compute_instance_template" "default" {
  name = "lb-backend-template"
  disk {
    auto_delete  = true
    boot         = true
    device_name  = "persistent-disk-0"
    mode         = "READ_WRITE"
    source_image = "projects/debian-cloud/global/images/family/debian-11"
    type         = "PERSISTENT"
  }
  labels = {
    managed-by-cnrm = "true"
  }
  machine_type = "n1-standard-1"
  metadata = {
    startup-script = "#! /bin/bash\n     sudo apt-get update\n     sudo apt-get install apache2 -y\n     sudo a2ensite default-ssl\n     sudo a2enmod ssl\n     vm_hostname=\"$(curl -H \"Metadata-Flavor:Google\" \\\n   http://169.254.169.254/computeMetadata/v1/instance/name)\"\n   sudo echo \"Page served from: $vm_hostname\" | \\\n   tee /var/www/html/index.html\n   sudo systemctl restart apache2"
  }
  network_interface {
    access_config {
      network_tier = "PREMIUM"
    }
    network    = "global/networks/default"
    subnetwork = "regions/us-east1/subnetworks/default"
  }
  region = "us-east1"
  scheduling {
    automatic_restart   = true
    on_host_maintenance = "MIGRATE"
    provisioning_model  = "STANDARD"
  }
  service_account {
    email  = "default"
    scopes = ["https://www.googleapis.com/auth/devstorage.read_only", "https://www.googleapis.com/auth/logging.write", "https://www.googleapis.com/auth/monitoring.write", "https://www.googleapis.com/auth/pubsub", "https://www.googleapis.com/auth/service.management.readonly", "https://www.googleapis.com/auth/servicecontrol", "https://www.googleapis.com/auth/trace.append"]
  }
  tags = ["allow-health-check"]
} 

Console

1. In the Google Cloud console, go to the Instance groupspage.

   Go to Instance groups

2. Click Create instance group.

3. On the left, choose New managed instance group (stateless).

4. For Name, enter lb-backend-example .

5. Under Location, select Single zone.

6. For Region, select your preferred region.

7. For Zone, select a zone.

8. Under Instance template, select the instance template lb-backend-template .

9. For Autoscaling mode, select On: add and remove instances to the group.

   Set Minimum number of instancesto 2 , and set Maximum number of instancesto 2 or more.

10. To create the new instance group, click Create.

gcloud

1. Create the managed instance group based on the template.

   gcloud compute instance-groups managed create lb-backend-example \
      --template= TEMPLATE_NAME 
   --size=2 --zone= ZONE_A 
   

Terraform

To create the managed instance group, use the google_compute_instance_group_manager resource .

 resource "google_compute_instance_group_manager" "default" {
  name = "lb-backend-example"
  zone = "us-east1-b"
  named_port {
    name = "http"
    port = 80
  }
  version {
    instance_template = google_compute_instance_template.default.id
    name              = "primary"
  }
  base_instance_name = "vm"
  target_size        = 2
} 

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands .

Console

1. In the Google Cloud console, go to the Instance groupspage.

   Go to Instance groups

2. Click lb-backend-example.

3. On the instance group's Overviewpage, click edit Edit.

4. In the Port mappingsection, click Add port.

   1. For the port name, enter http . For the port number, enter 80 .

5. Click Save.

gcloud

Use the gcloud compute instance-groups set-named-ports command.

gcloud compute instance-groups set-named-ports lb-backend-example \
    --named-ports http:80 \
    --zone ZONE_A 

Terraform

The named_port attribute is included in the managed instance group sample .

Console

1. In the Google Cloud console, go to the Firewall policiespage.

   Go to Firewall policies

2. Click Create firewall ruleto create the firewall rule.

3. For Name, enter fw-allow-health-check .

4. Select a Network.

5. Under Targets, select Specified target tags.

6. Populate the Target tagsfield with allow-health-check .

7. Set Source filterto IPv4 ranges.

8. Set Source IPv4 rangesto 130.211.0.0/22 and 35.191.0.0/16 .

9. Under Protocols and ports, select Specified protocols and ports.

10. Select the TCPcheckbox, and then type 80 for the port numbers.

11. Click Create.

gcloud

gcloud compute firewall-rules create fw-allow-health-check \
    --network= NETWORK 
\
    --action=allow \
    --direction=ingress \
    --source-ranges=130.211.0.0/22,35.191.0.0/16 \
    --target-tags=allow-health-check \
    --rules=tcp:80

Terraform

To create the firewall rule, use the google_compute_firewall resource .

 resource "google_compute_firewall" "default" {
  name          = "fw-allow-health-check"
  direction     = "INGRESS"
  network       = "global/networks/default"
  priority      = 1000
  source_ranges = ["130.211.0.0/22", "35.191.0.0/16"]
  target_tags   = ["allow-health-check"]
  allow {
    ports    = ["80"]
    protocol = "tcp"
  }
} 

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands .

Console

1. In the Google Cloud console, go to the External IP addressespage.

   Go to External IP addresses

2. To reserve an IPv4 address, click Reserve external static IP address.

3. For Name, enter lb-ipv4-1 .

4. Set Network Service Tierto Premium.

5. Set IP versionto IPv4.

6. Set Typeto Global.

7. Click Reserve.

gcloud

gcloud compute addresses create lb-ipv4-1 \
    --ip-version=IPV4 \
    --network-tier=PREMIUM \
    --global

Note the IPv4 address that was reserved:

gcloud compute addresses describe lb-ipv4-1 \
    --format="get(address)" \
    --global

Terraform

To reserve the IP address, use the google_compute_global_address resource .

 resource "google_compute_global_address" "default" {
  name       = "lb-ipv4-1"
  ip_version = "IPV4"
} 

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands .

Console

Select the load balancer type

1. In the Google Cloud console, go to the Load balancing page.

   Go to Load balancing

2. Click Create load balancer .
3. For Type of load balancer , select Application Load Balancer (HTTP/HTTPS) and click Next .
4. For Public facing or internal , select Public facing (external) and click Next .
5. For Global or single region deployment , select Best for global workloads and click Next .
6. For Load balancer generation , select Classic Application Load Balancer and click Next .
7. Click Configure .

Basic configuration

For the load balancer Name , enter something like web-map-https or web-map-http .

Frontend configuration

1. Click Frontend configuration .
2. Set Protocol to HTTPS .
3. Select IPv4 for IPv4 traffic. Set IP address to lb-ipv4-1 , which you created earlier.
4. Set Port to 443 .
5. Click Certificate , and select your primary SSL certificate.
6. Optional: Create an SSL policy:
   1. In the SSL policy list, select Create a policy .
   2. Set the name of the SSL policy to my-ssl-policy .
   3. For Minimum TLS Version , select TLS 1.0 .
   4. For Profile , select Modern . The Enabled features and Disabled features are displayed.
   5. Click Save .
   If you have not created any SSL policies, a default SSL policy is applied.
7. Optional: Select the Enable HTTP to HTTPS Redirect checkbox to enable redirects.

   Enabling this checkbox creates an additional partial HTTP load balancer that uses the same IP address as your HTTPS load balancer and redirects incoming HTTP requests to your load balancer's HTTPS frontend.

   This checkbox can only be selected when the HTTPS protocol is selected and a reserved IP address is used.

8. Click Done .

Backend configuration

1. Click Backend configuration .
2. Under Backend services & backend buckets , select Create a backend service .
3. Add a name for your backend service, such as web-backend-service .
4. Go to the Security section, and then select Enable IAP to secure access to your applications .

   Cloud CDN and IAP are not compatible. If you have Cloud CDN enabled, and you select to enable IAP, Cloud CDN is automatically disabled.

5. Optional: Configure a default backend security policy. The default security policy throttles traffic over a user-configured threshold. For more information about default security policies, see the Rate limiting overview .

   1. To opt out of the Cloud Armor default security policy, select None in the Cloud Armor backend security policy list.
   2. To configure the Cloud Armor default security policy, select Default security policy in the Cloud Armor backend security policy list.
   3. In the Policy name field, accept the automatically generated name or enter a name for your security policy.
   4. In the Request count field, accept the default request count or enter an integer between 1 and 10,000 .
   5. In the Interval field, select an interval.
   6. In the Enforce on key field, choose one of the following values: All , IP address , or X-Forwarded-For IP address . For more information about these options, see Identifying clients for rate limiting .
6. Select Enable Cloud CDN .
7. Optional: Modify the cache mode and TTL settings.
8. Retain the other default settings.
9. Click Create .

Host and path rules

For Host and path rules , retain the default settings.

Review and finalize

1. Click Review and finalize .
2. Review your load balancer configuration settings.
3. Optional: Click Equivalent code to view the REST API request that will be used to create the load balancer.
4. Click Create .

gcloud

1. Create a health check.

   gcloud compute health-checks create http http-basic-check \
        --port 80

2. Create a backend service.

   gcloud compute backend-services create web-backend-service \
       --load-balancing-scheme=EXTERNAL \
       --protocol=HTTP \
       --port-name=http \
       --health-checks=http-basic-check \
       --global

3. Add your instance group as the backend to the backend service.

   gcloud beta compute backend-services add-backend web-backend-service \
     --instance-group=lb-backend-example \
     --instance-group-zone= ZONE_A 
   \
     --global

4. For HTTP, create a URL map to route the incoming requests to the default backend service.

   gcloud beta compute url-maps create web-map-http \
     --default-service web-backend-service

5. For HTTPS, create a URL map to route the incoming requests to the default backend service.

   gcloud beta compute url-maps create web-map-https \
     --default-service web-backend-service

Set up an HTTPS frontend

Skip this section for HTTP load balancers.

1. For HTTPS, if you haven't already done so, create the global SSL certificate resource, as shown in the following sections:
• Creating a Google-managed SSL certificate resource
• Creating a self-managed SSL certificate resource

2. For HTTPS, create a target HTTPS proxy to route requests to your URL map. The proxy is the portion of the load balancer that holds the SSL certificate for an HTTPS load balancer, so you also load your certificate in this step.

   gcloud compute target-https-proxies create https-lb-proxy \
     --url-map=web-map-https \
     --ssl-certificates=www-ssl-cert

3. For HTTPS, create a global forwarding rule to route incoming requests to the proxy.

   gcloud compute forwarding-rules create https-content-rule \
     --load-balancing-scheme=EXTERNAL \
     --network-tier=PREMIUM \
     --address=lb-ipv4-1 \
     --global \
     --target-https-proxy=https-lb-proxy \
     --ports=443

4. Optional: For HTTPS, create a global SSL policy and attach it to the HTTPS proxy.
   To create a global SSL policy:

   gcloud compute ssl-policies create my-ssl-policy \
     --profile MODERN \
     --min-tls-version 1.0

   To attach the SSL policy to the global target HTTPS proxy:

   gcloud compute target-https-proxies update https-lb-proxy \
     --ssl-policy my-ssl-policy

Set up an HTTP frontend

Skip this section for HTTPS load balancers.

1. For HTTP, create a target HTTP proxy to route requests to your URL map.

   gcloud compute target-http-proxies create http-lb-proxy \
     --url-map=web-map-http

2. For HTTP, create a global forwarding rule to route incoming requests to the proxy.

   gcloud compute forwarding-rules create http-content-rule \
     --load-balancing-scheme=EXTERNAL \
     --address=lb-ipv4-1 \
     --global \
     --target-http-proxy=http-lb-proxy \
     --ports=80

Terraform

1. To create the health check, use the google_compute_health_check resource.

    resource "google_compute_health_check" "default" {
     name               = "http-basic-check"
     check_interval_sec = 5
     healthy_threshold  = 2
     http_health_check {
       port               = 80
       port_specification = "USE_FIXED_PORT"
       proxy_header       = "NONE"
       request_path       = "/"
     }
     timeout_sec         = 5
     unhealthy_threshold = 2
   } 
   

2. To create the backend service, use the google_compute_backend_service resource.

   This example uses load_balancing_scheme="EXTERNAL_MANAGED" , which sets up a global external Application Load Balancer with advanced traffic management capability . To create a classic Application Load Balancer, make sure you change the load_balancing_scheme to EXTERNAL before running the script.

    resource "google_compute_backend_service" "default" {
     name                            = "web-backend-service"
     connection_draining_timeout_sec = 0
     health_checks                   = [google_compute_health_check.default.id]
     load_balancing_scheme           = "EXTERNAL_MANAGED"
     port_name                       = "http"
     protocol                        = "HTTP"
     session_affinity                = "NONE"
     timeout_sec                     = 30
     backend {
       group           = google_compute_instance_group_manager.default.instance_group
       balancing_mode  = "UTILIZATION"
       capacity_scaler = 1.0
     }
   } 
   

3. To create the URL map, use the google_compute_url_map resource.

    resource "google_compute_url_map" "default" {
     name            = "web-map-http"
     default_service = google_compute_backend_service.default.id
   } 
   

4. To create the target HTTP proxy, use the google_compute_target_http_proxy resource.

    resource "google_compute_target_http_proxy" "default" {
     name    = "http-lb-proxy"
     url_map = google_compute_url_map.default.id
   } 
   

5. To create the forwarding rule, use the google_compute_global_forwarding_rule resource.

   This example uses load_balancing_scheme="EXTERNAL_MANAGED" , which sets up a global external Application Load Balancer with advanced traffic management capability . To create a classic Application Load Balancer, make sure you change the load_balancing_scheme to EXTERNAL before running the script.

    resource "google_compute_global_forwarding_rule" "default" {
     name                  = "http-content-rule"
     ip_protocol           = "TCP"
     load_balancing_scheme = "EXTERNAL_MANAGED"
     port_range            = "80-80"
     target                = google_compute_target_http_proxy.default.id
     ip_address            = google_compute_global_address.default.id
   } 
   

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands .

Console

1. In the Google Cloud console, go to the Load balancing page.

   Go to Load balancing

2. Click the load balancer that you just created.

3. In the Backend section, confirm that the VMs are healthy. The Healthy column should be populated, indicating that both VMs are healthy ( 2/2 ). If you see otherwise, first try reloading the page. It can take a few moments for the Google Cloud console to indicate that the VMs are healthy. If the backends do not appear healthy after a few minutes, review the firewall configuration and the network tag assigned to your backend VMs.

4. For HTTPS, if you are using a Google-managed certificate, confirm that your certificate resource's status is ACTIVE. For more information, see Google-managed SSL certificate resource status .
5. After the Google Cloud console shows that the backend instances are healthy, you can test your load balancer using a web browser by going to https:// IP_ADDRESS (or http:// IP_ADDRESS ). Replace IP_ADDRESS with the load balancer's IP address .
6. If you used a self-signed certificate for testing HTTPS, your browser displays a warning. You must explicitly instruct your browser to accept a self-signed certificate.
7. Your browser should render a page with content showing the name of the instance that served the page, along with its zone (for example, Page served from: lb-backend-example-xxxx ). If your browser doesn't render this page, review the configuration settings in this guide.

gcloud

gcloud compute addresses describe lb-ipv4-1 \
   --format="get(address)" \
   --global

After a few minutes have passed, you can test the setup by running the following curl command.

curl http:// IP_ADDRESS 

-OR-

curl https:// HOSTNAME 

Console

Disable Cloud CDN for a single backend service

1. In the Google Cloud console, go to the Cloud CDNpage.

   Go to Cloud CDN

2. On the right side of the origin row, click Menu more_vert and then select edit Edit.

3. Clear the checkboxes of any backend services that you want to stop from using Cloud CDN.

4. Click Update.

Remove Cloud CDN for all backend services for an origin

1. In the Google Cloud console, go to the Cloud CDNpage.

   Go to Cloud CDN

2. On the right side of the origin row, click Menu more_vert and then select Remove.

3. To confirm, click Remove.

gcloud

gcloud compute backend-services update BACKEND_SERVICE_NAME 
\
    --no-enable-cdn