Design and deploy global external Application Load Balancers on Google Cloud
Guided 6-step discovery to design and deploy a global external ALB with Cloud CDN caching, Cloud Armor WAF and Service Extensions — workload-mapped configs, Terraform HCL or gcloud scripts
- What
- Guided 6-step discovery to design and deploy a global external ALB with Cloud CDN caching, Cloud Armor WAF and Service Extensions — workload-mapped configs, Terraform HCL or gcloud scripts
- Cost
- Free
- Needs
- a Google Cloud account with billing enabled (deploying the designed configuration provisions REAL cloud infrastructure with REAL costs); gcloud CLI for automated discovery/actuation (design-only mode without it) — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — Google's official skill for designing and deploying Google Cloud global external Application Load Balancers: a 6-step discovery process. Step 1, project and protocol/cert basics. Step 2, sequential origin definition — Cloud Storage, Compute Engine MIGs, GKE clusters, Cloud Run services or external IPs/FQDNs — classified by workload type (static assets, cacheable API, uncacheable/transactional, dynamic SSR), then routing rules and CDN logging. Step 3, traffic management and Service Extensions (WASM plugins/callouts). Step 4, workload-mapped Cloud CDN caching (TTL, cache keys, compression, negative caching presets per workload). Step 5, Cloud Armor WAF — rate limiting and OWASP rules calibrated per workload (strict thresholds for login/checkout endpoints). Step 6, review, then emit production-grade Terraform HCL or gcloud CLI scripts, deployed via Infrastructure Manager or bash — with drift detection afterwards. Details stay progressively disclosed; recommended best-practice configs first, advanced knobs only on request. Honest caveats: methodology plus generated IaC — deploying what it designs provisions REAL Google Cloud infrastructure (billing-enabled account required, real cloud costs; deploying anything costs real money); gcloud availability assumed for automated discovery and actuation — without it the skill degrades gracefully to design-only mode. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a Google Cloud account with billing enabled (deploying the designed configuration provisions REAL cloud infrastructure with REAL costs); gcloud CLI for automated discovery/actuation (design-only mode without it) — the skill is guidance the agent follows, not software to install Install "Design and deploy global external Application Load Balancers on Google Cloud" for me. It teaches my agent Google's 6-step load-balancer workflow: discover the project, define backends sequentially by workload type (static, cacheable API, transactional, dynamic SSR), propose workload-mapped Cloud CDN caching and Cloud Armor WAF configs, then generate production Terraform HCL or gcloud CLI scripts and deploy via Infrastructure Manager or bash — with drift detection afterwards. Apache-2.0 licensed. Repository: https://github.com/google/skills/blob/main/skills/cloud/google-cloud-global-frontend-configuration/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "google-cloud-global-frontend-configuration". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. authenticate gcloud and pick the project; describe the workload to front; remember deploying the generated configuration incurs real Google Cloud costs). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.