Premium Tier

Related topics

• Premium Tier is part of Network Service Tiers From the official documentation: “Premium Tier delivers traffic on Google's premium backbone, while Standard Tier uses regular ISP networks.”
• Premium Tier is part of Security Command Center From the official documentation: “Security Command Center has three tiers: Standard, Premium, and Enterprise.”
• Cloud CDN depends on Premium Tier From the official documentation: “Cloud CDN is always Premium Tier.”
• Cloud CDN works with Premium Tier From the official documentation: “Cloud CDN | Only Premium Tier | Standard Tier is not available for Cloud CDN. |”
• 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.”
• 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.”
• backend service works with managed instance group From the official documentation: “Add the backend instance group to the backend service.”
• managed instance group is part of backend service From the official documentation: “Add the managed instance group to the backend service.”
• App Engine is an alternative to Cloud Run From the official documentation: “App Engine and Cloud Run are Google Cloud platforms for hosting apps and services.”
• Cloud CDN works with global external Application Load Balancer From the official documentation: “When you use an external backend with a global external Application Load Balancer, you can improve performance by using Cloud CDN caching.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud CDN works with Cloud Load Balancing From the official documentation: “Because Cloud CDN integrates with Cloud Load Balancing, Cloud CDN's approach differs from the approach of conventional CDNs.”
• 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 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.”
• App Engine works with Cloud Logging From the official documentation: “App Engine automatically sends both the request logs and app logs to the [Cloud Logging](/logging/docs/overview) agent.”
• App Engine works with Cloud Monitoring From the official documentation: “This tutorial shows how to set up an uptime alert for the [Python Hello World app](/python/getting-started/hello-world) running on App Engine flexible environment using [Cloud Monitoring](/monitoring/docs).”
• backend service works with Cloud CDN From the official documentation: “Clear the checkboxes of any backend services that you want to stop from using Cloud CDN.”
• backend service depends on managed instance group From the official documentation: “As a part of this step, you need to assign the health check that you created to the backend service and add the instance group as the backend to the backend service.”
• Cloud Load Balancing works with Cloud Run From the official documentation: “If you are using Cloud Load Balancing with Cloud Run, configure custom error responses at the load balancer level.”
• Cloud Load Balancing works with managed instance group From the official documentation: “It configures the load balancer to connect to the instance group.”
• Cloud Monitoring works with Cloud Run From the official documentation: “Cloud Monitoring records metrics regarding the execution of Cloud Run.”
• 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.”
• App Engine works with Cloud CDN From the official documentation: “Cloud CDN is supported for backend services with Cloud Run, Cloud Run functions, API Gateway, and App Engine backends.”
• App Engine works with Cloud Load Balancing From the official documentation: “If you want to use an IP address that only maps to your domain then you should instead [set up a load balancer with App Engine](/load-balancing/docs/https/setting-up-https-serverless).”
• App Engine 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.”
• 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.”
• Cloud CDN works with Cloud Logging From the official documentation: “Each Cloud CDN request is logged in [Cloud Logging](/logging/docs/write-query-log-entries-gcloud).”
• Cloud CDN works with Cloud Monitoring From the official documentation: “Cloud CDN exports metrics to Cloud Monitoring.”
• Cloud CDN is part of global external Application Load Balancer From the official documentation: “Configure a backend service for the global external Application Load Balancer, attach the internet NEG, and enable Cloud CDN or Cloud Armor if required.”
• Cloud CDN depends on global external Application Load Balancer From the official documentation: “Cloud CDN leverages Google Cloud global external Application Load Balancers to provide routing, health checking, and Anycast IP support.”
• Cloud CDN works with managed instance group From the official documentation: “[Set up Cloud CDN with a managed instance group](/cdn/docs/setting-up-cdn-with-mig)”
• Cloud Load Balancing works with Cloud Monitoring From the official documentation: “Key performance and health metrics reported by Cloud Monitoring for Cloud Load Balancing resources.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• 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 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 Monitoring works with global external Application Load Balancer From the official documentation: “The load balancer also exports monitoring data to Cloud Monitoring.”
• global external Application Load Balancer works with managed instance group From the official documentation: “The managed instance group provides VMs that run the backend servers of an external Application Load Balancer.”
• 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.”