Google Cloud Platform Peered Dns Domain
This page shows how to write Terraform for Cloud Platform Peered Dns Domain and write them securely.
The Peered Dns Domain in Cloud Platform can be configured in Terraform with the resource name
google_service_networking_peered_dns_domain. 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:
project- (Optional) The producer project number. If not provided, the provider project is used.
name- (Required) Internal name used for the peered DNS domain.
network- (Required) The network in the consumer project.
dns_suffix- (Required) The DNS domain suffix of the peered DNS domain. Make sure to suffix with a
service- (Optional) Private service connection between service and consumer network, defaults to
In addition to the arguments listed above, the following computed attributes are exported:
id- an identifier for the resource with format
parent- an identifier for the resource with format
Explanation in Terraform Registry
Allows management of a single peered DNS domain for an existing Google Cloud Platform project. When using Google Cloud DNS to manage internal DNS, create peered DNS domains to make your DNS available to services like Google Cloud Build.
Tips: Best Practices for The Other Google Cloud Platform Resources
In addition to the google_project, Google Cloud Platform has the other resources that should be configured for security reasons. Please check some examples of those resources and precautions.
Ensure project-level default network creation is disabled
It is better to disable the auto-creation of default networks. The default network for a GCP project is usually configured coarsely, leaving the risk of unwanted access to resources in the network.