Standard Tier

Related topics

• Premium Tier is an alternative to Standard Tier From the official documentation: “You can choose Premium Tier or Standard Tier.”
• Standard Tier is part of Network Service Tiers From the official documentation: “Google offers premium (default) and standard [Network Service Tiers](/network-tiers).”
• Standard Tier is part of Security Command Center From the official documentation: “Security Command Center has three tiers: Standard, Premium, and Enterprise.”
• Cloud Storage works with Standard Tier From the official documentation: “To use Standard Tier with Cloud Storage, you must configure your storage bucket as the backend of the Google Cloud load balancer.”
• Standard Tier configures external Application Load Balancer From the official documentation: “This includes traditional on-premises load balancers, [external passthrough Network Load Balancers](/compute/docs/load-balancing/network) on Google Cloud, and [external Application Load Balancers](/compute/docs/load-balancing/http) in a single region configuration (for example…”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• Cloud CDN works with external Application Load Balancer From the official documentation: “[Cloud CDN is supported with external Application Load Balancers](/cdn/docs/overview).”
• Cloud Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• external Application Load Balancer works with Google Cloud Armor From the official documentation: “Learn the value of adding Cloud CDN and Google Cloud Armor to an existing external Application Load Balancer deployment.”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud CDN works with Cloud Storage From the official documentation: “Set up Cloud CDN using a Cloud Storage bucket as the backend”
• Cloud Storage works with external Application Load Balancer From the official documentation: “In order to serve objects through load balancing, the Cloud Storage objects must be publicly accessible.”
• Cloud CDN works with Google Cloud Armor From the official documentation: “You can use Cloud Armor with Cloud CDN to protect the CDN origin servers.”
• Cloud Run works with external Application Load Balancer From the official documentation: “When configured to listen for HTTP/2, Cloud Run automatically handles the HTTP/2 or gRPC traffic arriving from the Application Load Balancer.”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• Premium Tier is part of Network Service Tiers From the official documentation: “Google offers premium (default) and standard [Network Service Tiers](/network-tiers).”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• Cloud CDN works with Cloud Run From the official documentation: “You can use [Cloud CDN](/cdn/docs/overview) to forward requests to Cloud Run and cache OCSP responses.”
• Cloud CDN depends on external Application Load Balancer From the official documentation: “Cloud CDN uses an [external Application Load Balancer](/load-balancing/docs/https) as the origin for cacheable content.”
• Google Cloud Armor secures external Application Load Balancer From the official documentation: “The Google Cloud-managed load balancer applies an initial set of policies—for example, Cloud Armor protection if you are using an external Application Load Balancer.”
• Premium Tier is part of Security Command Center From the official documentation: “Security Command Center has three tiers: Standard, Premium, and Enterprise.”
• Pub/Sub works with Security Command Center From the official documentation: “This page explains how to use the Security Command Center API to enable finding notifications for Pub/Sub.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• Cloud CDN depends on Premium Tier From the official documentation: “Cloud CDN is always Premium Tier.”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run is an alternative to Compute Engine From the official documentation: “The decision of whether to use Cloud Run, GKE, or Compute Engine as your application host involves trade-offs between configuration flexibility and management effort.”
• Cloud Run works with Google Cloud Armor From the official documentation: “See Google Cloud Armor documentation to learn how to [use Google Cloud Armor with Cloud Run](/armor/docs/integrating-cloud-armor#serverless).”
• Compute Engine works with external Application Load Balancer From the official documentation: “You can use a [Terraform module](https://github.com/terraform-google-modules/terraform-google-lb-http/tree/master/examples/multi-mig-http-lb) to bring up an external HTTP load balancer with Compute Engine backends.”
• Compute Engine works with Security Command Center From the official documentation: “After you activate Security Command Center, it starts to analyze, or scan, your resources for Compute Engine and other Google Cloud services.”
• external Application Load Balancer depends on Cloud CDN From the official documentation: “The load balancer doesn't support the use of signed URLs unless Cloud CDN is enabled.”
• Google Cloud Armor secures Cloud CDN From the official documentation: “Cloud Armor helps protect Cloud CDN origin servers from application layer (L7) attacks, such as SQL injection (SQLi) and cross-site scripting (XSS).”
• Google Cloud Armor secures Cloud Run From the official documentation: “Google Cloud Armor helps you protect your Cloud Run services from multiple types of threats, including distributed denial-of-service (DDoS) attacks and application attacks like cross-site scripting (XSS) and SQL injection (SQLi).”
• Google Cloud Armor works with Security Command Center From the official documentation: “Cloud Armor exports two findings to Security Command Center:”
• Security Command Center secures BigQuery From the official documentation: “Security Command Center analyzes various logs for potential threats that affect BigQuery resources.”
• Security Command Center secures Cloud Storage From the official documentation: “Security Command Center analyzes various logs for potential threats that affect Cloud Storage resources.”
• Security Command Center secures Compute Engine From the official documentation: “Security Command Center performs [agentless](#runtime) and [log-based](#log-based) monitoring of Compute Engine resources.”