Google Compute Engine Instance Group Named Port
This page shows how to write Terraform for Compute Engine Instance Group Named Port and write them securely.
google_compute_instance_group_named_port (Terraform)
The Instance Group Named Port in Compute Engine can be configured in Terraform with the resource name google_compute_instance_group_named_port
. The following sections describe 5 examples of how to use the resource and its parameters.
Example Usage from GitHub
resource "google_compute_instance_group_named_port" "named_port_0" {
group = google_container_cluster.gke_cluster.instance_group_urls[0]
name = "http"
port = 30000
}
resource "google_compute_instance_group_named_port" "http_port" {
group = google_compute_instance_group_manager.jack_manager.name
zone = data.google_compute_zones.available.names.0
name = "http"
port = 80
resource "google_compute_instance_group_named_port" "http_port" {
group = google_compute_instance_group_manager.jack_manager.name
zone = data.google_compute_zones.available.names.0
name = "http"
port = 80
resource "google_compute_instance_group_named_port" "http" {
for_each = data.google_compute_instance_group.instance_groups
group = each.value.self_link
zone = each.value.zone
name = "http"
port = 80
resource "google_compute_instance_group_named_port" "this" {
group = var.group
name = var.name
port = var.port
project = var.project
zone = var.zone
Parameters
-
group
required - string
The name of the instance group.
The name for this named port. The name must be 1-63 characters long, and comply with RFC1035.
-
port
required - number
The port number, which can be a value between 1 and 65535.
The zone of the instance group.
Explanation in Terraform Registry
Mange the named ports setting for a managed instance group without managing the group as whole. This resource is primarily intended for use with GKE-generated groups that shouldn't otherwise be managed by other tools. To get more information about InstanceGroupNamedPort, see:
- API documentation
- How-to Guides
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.
Frequently asked questions
What is Google Compute Engine Instance Group Named Port?
Google Compute Engine Instance Group Named Port 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 Instance Group Named Port?
For Terraform, the Escoto/GKE-Ghost-Deployment, MehmetIron/infra-bootcamp and husnusensoy/infra-bootcamp source code examples are useful. See the Terraform Example section for further details.