Table: gcp_compute_backend_bucket - Query Google Cloud Compute Backend Buckets using SQL

A Google Cloud Compute Backend Bucket is a Google Cloud service that allows you to store and serve static web content directly from a Google Cloud Storage bucket. It is typically used in conjunction with HTTP(S) Load Balancing and URL Maps to serve static website content, images, videos, or downloads. It is a globally available resource that scales to meet your needs and provides several benefits including low latency, high scalability, and cost-effectiveness.

Table Usage Guide

The gcp_compute_backend_bucket table provides insights into Backend Buckets within Google Cloud Compute. As a DevOps engineer or system administrator, explore backend bucket-specific details through this table, including its configuration, status, and other metadata. Utilize it to monitor and manage the storage and serving of your static web content, ensuring optimal performance and cost-effectiveness.

Examples

Basic info

Explore the fundamental details of your Google Cloud Platform's compute backend buckets. This is useful for gaining insights into each bucket's name, unique identifier, and description.

select
  name,
  id,
  description,
  bucket_name
from
  gcp_compute_backend_bucket;

select
  name,
  id,
  description,
  bucket_name
from
  gcp_compute_backend_bucket;

List of backend buckets where cloud CDN is not enabled

Explore which backend buckets in your Google Cloud Platform configuration do not have the Cloud CDN feature enabled. This is useful for identifying potential areas to improve content delivery and network performance.

select
  name,
  id,
  enable_cdn
from
  gcp_compute_backend_bucket
where
  not enable_cdn;

select
  name,
  id,
  enable_cdn
from
  gcp_compute_backend_bucket
where
  enable_cdn = 0;

Backend bucket count per storage bucket

Analyze the distribution of backend buckets across storage buckets in your Google Cloud Platform. This can help to balance resource allocation and optimize storage utilization.

select
  bucket_name,
  count(*) as backend_bucket_count
from
  gcp_compute_backend_bucket
group by
  bucket_name;

select
  bucket_name,
  count(*) as backend_bucket_count
from
  gcp_compute_backend_bucket
group by
  bucket_name;

Query examples

Control examples

Compute Backend Bucket should not have dangling storage bucket

Schema for gcp_compute_backend_bucket

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form, e.g. connection_name.
akas	jsonb		Array of globally unique identifier strings (also known as) for the resource.
bucket_name	text	!=, =	Specifies the name of the cloud storage bucket.
creation_timestamp	timestamp with time zone		The creation timestamp of the resource.
description	text		A user-specified, human-readable description of the backend bucket.
enable_cdn	boolean	!=, =	Specifies whether the Cloud CDN is enabled for this backend bucket, or not.
id	bigint		The unique identifier for the resource.
kind	text		The type of the resource.
location	text		The GCP multi-region, region, or zone in which the resource is located.
name	text	=	A friendly name that identifies the resource.
project	text		The GCP Project in which the resource is located.
self_link	text		The server-defined URL for the resource.
signed_url_cache_max_age_sec	bigint		Specifies the maximum number of seconds the response to a signed URL request will be considered fresh.
signed_url_key_names	jsonb		A list od names of the keys for signing request URLs.
title	text		Title of the resource.

Export

This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.

You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh script:

/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- gcp

You can pass the configuration to the command with the --config argument:

steampipe_export_gcp --config '<your_config>' gcp_compute_backend_bucket