Google Compute Engine Project Usage Export Bucket
This page shows how to write Terraform for Compute Engine Project Usage Export Bucket and write them securely.
google_project_usage_export_bucket (Terraform)
The Project Usage Export Bucket in Compute Engine can be configured in Terraform with the resource name google_project_usage_export_bucket
. The following sections describe 1 example of how to use the resource and its parameters.
Example Usage from GitHub
resource "google_project_usage_export_bucket" "this" {
bucket_name = var.bucket_name
prefix = var.prefix
project = var.project
dynamic "timeouts" {
Parameters
-
bucket_name
required - string
The bucket to store reports in.
A prefix for the reports, for instance, the project name.
-
project
optional computed - string
The project to set the export bucket on. If it is not provided, the provider project is used.
Explanation in Terraform Registry
Sets up a usage export bucket for a particular project. A usage export bucket is a pre-configured GCS bucket which is set up to receive daily and monthly reports of the GCE resources used. For more information see the Docs and for further details, the API Documentation.
Note: You should specify only one of these per project. If there are two or more they will fight over which bucket the reports should be stored in. It is safe to have multiple resources with the same backing bucket.
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 Project Usage Export Bucket?
Google Compute Engine Project Usage Export Bucket 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 Usage Export Bucket?
For Terraform, the niveklabs/google source code example is useful. See the Terraform Example section for further details.