This guide helps you understand, deploy, and use theLoad balanced managed VMs Jump Start Solution, which demonstrates how to create a virtual machine clusterwith a load balancer, make VMs globally available, and instantaneously managetraffic.

You can deploy the solution to help you do the following:

• Create redundant versions of an application that is hosted on multiple VMs.
• Automatically scale the number of VMs to meet user demand.
• Automatically heal failing copies of an application.
• Distribute traffic to multiple locations.
• Migrate an existing load-balanced implementation to the cloud with minormodifications (lift and shift).

This document is intended for developers who have some background with loadbalancers. It assumes that you're familiar with basic cloud concepts, though notnecessarily Google Cloud. Experience with Terraform is helpful.

Objectives

This solution guide helps you do the following:

• Learn about load balancer features and configurations, includingautoscaling and autohealing.
• Deploy two or more VMs that can potentially serve an application, and use aload balancer to manage traffic.
• Modify the deployment location and the number of nodes.
• Understand load balancer design considerations.

Architecture

This solution deploys a group of VMs that are managed by a load balancer. Thefollowing diagram shows the architecture of the Google Cloud resources:

Request flow

The following is the request processing flow of the topology that the load balanced managed VMssolution deploys. The steps in the flow are numbered as shown in thepreceding architecture diagram.

1. The user makes a request to the application, which is deployed onCompute Engine. The request first lands on Cloud Load Balancing.

2. Cloud Load Balancing distributes traffic to the Compute Engine managedinstance group (MIG), which scales the number of instances based on trafficvolume.

Components and configuration

The architecture includes the following components:

Cost

For an estimate of the cost of the Google Cloud resources that theload balanced managed VMs solution uses, see the precalculated estimate in theGoogle Cloud Pricing Calculator.

Use the estimate as a starting point to calculate the cost of your deployment.You can modify the estimate to reflect any configuration changes that you planto make for the resources that are used in the solution.

The precalculated estimate is based on assumptions for certain factors,including the following:

• The Google Cloud locations where the resources are deployed.
• The amount of time that the resources are used.

Deploy the solution

This section guides you through the process of deploying the solution.

Create or choose a Google Cloud project

When you deploy the solution, you choose theGoogle Cloud project where the resources are deployed. You can either create a new project or use anexisting project for the deployment.

If you want to create a new project, do sobefore you begin the deployment.Using a new project can help avoid conflicts with previously provisionedresources, such as resources that are used for production workloads.

To create a project, complete the following steps:

1. Ensure that you have the Project Creator IAM role (roles/resourcemanager.projectCreator).Learn how to grant roles.

2. In the Google Cloud console, go to the project selector page.

   Go to project selector

3. ClickCreate project.

4. Name your project. Make a note of your generated project ID.

5. Edit the other fields as needed.

6. ClickCreate.

Get the required IAM permissions

To start the deployment process, you need the Identity and Access Management (IAM)permissions that are listed in the following table.

If you created a new project for this solution, then you have theroles/ownerbasic role in that project and have all the necessary permissions. If you don't have theroles/owner role, then ask your administrator to grant these permissions (orthe roles that include these permissions) to you.

About temporary service account permissions

If you start the deployment process through the console, Google creates aservice account to deploy the solution on your behalf (and to delete the deployment later if youchoose). This service account is assigned certain IAM permissionstemporarily; that is, the permissions are revoked automatically after thesolution deployment and deletion operations are completed. Google recommendsthat after you delete the deployment, you delete the service account, asdescribed later in this guide.

Choose a deployment method

To help you deploy this solution with minimal effort, a Terraform configurationis provided in GitHub. The Terraform configuration defines all theGoogle Cloud resources that are required for the solution.

You can deploy the solution by using one of the following methods:

• Through the console: Use this method if you wantto try the solution with the default configuration and see how it works.Cloud Build deploys all the resources that are required for thesolution. When you no longer need the deployed solution, you can delete itthrough the console. Any resources that you create afteryou deploy the solution might need to be deleted separately.

  To use this deployment method, follow the instructions inDeploy through the console.

• Using the Terraform CLI: Use this method if you want to customize thesolution or if you want to automate the provisioning and management of theresources by using the infrastructure as code (IaC) approach. Download theTerraform configuration from GitHub, optionally customize the code asnecessary, and then deploy the solution by using the Terraform CLI. Afteryou deploy the solution, you can continue to use Terraform to manage thesolution.

  To use this deployment method, follow the instructions inDeploy using the Terraform CLI.

