Anleitung und Anforderungen für Lab-Einrichtung
Schützen Sie Ihr Konto und Ihren Fortschritt. Verwenden Sie immer den privaten Modus und Lab-Anmeldedaten, um dieses Lab auszuführen.

Terraform Essentials: Firewall Policy

Lab 30 Minuten universal_currency_alt 1 Guthabenpunkt show_chart Einsteiger
info Dieses Lab kann KI-Tools enthalten, die den Lernprozess unterstützen.
Dieser Inhalt ist noch nicht für Mobilgeräte optimiert.
Die Lernumgebung funktioniert am besten, wenn Sie auf einem Computer über einen per E‑Mail gesendeten Link darauf zugreifen.

gem-terraform-fw-rule-create

Google Cloud self-paced labs logo

Activate Cloud Shell

Cloud Shell is a virtual machine that is loaded with development tools. It offers a persistent 5GB home directory and runs on the Google Cloud. Cloud Shell provides command-line access to your Google Cloud resources.

  1. Click Activate Cloud Shell Activate Cloud Shell icon at the top of the Google Cloud console.

When you are connected, you are already authenticated, and the project is set to your PROJECT_ID. The output contains a line that declares the PROJECT_ID for this session:

Your Cloud Platform project in this session is set to YOUR_PROJECT_ID

gcloud is the command-line tool for Google Cloud. It comes pre-installed on Cloud Shell and supports tab-completion.

  1. (Optional) You can list the active account name with this command:
gcloud auth list
  1. Click Authorize.

  2. Your output should now look like this:

Output:

ACTIVE: * ACCOUNT: student-01-xxxxxxxxxxxx@qwiklabs.net To set the active account, run: $ gcloud config set account `ACCOUNT`
  1. (Optional) You can list the project ID with this command:
gcloud config list project

Output:

[core] project = <project_ID>

Example output:

[core] project = qwiklabs-gcp-44776a13dea667a6 Note: For full documentation of gcloud, in Google Cloud, refer to the gcloud CLI overview guide.

Overview

This lab guides you through creating a firewall rule in Google Cloud using Terraform. You will learn how to define a firewall rule resource, configure its properties, and apply it to your Google Cloud project. This lab assumes you have a basic understanding of Google Cloud and Terraform.

Task 1. Configure Google Cloud Project

Before you begin, configure your Google Cloud project. This includes setting the project ID, region, and zone. Also, enable the IAM API.

  1. Set your Project ID:

    gcloud config set project {{{ project_0.project_id | "PROJECT_ID" }}} Note:
    This command sets your active project.
  2. Set your default region to

    gcloud config set compute/region {{{ project_0.default_region | "REGION" }}} Note:
    This command sets your active compute region.
  3. Set your default zone to

    gcloud config set compute/zone {{{ project_0.default_zone | "ZONE" }}} Note:
    This command sets your active compute zone.

Task 2. Create a Cloud Storage Bucket for Terraform State

Terraform uses a state file to track the resources it manages. For collaboration and persistence, it's best to store this state file in a remote backend like Google Cloud Storage (GCS).

  1. Create a Cloud Storage bucket. Ensure the bucket name is globally unique and prefixed with your project ID:

    gcloud storage buckets create gs://{{{ project_0.project_id | "PROJECT_ID" }}}-tf-state --project={{{ project_0.project_id | "PROJECT_ID" }}} --location={{{ project_0.default_region | "REGION" }}} --uniform-bucket-level-access Note:
    This command creates a Cloud Storage bucket in the specified region to store the Terraform state file.
  2. Enable versioning on the GCS bucket:

    gsutil versioning set on gs://{{{ project_0.project_id | "PROJECT_ID" }}}-tf-state Note:
    This enables versioning on the bucket.

Task 3. Defining the Firewall Rule in Terraform

