Google Compute Engine Firewall Policy
This page shows how to write Terraform for Compute Engine Firewall Policy and write them securely.
The Firewall Policy in Compute Engine can be configured in Terraform with the resource name
google_compute_firewall_policy. The following sections describe how to use the resource and its parameters.
Example Usage from GitHub
An example could not be found in GitHub.
The following arguments are supported:
parent- (Required) The parent of the firewall policy.
short_name- (Required) User-provided name of the Organization firewall policy. The name should be unique in the organization in which the firewall policy is created. The name must be 1-63 characters long, and comply with RFC1035. Specifically, the name must be 1-63 characters long and match the regular expression a-z? which means the first character must be a lowercase letter, and all following characters must be a dash, lowercase letter, or digit, except the last character, which cannot be a dash.
description- (Optional) An optional description of this resource. Provide this property when you create the resource.
In addition to the arguments listed above, the following computed attributes are exported:
id- an identifier for the resource with format
creation_timestamp- Creation timestamp in RFC3339 text format.
fingerprint- Fingerprint of the resource. This field is used internally during updates of this resource.
id- The unique identifier for the resource. This identifier is defined by the server.
name- Name of the resource. It is a numeric ID allocated by GCP which uniquely identifies the Firewall Policy.
rule_tuple_count- Total count of all firewall policy rule tuples. A firewall policy can not exceed a set number of tuples.
self_link- Server-defined URL for the resource.
self_link_with_id- Server-defined URL for this resource with the resource id.
Explanation in Terraform Registry
Hierarchical firewall policy rules let you create and enforce a consistent firewall policy across your organization. Rules can explicitly allow or deny connections or delegate evaluation to lower level policies. Policies can be created within organizations or folders. This resource should be generally be used with
google_compute_firewall_policy_ruleFor more information see the official 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.