Google Compute Engine Project Metadata Item

google_compute_project_metadata_item (Terraform)

The Project Metadata Item in Compute Engine can be configured in Terraform with the resource name google_compute_project_metadata_item. The following sections describe 2 examples of how to use the resource and its parameters.

Example Usage from GitHub

jonpulsifer/nawl

resource "google_compute_project_metadata_item" "oslogin" {
  for_each = var.compute ? toset([var.project_id]) : []
  project  = each.key
  key      = "enable-oslogin"
  value    = "TRUE"
  depends_on = [

jonpulsifer/terraform-modules

resource "google_compute_project_metadata_item" "oslogin" {
  for_each = var.compute ? toset([var.project_id]) : []
  project  = each.key
  key      = "enable-oslogin"
  value    = "TRUE"
  depends_on = [

Parameters

• id optional computed - string
• key required - string

The metadata key to set.

• project optional computed - string

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

• value required - string

The value to set for the given metadata key.

• timeouts single block
  • create optional - string
  • delete optional - string
  • update optional - string

Explanation in Terraform Registry

Manages a single key/value pair on metadata common to all instances for a project in GCE. Using google_compute_project_metadata_item lets you manage a single key/value setting in Terraform rather than the entire project metadata map.

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.

google_compute_disk

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.

google_compute_firewall

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.

google_compute_instance

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.

google_compute_project_metadata

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.

google_compute_ssl_policy

Ensure to use modern TLS protocols

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

google_compute_subnetwork

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.