Premium Tier

Related topics

• Premium Tier is part of Security Command Center From the official documentation: “Security Command Center has three tiers: Standard, Premium, and Enterprise.”
• Cloud Load Balancing depends on Premium Tier From the official documentation: “Premium Tier networking is also necessary to use Google's global load-balancing products.”
• Cloud NAT gateway works with Premium Tier From the official documentation: “When you create a Cloud NAT gateway, Google Cloud lets you assign IP addresses from both Standard Tier and Premium Tier.”
• global external Application Load Balancer depends on Premium Tier From the official documentation: “Certain external load balancers, such as the global external Application Load Balancer and the global external proxy Network Load Balancer can only be configured in Premium Tier.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Load Balancing works with Google Cloud Armor From the official documentation: “For applications that are exposed behind Cloud Load Balancing, use Google Cloud Armor default policies or configure your own policies to add Layer 3 to Layer 7 network protection for externally-facing applications or services.”
• Cloud Logging works with Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Google Cloud Armor secures global external Application Load Balancer From the official documentation: “Cloud Armor also provides configurable security policies to services accessed through an external Application Load Balancer.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Run works with global external Application Load Balancer From the official documentation: “You can use a global external Application Load Balancer as the frontend for your Cloud Run, Cloud Run functions, and App Engine applications.”
• Google Cloud Armor works with Security Command Center From the official documentation: “Cloud Armor integrates automatically with the Security Command Center.”
• Model Armor works with Security Command Center From the official documentation: “Model Armor findings are published to Security Command Center on the Premium and Enterprise tiers.”
• backend service is part of Cloud Load Balancing From the official documentation: “Quotas and limits for Cloud Load Balancing resources such as forwarding rules, backend services, and more.”
• backend service configures Cloud Load Balancing From the official documentation: “A [backend service](/compute/docs/reference/rest/v1/backendServices) defines how Cloud Load Balancing distributes traffic.”
• backend service works with Cloud Logging From the official documentation: “After you enable logging on the backend service, HTTP or HTTPS requests are logged by using [Cloud Logging](/logging/docs) logs requests.”
• backend service is part of global external Application Load Balancer From the official documentation: “Global external Application Load Balancers use the `EXTERNAL_MANAGED` load balancing scheme and global load balancing components, such as the forwarding rule, URL map, and backend service.”
• backend service works with Google Cloud Armor From the official documentation: “If you use one of the following load balancers, you can add additional protection to your applications by enabling Cloud Armor on the backend service during load balancer creation:”
• Cloud Load Balancing works with Cloud Run From the official documentation: “Ensures that Cloud Run services are configured to accept traffic only from Internal sources and Cloud Load Balancing.”
• Cloud Load Balancing works with GKE From the official documentation: “GKE and GKE Enterprise network controllers also support the deployment of Cloud Load Balancing for built-in integration with container networking.”
• Cloud Load Balancing works with Model Armor From the official documentation: “When using Model Armor as a service extension with Cloud Load Balancing, the Service Extensions service agent is involved.”
• Cloud Logging works with Cloud Run From the official documentation: “Cloud Logging captures, stores, and analyzes Cloud Run logs.”
• Cloud Logging works with global external Application Load Balancer From the official documentation: “This document shows you how to configure and use [Cloud Logging](/logging) and [Cloud Monitoring](/monitoring) with classic Application Load Balancers, global external Application Load Balancers, and Cloud CDN.”
• Cloud Logging works with Google Cloud Armor From the official documentation: “Each HTTP(S) request that is evaluated against a Cloud Armor security policy is logged through Cloud Logging.”
• Cloud Logging works with Model Armor From the official documentation: “Use Cloud Logging to analyze Model Armor usage patterns, errors, and performance metrics.”
• Cloud Logging is an alternative to Security Command Center From the official documentation: “After you revoke compromised credentials and restore your service, review all access to your Google Cloud resources. You can use Cloud Logging or Security Command Center.”
• 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).”
• GKE works with global external Application Load Balancer From the official documentation: “After you [create the equivalent resources](#migrate-resources), exposing external endpoints behind a global external Application Load Balancer enables you to gradually migrate traffic between Cloud Run and Google Kubernetes Engine (GKE).”
• GKE works with Google Cloud Armor From the official documentation: “This document explains how Cloud Armor interacts with VPC firewall rules, Identity-Aware Proxy (IAP), Google Kubernetes Engine (GKE), Cloud CDN, and Global Front End.”
• GKE configures Google Cloud Armor From the official documentation: “You can configure Cloud Armor by using Google Kubernetes Engine (GKE) ingress security policies.”
• GKE works with Model Armor From the official documentation: “To screen traffic to and from a GKE cluster and to protect all interactions with the AI models, you can integrate [Model Armor](/security-command-center/docs/model-armor-gke-integration) with GKE .”
• Google Cloud Armor is part of Cloud Load Balancing From the official documentation: “Consequently, RoCE VPC networks for bare metal instances don't support load balancer features,<br>including [Google Cloud Armor](/armor/docs/cloud-armor-overview).”
• 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).”
• Security Command Center depends on Cloud Logging From the official documentation: “By using Security Command Center, you can see when high-risk threats such as malware, cryptomining, unauthorized access to Google Cloud resources, outgoing DDoS attacks, port scanning, and brute-force SSH have been detected based on your Cloud Logging logs.”
• Security Command Center secures GKE From the official documentation: “Security Command Center performs [runtime](#runtime) and [log-based](#log-based) monitoring of Google Kubernetes Engine resources.”