Deploy through the console

Complete the following steps to deploy the preconfigured solution.

1. In the Google Cloud Jump Start Solutions catalog, go to theLoad balanced managed VMs page.

2. Review the information that's provided on the page, such as the estimatedcost of the solution and the estimated deployment time.

3. When you're ready to start deploying the solution, clickDeploy.

   A step-by-step interactive guide is displayed.

4. Complete the steps in the interactive guide:

   1. Select a project where you want to create resources that are deployed bythe solution and clickContinue.

   2. In theDeployment name field, type a name you have not previouslyused in this project.

   3. Optionally, add an identifying label to the deployment. (Solutionindicator and deployment name labels are automatically added.) You canuse labels to organize resources by criteria such as cost center,environment, or state.

      For more information about labels, seeCreating and managinglabels

   4. From theRegion andZone drop-down lists, select the desiredlocation where resources will be created.

      For more information about regions and zones, seeGeography andregions

   5. In theNumber of nodes field, type the minimum number of virtualmachines in the MIG. The load balancer is configured to scale the numberof virtual machines based on user traffic volume. For this deployment,you can use the default value of 2 nodes.

      For more information about creating multiple VMs, seeBasic scenarios forcreating managed instance groups(MIGs).

   6. ClickContinue.

5. When you've finished specifying options, clickDeploy.

   TheSolution deployments page is displayed. TheStatus field on thispage showsDeploying.

6. Wait for the solution to be deployed.

   If the deployment fails, theStatus field showsFailed. You can usethe Cloud Build log to diagnose the errors. For more information,seeErrors when deploying fromthe console.

   After the deployment is completed, theStatus field changes toDeployed.

7. To view the Google Cloud resources that are deployed and theirconfiguration, take an interactive tour.

   Start the tour

You deployed the example solution, viewed the load balancer configuration, andviewed the application site that is served by VMs. To learn about designrecommendations to address your organization's unique load balancing needs, seeDesignrecommendations.

When you no longer need the solution, you can delete the deployment to avoidcontinued billing for the Google Cloud resources. For more information,seeDelete the deployment.

Deploy using the Terraform CLI

This section describes how you can customize the solution or automate theprovisioning and management of the solution by using the Terraform CLI.Solutions that you deploy by using the Terraform CLI are not displayed in theSolution deployments page in the Google Cloud console.

Set up the Terraform client

You can run Terraform either in Cloud Shell or on your local host. Thisguide describes how to run Terraform in Cloud Shell, which hasTerraform preinstalled and configured to authenticate with Google Cloud.

The Terraform code for this solution is available in a GitHub repository.

1. Clone the GitHub repository to Cloud Shell.

   

   A prompt is displayed to confirm downloading the GitHub repository toCloud Shell.

2. ClickConfirm.

   Cloud Shell is launched in a separate browser tab, and theTerraform code is downloaded to the$HOME/cloudshell_open directory ofyour Cloud Shell environment.

3. In Cloud Shell, check whether the current working directory is$HOME/cloudshell_open/terraform-google-load-balanced-vms/. This is thedirectory that contains the Terraform configuration files for the solution.If you need to change to that directory, run the following command:

   cd$HOME/cloudshell_open/terraform-google-load-balanced-vms/

4. Initialize Terraform by running the following command:

   terraform init

   Wait until you see the following message:

   Terraform has been successfully initialized!

Configure the Terraform variables

The Terraform code that you downloaded includes variables that you can use tocustomize the deployment based on your requirements. For example, you canspecify the Google Cloud project and theregion where you want the solution to bedeployed.

1. Make sure that the current working directory is$HOME/cloudshell_open/terraform-google-load-balanced-vms/. If itisn't, go to that directory.

2. In the same directory, create a text file namedterraform.tfvars.

