Google Compute Engine Project Default Network Tier

This page shows how to write Terraform for Compute Engine Project Default Network Tier and write them securely.

google_compute_project_default_network_tier (Terraform)

The Project Default Network Tier in Compute Engine can be configured in Terraform with the resource name google_compute_project_default_network_tier. The following sections describe 5 examples of how to use the resource and its parameters.

Example Usage from GitHub
resource "google_compute_project_default_network_tier" "default" {
  network_tier = "STANDARD"
resource "google_compute_project_default_network_tier" "default" {
  network_tier = var.network_tier

data "google_compute_network" "default" {
  name = "default"
resource "google_compute_project_default_network_tier" "default" {
    network_tier            = "PREMIUM"
resource "google_compute_project_default_network_tier" "default_network_tier" {
  network_tier = "PREMIUM"
  project      = var.config_project_id
resource "google_compute_project_default_network_tier" "default" {
    network_tier            = "PREMIUM"

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).


The default network tier to be configured for the project. This field can take the following values: PREMIUM or STANDARD.

The ID of the project in which the resource belongs. If it is not provided, the provider project is used.

Explanation in Terraform Registry

Configures the Google Compute Engine Default Network Tier for a project. For more information, see, the Project API documentation.

Tips: Best Practices for The Other Google Compute Engine Resources

In addition to the google_compute_disk, Google Compute Engine has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.



Ensure the encryption key for your GCE disk is stored securely

It is better to store the encryption key for your GCE disk securely. Secret Manager could be used instead.



Ensure your VPC firewall blocks unwanted outbound traffic

It is better to block unwanted outbound traffic not to expose resources in the VPC to unwanted attacks.



Ensure appropriate service account is assigned to your GCE instance

It is better to create a custom service account for the instance and assign it.



Ensure OS login for your GCE instances is enabled at project level

It is better to enable OS login for your GCE instances. Enabling OS login ensures that SSH keys used to connect to instances are mapped with IAM users, allowing centralized and automated SSH key management.



Ensure to use modern TLS protocols

It's better to adopt TLS v1.2+ instead of outdated TLS protocols.



Ensure VPC flow logging is enabled

It is better to enable VPC flow logging. VPC flow logging allows us to audit traffic in your network.

Review your Google Compute Engine settings

In addition to the above, there are other security points you should be aware of making sure that your .tf files are protected in Shisho Cloud.

Frequently asked questions

What is Google Compute Engine Project Default Network Tier?

Google Compute Engine Project Default Network Tier is a resource for Compute Engine of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Compute Engine Project Default Network Tier?

For Terraform, the de-py/Terraform-Ansible-Demo, mmcloughlin/goperf and DaniloBNascimento/gcp-foundation-tf source code examples are useful. See the Terraform Example section for further details.