Now, you will define the firewall rule using Terraform's configuration language.

  1. Create a new directory for your Terraform configuration files.

    mkdir terraform-firewall && cd $_ Note:
    This creates a new directory and changes the current directory to it.
  2. Create a file named firewall.tf and add the following code to define a firewall rule that allows SSH traffic (port 22) to instances with the tag ssh-allowed.

    resource "google_compute_firewall" "allow_ssh" { name = "allow-ssh-from-anywhere" network = "default" project = "{{{ project_0.project_id | "PROJECT_ID" }}}" allow { protocol = "tcp" ports = ["22"] } source_ranges = ["0.0.0.0/0"] target_tags = ["ssh-allowed"] } Note:
    This configuration creates a firewall rule named `allow-ssh-from-anywhere` that allows TCP traffic on port 22 from any source IP address (0.0.0.0/0) to instances tagged with `ssh-allowed`.
  3. Create a variables.tf file to define variables used in firewall.tf and main.tf.

    variable "project_id" { type = string default = "{{{ project_0.project_id | "PROJECT_ID" }}}" } variable "bucket_name" { type = string default = "{{{ project_0.project_id | "PROJECT_ID" }}}-tf-state" } variable "region" { type = string default = "{{{ project_0.default_region | "REGION" }}}" } Note:
    This creates variables for the project ID, bucket name, and region.
  4. Create an outputs.tf file to output the firewall rule name.

    output "firewall_name" { value = google_compute_firewall.allow_ssh.name } Note:
    This outputs the name of the firewall rule.

Task 4. Applying the Terraform Configuration

Now you will apply the Terraform configuration to create the firewall rule in your Google Cloud project.

  1. Run terraform init to enable Terraform.

    terraform init Note:
    This command downloads the Terraform provider for the configuration files.
  2. Run terraform plan to preview the changes Terraform will make.

    terraform plan Note:
    This command shows the planned changes without applying them.
  3. Run terraform apply to apply the configuration and create the firewall rule.

    terraform apply Note:
    Type `yes` when prompted to confirm the changes.
  4. Verify that the firewall rule has been created in the Google Cloud Console.

    Navigate to **VPC network > Firewall** in the Google Cloud Console and verify the existence of the `allow-ssh-from-anywhere` firewall rule. Note:
    This is a manual verification step.

Task 5. Cleaning Up Resources

To avoid incurring unnecessary costs, destroy the resources created in this lab.

  1. Run terraform destroy to remove the firewall rule.

    terraform destroy Note:
    Type `yes` when prompted to confirm the destruction.

Congratulations!

You have successfully created and destroyed a firewall rule in Google Cloud using Terraform. You have learned how to define firewall rules as code, manage their properties, and apply them to your Google Cloud project. This approach enables you to automate and manage your infrastructure in a consistent and repeatable manner.

Additional Resources

Manual Last Updated Jul 22, 2025

Lab Last Tested Jul 22, 2025

Vorbereitung

  1. Labs erstellen ein Google Cloud-Projekt und Ressourcen für einen bestimmten Zeitraum
  2. Labs haben ein Zeitlimit und keine Pausenfunktion. Wenn Sie das Lab beenden, müssen Sie von vorne beginnen.
  3. Klicken Sie links oben auf dem Bildschirm auf Lab starten, um zu beginnen

Privates Surfen verwenden

  1. Kopieren Sie den bereitgestellten Nutzernamen und das Passwort für das Lab
  2. Klicken Sie im privaten Modus auf Konsole öffnen

In der Konsole anmelden

  1. Melden Sie sich mit Ihren Lab-Anmeldedaten an. Wenn Sie andere Anmeldedaten verwenden, kann dies zu Fehlern führen oder es fallen Kosten an.
  2. Akzeptieren Sie die Nutzungsbedingungen und überspringen Sie die Seite zur Wiederherstellung der Ressourcen
  3. Klicken Sie erst auf Lab beenden, wenn Sie das Lab abgeschlossen haben oder es neu starten möchten. Andernfalls werden Ihre bisherige Arbeit und das Projekt gelöscht.

Diese Inhalte sind derzeit nicht verfügbar

Bei Verfügbarkeit des Labs benachrichtigen wir Sie per E-Mail

Sehr gut!

Bei Verfügbarkeit kontaktieren wir Sie per E-Mail

Es ist immer nur ein Lab möglich

Bestätigen Sie, dass Sie alle vorhandenen Labs beenden und dieses Lab starten möchten

Privates Surfen für das Lab verwenden

Am besten führen Sie dieses Lab in einem Inkognito- oder privaten Browserfenster aus. So vermeiden Sie Konflikte zwischen Ihrem privaten Konto und dem Teilnehmerkonto, die zusätzliche Kosten für Ihr privates Konto verursachen könnten.