3. In theterraform.tfvars file, copy the following code snippet, and setvalues for the required variables.

   • Follow the instructions that are provided as comments in the codesnippet.
   • This code snippet includes only the variables for which youmust setvalues. The Terraform configuration includes other variables that havedefault values. To review all the variables and the default values, seethevariables.tf file that's available in the$HOME/cloudshell_open/terraform-google-load-balanced-vms/ directory.
   • Make sure that each value that you set in theterraform.tfvars filematches the variabletype as declared in thevariables.tf file. For example, if the type that'sdefined for a variable in thevariables.tf file isbool, then youmust specifytrue orfalse as the value of that variable in theterraform.tfvars file.

   # This is an example of the terraform.tfvars file.# The values that you set in this file must match the variable types, as declared in variables.tf.# The values in this file override any defaults in variables.tf.# ID of the project in which you want to deploy the solutionproject_id="PROJECT_ID"# Google Cloud region where you want to deploy the solution# Example: us-central1region="REGION"# Google Cloud zone where you want to deploy the solution# Example: us-central1-azone="ZONE"# The number of Cloud Compute nodes you want to deploy (minimum of 2)# Example: 2nodes="NODES"# The name of this particular deployment, will get added as a prefix to most resources# Example: load-balanced-vmsdeployment_name="DEPLOYMENT_NAME"# The following variables have default values. You can set your own values or remove them to accept the defaults# A set of key/value label pairs to assign to the resources that are deployed by this solution# Example: {"team"="monitoring", "environment"="test"}labels={"KEY1"="VALUE1",..."KEYn"="VALUEn"}# Whether to enable underlying APIs# Example: trueenable_apis="ENABLE_APIS"# If you want to deploy to an existing network, enter your network details in the following variables:# VPC network to deploy VMs in. A VPC will be created if not specifiednetwork_id="NETWORK_ID"# Subnetwork to deploy VMs in. A Subnetwork will be created if not specifiedsubnet_self_link="SUBNET_SELF_LINK"#Shared VPC host project ID, if a Shared VPC is provided via network_idnetwork_project_id="NETWORK_PROJECT_ID"

For information about the values that you can assign to the required variables,see the following:

• project_id,region, andzone are required. For information aboutthe values that you can use for these variables, see the following:
  • Identifyingprojects
  • Available regions andzones
• The other variables have default values. You might change some of them(for example,deployment_name andlabels).

Validate and review the Terraform configuration

1. Make sure that the current working directory is$HOME/cloudshell_open/terraform-google-load-balanced-vms/. If itisn't, go to that directory.

2. Verify that the Terraform configuration has no errors:

   terraform validate

   If the command returns any errors, make the required corrections in theconfiguration and then run theterraform validate command again. Repeatthis step until the command returns the following message:

   Success! The configuration is valid.

3. Review the resources that are defined in the configuration:

   terraform plan

4. If you didn't create theterraform.tfvars file asdescribed earlier, Terraform prompts you to enter values for the variablesthat don't have default values.Enter the required values.

   The output of theterraform plan command is a list of the resources thatTerraform provisions when you apply the configuration.

   If you want to make any changes, edit the configuration and then run theterraform validate andterraform plan commands again.

Provision the resources

When no further changes are necessary in the Terraform configuration, deploythe resources.

1. Make sure that the current working directory is$HOME/cloudshell_open/terraform-google-load-balanced-vms/. If itisn't, go to that directory.

2. Apply the Terraform configuration:

   terraform apply

3. If you didn't create theterraform.tfvars file asdescribed earlier, Terraform prompts you to enter values for the variablesthat don't have default values.Enter the required values.

   Terraform displays a list of the resources that will be created.

4. When you're prompted to perform the actions, enteryes.

   Terraform displays messages showing the progress of the deployment.

   If the deployment can't be completed, Terraform displays the errors thatcaused the failure. Review the error messages and update the configurationto fix the errors. Then run theterraform apply command again. For helpwith troubleshooting Terraform errors, seeErrors when deploying the solution using the Terraform CLI.

   After all the resources are created, Terraform displays the followingmessage:

   Apply complete!

   The following additional output is displayed:

   Outputs:console_page_for_load_balancer = "https://console.cloud.google.com/net-services/loadbalancing/details/http/<DEPLOYMENT_NAME>-lb-url-map?project=<PROJECT_ID>"load_balancer_endpoint = "<VALUE>"

5. To view the Google Cloud resources that are deployed and theirconfiguration, take an interactive tour.

   Start the tour

When you no longer need the solution, you can delete the deployment to avoidcontinued billing for the Google Cloud resources. For more information,seeDelete the deployment.

