HTTP(S) Load Balancing

Related topics

• API Gateway works with HTTP(S) Load Balancing From the official documentation: “Using custom domains for API Gateway with HTTP(S) Load Balancing.”
• Cloud Storage works with HTTP(S) Load Balancing From the official documentation: “Alternatively, you can use [HTTP(S) load balancing](/load-balancing/docs/https/ext-load-balancer-backend-buckets) with Cloud Storage to serve content from a custom domain over HTTPS.”
• GKE Ingress controller configures HTTP(S) Load Balancing From the official documentation: “Typically, the HTTP(S) load balancer is configured by the [GKE ingress controller](https://github.com/kubernetes/ingress-gce), which gets configuration information from a Kubernetes [Ingress](/kubernetes-engine/docs/concepts/ingress) object.”
• HTTP(S) Load Balancing is part of Cloud Load Balancing From the official documentation: “In a GKE cluster, incoming traffic is handled by [HTTP(S) Load Balancing](/load-balancing/docs/https), a component of [Cloud Load Balancing](/load-balancing/docs/load-balancing-overview).”
• 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.”
• API Gateway works with Cloud Run From the official documentation: “API Gateway only supports Cloud Run gRPC services at this time.”
• 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 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 Storage From the official documentation: “Cloud Storage always provides a `Cache-Control` header to Cloud CDN.”
• 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 Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• API Gateway 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.”
• API Gateway secures Cloud Functions From the official documentation: “Deploy an API on API Gateway to secure traffic to a Cloud Functions backend using the Google Cloud CLI.”
• App Engine works with Cloud Storage From the official documentation: “To use a Cloud Storage bucket from an App Engine app:”
• 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 Functions works with Cloud Storage From the official documentation: “You can use Cloud Run functions to launch Workflows in response to Pub/Sub events or file changes in Cloud Storage.”
• API Gateway works with App Engine From the official documentation: “Learn how to use API Gateway to manage and secure traffic to an App Engine backend service.”
• API Gateway works with Cloud Functions From the official documentation: “The steps required to set up API Gateway to manage and secure a [Cloud Functions](/functions/docs) backend service are outlined in the API Gateway [Quickstarts](/api-gateway/docs/quickstarts).”
• API Gateway is an alternative to Cloud Load Balancing From the official documentation: “To securely expose frontend applications to users, you can use Cloud Load Balancing or API Gateway.”
• API Gateway secures Cloud Run From the official documentation: “This page shows you how to set up API Gateway to manage and secure a [Cloud Run](/run/docs) backend service with gRPC.”
• API Gateway works with Google Cloud Armor From the official documentation: “These fields can be used to set up [Identity-Aware Proxy](/iap/docs), [Cloud CDN](/cdn/docs), and [Cloud Armor](/armor/docs) respectively with your API Gateway service.”
• 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 depends on Cloud Storage From the official documentation: “App Engine creates a [default Cloud Storage multi-regional bucket](/appengine/docs/flexible/locations#cloud-storage-location) on your behalf on the same region where it creates your application. It requires this bucket to store the contents of your application.”
• App Engine is an alternative to Cloud Storage From the official documentation: “You can use durable storage like Cloud Storage or an in-memory cache like App Engine to share data between pipeline instances.”
• Cloud Functions depends on Cloud Run From the official documentation: “Cloud Run functions represent the next evolution of Cloud Functions, offering an event-driven programming model with enhanced control and scalability, leveraging the Cloud Run serverless platform.”
• 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 Identity and Access Management From the official documentation: “Cloud Load Balancing caches IAM permissions for five minutes, so it takes up to five minutes for a role change to become effective.”
• 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).”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• 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 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).”
• Identity and Access Management secures Cloud Functions From the official documentation: “You use [Identity and Access Management (IAM)](/iam) to authorize identities to perform administrative actions on functions created using the [Cloud Functions v2 API](/functions/docs/apis)—for example, using `gcloud functions`, the REST API, or Terraform.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”