google-cloud-global-frontend-configuration

Designs and deploys Google Cloud global external Application Load Balancers with Cloud CDN and Cloud Armor.

Updated May 11, 2026
One-click install
npx skills add https://github.com/alon3153/upe-social-publisher --skill google-cloud-global-frontend-configuration-alon3153
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: google-cloud-global-frontend-configuration
Source: https://github.com/alon3153/upe-social-publisher/tree/main/.agents/skills/google-cloud-global-frontend-configuration
Command: npx skills add https://github.com/alon3153/upe-social-publisher --skill google-cloud-global-frontend-configuration-alon3153

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Configuring a Google Cloud global external Application Load Balancer involves many interdependent resources (backends, URL maps, target proxies, forwarding rules, CDN policies, WAF rules) where mistakes cause deployment failures or misconfigured security. This Skill guides you through a structured 6-step discovery process that maps your workload requirements to best-practice configurations and generates deployable infrastructure code. ## Core Features & Use Cases - Guided 6-Step Configuration: Walks through basics, origin setup, traffic management, Cloud CDN caching, Cloud Armor security, and review, with opinionated recommendations per workload type (static, cacheable API, transactional API, dynamic SSR). - Resource Discovery: Auto-detects your Google Cloud project and lists existing Cloud Storage buckets, MIGs, GKE clusters, and Cloud Run services via gcloud commands. - Code Generation & Deployment: Produces production-grade Terraform HCL or gcloud bash scripts, deploys via Infrastructure Manager with IAM pre-checks, and detects configuration drift with reconciliation options. - Use Case: You need to serve a static site from a Cloud Storage bucket and an API from Cloud Run behind one HTTPS load balancer. The Skill discovers your resources, recommends CDN caching and rate-limiting rules per workload, and generates Terraform you can deploy immediately. ## Quick Start Ask the agent to design and deploy a Google Cloud global external Application Load Balancer for your project with HTTPS, a Cloud Run backend, and Cloud CDN enabled.

Frequently Asked Questions about google-cloud-global-frontend-configuration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure a Google Cloud global external Application Load Balancer?▼

Follow the 6-step flow: define basics (name, protocol, certificates), configure origins and workload types, set traffic management rules, apply Cloud CDN caching recommendations, add Cloud Armor security policies, then review and deploy as Terraform or a gcloud script.

How do I deploy load balancer Terraform with Infrastructure Manager?▼

Run gcloud infra-manager deployments apply with your local Terraform directory, a service account, and the --import-existing-resources flag. Verify the identity has compute.admin, config.admin, and iam.serviceAccounts.actAs permissions first, and delete any local .terraform directory.

What Cloud CDN cache mode should I use for my workload?▼

Static images and objects use CACHE_ALL_STATIC with long TTLs. Cacheable APIs and dynamic SSR pages use USE_ORIGIN_HEADERS with TTLs managed by the origin. Uncacheable transactional APIs bypass CDN entirely.

Can Cloud Armor rate limiting protect Cloud Storage backend buckets?▼

No. Cloud Armor edge policies (CLOUD_ARMOR_EDGE) required for backend buckets do not support rate_limit_options. Only standard allow or deny rules can be applied to Cloud Storage backends.

How do I detect configuration drift on a deployed load balancer?▼

Create an Infrastructure Manager preview against the existing deployment, then list resource drifts with gcloud infra-manager resource-drifts list. You can either re-apply the Terraform code to overwrite manual changes or backport console changes into your HCL.

When should I not use this load balancer configuration approach?▼

This workflow targets only Google Cloud global external Application Load Balancers. It does not cover non-Google Cloud load balancing, purely regional or internal load balancing setups, unless they are part of a hybrid or failover global design.