Design recommendations

This section provides recommendations for using the load balanced managed VMssolution to develop an architecture that meets your requirements for security,reliability, cost, and performance.

For a high level overview of best practices, seePatterns for scalable andresilientapps .

Security

Implement the recommendations in the following guides to help secure yourarchitecture:

• Implement security by design
• Implement shift-left security

For example, your architecture might have the following requirements:

• You might require security features that are only available on a specificoperating system. For more information, seeOperating systemdetails

• You might need to fine-tune subnet details in a custom network. For moreinformation about creating networks, seeCreate and manage VPCnetworks

Reliability

Use the following guidelines to create reliable services:

• Designing resilient systems on Compute Engine
• Using load balancing for highly available applications

For example, you might fine-tune your VM health check details to ensure thattiming is in line with your organization's commitments to customers. For moreinformation about configuring health checks, seeSet up an application healthcheck andautohealing .

Performance

Optimize performance by adhering to the best practices described inGoogle Cloud Well-Architected Framework: Performance optimization.

For example, the application that you deploy might require specific hardwarerequirements. For more information about configuring disk, memory, and CPUdetails on Compute Engine, seeMachine families resource and comparisonguide .

Cost

Use the best practices in the following guide to optimize the cost of your workflows:Google Cloud Well-Architected Framework: Cost optimization

For example, you might set the maximum number of nodes in your MIG based on amaximum cost you would prefer to incur for Compute Engine instances. For moreinformation about setting the target size of the autoscaler, seeTurning off orrestricting anautoscaler.

Note the following:

• Before you make any design changes, assess the cost impact and considerpotential trade-offs with other features. You can assess the cost impact ofdesign changes by using theGoogle Cloud Pricing Calculator.
• To implement design changes in the solution, you need expertise inTerraform coding and advanced knowledge of the Google Cloud servicesthat are used in the solution.
• If you modify the Google-provided Terraform configuration and if you thenexperience errors, create issues inGitHub.GitHub issues are reviewed on a best-effort basis and are not intended forgeneral usage questions.
• For more information about designing and setting up production-gradeenvironments in Google Cloud, seeLanding zone design in Google Cloud andGoogle Cloud setup checklist.

Delete the deployment

When you no longer need the solution, to avoid continued billing for theresources that you created in this solution, delete all the resources.

Delete through the console

Use this procedure if you deployed the solution throughthe console.

1. In the Google Cloud console, go to theSolution deployments page.

   Go to Solution deployments

2. Select the project that contains the deployment that you want to delete.

3. Locate the deployment that you want to delete.

4. In the row for the deployment, clickmore_vertActionsand then selectDelete.

   You might need to scroll to seeActions in the row.

5. Enter the name of the deployment and then clickConfirm.

   TheStatus field showsDeleting.

   If the deletion fails, see the troubleshooting guidance inError when deleting a deployment.

When you no longer need the Google Cloud project that you used for the solution, youcan delete the project. For more information, seeOptional: Delete the project.

Delete using the Terraform CLI

Use this procedure if you deployed the solution by using the Terraform CLI.

1. In Cloud Shell, make sure that the current working directory is$HOME/cloudshell_open/terraform-google-load-balanced-vms/. If itisn't, go to that directory.

2. Remove the resources that were provisioned by Terraform:

   terraform destroy

   Terraform displays a list of the resources that will be destroyed.

3. When you're prompted to perform the actions, enteryes.

   Terraform displays messages showing the progress. After all the resourcesare deleted, Terraform displays the following message:

   Destroy complete!

   If the deletion fails, see the troubleshooting guidance inError when deleting a deployment.

When you no longer need the Google Cloud project that you used for the solution, youcan delete the project. For more information, seeOptional: Delete the project.

Optional: Delete the project

If you deployed the solution in a new Google Cloud project, and if you no longerneed the project, then delete it by completing the following steps:

1. In the Google Cloud console, go to theManage resources page.

   Go to Manage resources

2. In the project list, select the project that you want to delete, and then clickDelete.
3. At the prompt, type the project ID, and then clickShut down.

If you decide to retain the project, then delete the service account that wascreated for this solution, as described in the next section.

Optional: Delete the service account

If you deleted the project that you used for the solution, then skip thissection.

As mentioned earlier in this guide, when you deployed the solution, a serviceaccount was created on your behalf. The service account was assigned certainIAM permissionstemporarily; that is, the permissions wererevoked automatically after the solution deployment and deletion operations werecompleted, but the service account isn't deleted. Google recommends thatyou delete this service account.

• If you deployed the solution through the Google Cloud console, go to theSolution deployments page. (If you're already on that page, refresh the browser.) A process istriggered in the background to delete the service account. No further actionis necessary.

• If you deployed the solution by using the Terraform CLI, complete thefollowing steps:

  1. In the Google Cloud console, go to theService accounts page.

     Go to Service accounts

  2. Select the project that you used for the solution.

  3. Select the service account that you want to delete.

     The email ID of the service account that was created for the solution isin the following format:

     goog-sc-DEPLOYMENT_NAME-NNN@PROJECT_ID.iam.gserviceaccount.com

     The email ID contains the following values:

     • DEPLOYMENT_NAME: the name of the deployment.
     • NNN: a random 3-digit number.
     • PROJECT_ID: the ID of the project in which youdeployed the solution.

  4. ClickDelete.

Troubleshoot errors

The actions that you can take to diagnose and resolve errors depend on thedeployment method and the complexity of the error.

Errors when deploying through the console

If the deployment fails when you use the console, do thefollowing:

1. Go to theSolution deployments page.

   If the deployment failed, theStatus field showsFailed.

2. View the details of the errors that caused the failure:

   1. In the row for the deployment, clickmore_vertActions.

      You might need to scroll to seeActions in the row.

   2. SelectView Cloud Build logs.

3. Review the Cloud Build log and take appropriate action to resolvethe issue that caused the failure.

Errors when deploying using the Terraform CLI

If the deployment fails when you use Terraform, the output of theterraformapply command includes error messages that you can review to diagnose theproblem.

The examples in the following sections show deployment errors that you mightencounter when you use Terraform.

API not enabled error

If you create a project and then immediately attempt to deploy the solution inthe new project, the deployment might fail with an error like the following:

Error: Error creating Network: googleapi: Error 403: Compute Engine API has notbeen used in projectPROJECT_ID before or it is disabled. Enable it by visitinghttps://console.developers.google.com/apis/api/compute.googleapis.com/overview?project=PROJECT_IDthen retry. If you enabled this API recently, wait a few minutes for the actionto propagate to our systems and retry.

If this error occurs, wait a few minutes and then run theterraform applycommand again.

Cannot assign requested address error

When you run theterraform apply command, acannot assign requested addresserror might occur, with a message like the following:

Error: Error creating service account: Post "https://iam.googleapis.com/v1/projects/PROJECT_ID/serviceAccounts: dial tcp [2001:db8:ffff:ffff::5f]:443: connect: cannot assign requested address

If this error occurs, run theterraform apply command again.

Error when deleting a deployment

In certain cases, attempts to delete a deployment might fail:

• After deploying a solution through the console, if youchange any resource that was provisioned by the solution, and if you then tryto delete the deployment, the deletion might fail. TheStatus field on theSolution deployments page showsFailed, and theCloud Build log shows the cause of the error.
• After deploying a solution by using the Terraform CLI, if you change anyresource by using a non-Terraform interface (for example,the console), and if you then try to delete the deployment,the deletion might fail. The messages in the output of theterraform destroycommand show the cause of the error.

Review the error logs and messages, identify and delete the resources thatcaused the error, and then try deleting the deployment again.

If a console-based deployment doesn't get deleted and if you can'tdiagnose the error by using the Cloud Build log, then you can deletethe deployment by using the Terraform CLI, as described in the next section.

Delete a console-based deployment by using the Terraform CLI

This section describes how to delete a console-based deployment iferrors occur when you try to delete it through the console. Inthis approach, you download the Terraform configuration for the deployment thatyou want to delete and then use the Terraform CLI to delete the deployment.

1. Identify the region where the deployment's Terraform code, logs, and otherdata are stored. This region might be different from the region thatyou selected while deploying the solution.

   1. In the Google Cloud console, go to theSolution deploymentspage.

      Go to Solution deployments

   2. Select the project that contains the deployment that you want to delete.

   3. In the list of deployments, identify the row for the deployment that youwant to delete.

   4. Clickexpand_moreView all rowcontent.

   5. In theLocation column, note thesecond location, as highlightedin the following example:

      

2. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, aCloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

3. Create environment variables for the project ID, region, and name ofthe deployment that you want to delete:

   exportREGION="REGION"exportPROJECT_ID="PROJECT_ID"exportDEPLOYMENT_NAME="DEPLOYMENT_NAME"

   In these commands, replace the following:

   • REGION: the location that you noted earlier inthis procedure.
   • PROJECT_ID: the ID of the project where youdeployed the solution.
   • DEPLOYMENT_NAME: the name of the deploymentthat you want to delete.

4. Get the ID of the latest revision of the deployment that you wantto delete:

   exportREVISION_ID=$(curl\-H"Authorization: Bearer $(gcloud auth print-access-token)"\-H"Content-Type: application/json"\"https://config.googleapis.com/v1alpha2/projects/${PROJECT_ID}/locations/${REGION}/deployments/${DEPLOYMENT_NAME}"\|jq.latestRevision-r)echo$REVISION_ID

   The output is similar to the following:

   projects/PROJECT_ID/locations/REGION/deployments/DEPLOYMENT_NAME/revisions/r-0

5. Get the Cloud Storage location of the Terraform configuration forthe deployment:

   exportCONTENT_PATH=$(curl\-H"Authorization: Bearer $(gcloud auth print-access-token)"\-H"Content-Type: application/json"\"https://config.googleapis.com/v1alpha2/${REVISION_ID}"\|jq.applyResults.content-r)echo$CONTENT_PATH

   The following is an example of the output of this command:

   gs://PROJECT_ID-REGION-blueprint-config/DEPLOYMENT_NAME/r-0/apply_results/content

6. Download the Terraform configuration from Cloud Storage toCloud Shell:

   gcloud storage cp $CONTENT_PATH $HOME --recursivecd $HOME/content/

   Wait until theOperation completed message is displayed, as shown inthe following example:

   Operation completed over 45 objects/268.5 KiB

7. Initialize Terraform:

   terraform init

   Wait until you see the following message:

   Terraform has been successfully initialized!

8. Remove the deployed resources:

   terraform destroy

   Terraform displays a list of the resources that will be destroyed.

   If any warnings about undeclared variables are displayed, ignore thewarnings.

9. When you're prompted to perform the actions, enteryes.

   Terraform displays messages showing the progress. After all theresources are deleted, Terraform displays the following message:

   Destroy complete!

10. Delete the deployment artifact:

    curl-XDELETE\-H"Authorization:Bearer$(gcloudauthprint-access-token)"\-H"Content-Type:application/json"\"https://config.googleapis.com/v1alpha2/projects/${PROJECT_ID}/locations/${REGION}/deployments/${DEPLOYMENT_NAME}?force=true&delete_policy=abandon"

11. Wait a few seconds and then verify that the deployment artifact wasdeleted:

    curl-H"Authorization:Bearer$(gcloudauthprint-access-token)"\-H"Content-Type:application/json"\"https://config.googleapis.com/v1alpha2/projects/${PROJECT_ID}/locations/${REGION}/deployments/${DEPLOYMENT_NAME}"\|jq.error.message

    If the output showsnull, wait a few seconds and then run the commandagain.

    After the deployment artifact is deleted, a message as shown in thefollowing example is displayed:

    Resource 'projects/PROJECT_ID/locations/REGION/deployments/DEPLOYMENT_NAME' was not found

Submit feedback

Jump Start Solutions are for informational purposes only and are not officiallysupported products. Google may change or remove solutions without notice.

To troubleshoot errors, review the Cloud Build logs and the Terraformoutput.

To submit feedback, do the following:

• For documentation, in-console tutorials, or the solution, usetheSend Feedback button on the page.

• For unmodified Terraform code, create issues in theGitHub repository.GitHub issues are reviewed on a best-effort basis and are not intended forgeneral usage questions.

• For issues with the products that are used in the solution, contactCloud Customer Care.

What's next

Review the following documentation to learn about architectural and operationalbest practices for products used in this solution:

• Patterns for scalable and resilient apps
• Compute Engine: Create and start a VM
• Compute Engine: Create custom images
• Compute Engine: Create instance templates
• Compute Engine: Basic scenarios for creating managed instance groups(MIGs)