Generated banner for Google Cloud Global Frontend Configuration
Generated logo for Google Cloud Global Frontend Configuration

Google Cloud Global Frontend Configuration

GoogleOfficialPublished by Google

  • Skill
  • Workflow
  • Cloud and DevOps
  • Apache-2.0
  • No issues found

From the author

Guides agents through a 6-step discovery process to design and deploy Google Cloud global external Application Load Balancers with Cloud CDN, Cloud Armor, and Service Extensions, mapping workload requirements to best-practice configurations. Use when: - Designing, configuring, or deploying a Google Cloud global external Application Load Balancer, Cloud CDN, Cloud Armor WAF, or Service Extensions. - Discovering existing Google Cloud resources (Cloud Storage, MIGs, GKE, Cloud Run) to use as backends. - Generating production-grade Terraform HCL or gcloud CLI scripts for global external Application Load Balancers. - Actuating deployments via Infrastructure Manager or bash scripts, including IAM pre-checks. - Detecting, analyzing, or reconciling configuration drift on deployed global external Application Load Balancers. Don't use for: - Non-Google Cloud load balancing or security configurations. - Purely regional or internal load balancing setups (unless part of a hybrid/failover global design).
— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured, interactive process for agents to assist users in building production-grade Google Cloud global external Application Load Balancers. It covers the full lifecycle, including resource discovery, backend configuration, traffic management, and security policy setup using Cloud CDN and Cloud Armor. The skill follows an opinionated, best-practice approach, progressively disclosing complexity and offering automated generation of Terraform HCL or gcloud CLI scripts for deployment and drift management.

What it does

  • Discovers existing Google Cloud resources like GKE, Cloud Run, and MIGs for backend integration.
  • Maps specific workload types to optimized Cloud CDN and Cloud Armor security configurations.
  • Generates production-ready Terraform HCL or gcloud CLI scripts based on user requirements.
  • Facilitates deployment through Google Cloud Infrastructure Manager.
  • Detects and reconciles configuration drift between deployed infrastructure and code.
  • Provides a structured 6-step flow to ensure all critical load balancer components are configured correctly.

When to use it

  • When designing or deploying a new global external Application Load Balancer on Google Cloud.
  • When you need to integrate Cloud CDN or Cloud Armor WAF with existing backend services.
  • When you need to generate infrastructure-as-code (Terraform) for load balancing components.
  • When you need to identify and fix configuration drift on existing load balancer deployments.

Advantages

  • Ensures adherence to Google Cloud best practices for performance and security.
  • Reduces manual configuration errors through a guided, step-by-step discovery process.
  • Simplifies complex load balancer setups by hiding advanced options unless requested.
  • Provides clear paths for both initial deployment and ongoing infrastructure maintenance.

Usage examples

“Help me set up a global load balancer for my Cloud Run service.”
The agent will initiate the 6-step flow, starting with project discovery and guiding the user through selecting the Cloud Run backend and applying recommended security/caching settings.
“I need to secure my API backend with Cloud Armor. Can you help?”
The agent will identify the workload as a 'Cacheable API' or 'Uncacheable API' and propose the appropriate Cloud Armor rate limiting and OWASP protection rules.
“Check if my load balancer configuration has drifted.”
The agent will use Infrastructure Manager to generate a preview, compare it against the local Terraform code, and present options to either overwrite or backport the changes.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/google/google-cloud-global-frontend-configuration/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip google-cloud-global-frontend-configuration.zip -d .agents/skills

Documentation by Google

Google Cloud global external Application Load Balancer Configuration Skill

Attribution

MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read Usage Attribution. For commands executed directly in the terminal (never in generated scripts, Terraform, or user code), prefix gcloud with CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:google-cloud-global-frontend-configuration)" and append agent-skills/1.0 (skill:google-cloud-global-frontend-configuration) to User-Agent headers.

Purpose & Agent Guidance

This skill enables the agent to guide users through a structured, 6-step discovery process to design and deploy Google Cloud global external Application Load Balancers (incorporating Cloud CDN, Cloud Armor, and Service Extensions).

Assumptions & Target Environments:

  • This skill assumes it is called from environments (such as Gemini CLI, Antigravity, etc.) where the Google Cloud CLI (gcloud) can be executed.

  • If gcloud is not available or accessible, the skill cannot perform automated resource discovery or managed deployment actuation. In such environments, the skill will limit its support to guiding the design and generating Terraform HCL configurations.

When executing this skill, the agent must:

  • Map user workload requirements to simplified, opinionated best-practice configurations using actual Google Cloud product names.

  • Progressively disclose details, hiding advanced complexity unless the user explicitly asks for customization.

  • Leverage the reference documents in the references/ directory to perform resource discovery, code generation, actuation, and drift detection.

The 6-Step Configuration Flow

Step 1: Basics
  • Project Discovery: Consult references/resource-discovery.md to auto-detect the Google Cloud project ID. Present the discovered project ID to the user.

  • Ask the user for the foundational details of their load balancer:

    • Name & Description: What should we call this load balancer?

    • Protocol Selection: Do they need HTTP, HTTPS, or both?

    • Certificate Management: Do they want to use Google-managed certificates or bring their own existing certificates?

Step 2: Origin Configuration

Help the user define their backend workloads through a strictly sequential, step-by-step loop. Do NOT ask everything at once. All steps are mandatory.

  • Sub-step A - Origin Setup: Ask if they have a single origin or need multi-origin support. Wait for response.

  • Sub-step B - Origin Types: Ask them to select the backend types from: Cloud Storage Buckets, Compute Engine Managed Instance Groups (MIGs), Google Kubernetes Engine (GKE) Clusters, Cloud Run Services, or External/Internet origins (IP/FQDN). Wait for response.

  • Sub-step C - Origin Definition Loop: Execute the following loop sequentially for EACH origin type selected in Sub-step B. Wait for the user to answer for one origin before asking about the next:

    • Resource Discovery: For Google Cloud-native origins (Cloud Storage, MIGs, GKE, Cloud Run), consult references/resource-discovery.md to fetch resources. Present the list starting with 1. Create New, 2. NA. For External/Internet origins, just ask for the FQDN/IP.

    • Workload Type (CRITICAL): Immediately after they define the resource, ask exactly what type of workload is being served:

      1. Static Images / Objects (Static content, images, videos, styling assets)

      2. Cacheable API (Read-only, public APIs where cached data is acceptable)

      3. Uncacheable API / Transactions (Transactional endpoints, login, checkout, account changes)

      4. Dynamic Web (SSR) (Dynamic pages, server-side rendered apps, custom dynamic sessions)

  • Sub-step D - Routing Rules: Once ALL origins have been fully defined one by one, ask how traffic should be routed between them (Path-based, header-based, or query-param-based). Wait for response.

  • Sub-step E - Logging: After routing is established, ask if they want to enable Cloud CDN logging, and if so, at what sampling rate (0-100%). Wait for response.

Step 3: Traffic Management & Extensibility
  • Provide a brief summary of the origins and routing rules defined in Step 2.

  • Ask if they need to enable Advanced Traffic Management settings (such as granular weighted load balancing, traffic mirroring, or Cloud Load Balancing Service Extensions for custom WASM plugins / callouts), or if they want to proceed with Google Cloud Best Practice Configuration.

Step 4: Caching (Cloud CDN)

Propose a "Recommended Configuration" based entirely on the Workload Type from Step 2. Do not list the advanced settings (TTL, Cache Keys, Compression) unless they reject the recommendation and want to customize.

  • If Workload = Static Images / Objects:

    • Cache Mode: Cache All Static

    • TTL: Client (1 day / 86400s), Default (30 days / 2592000s), Max (365 days / 31536000s) — balances long-term cache offload for static assets with periodic re-validation.

    • Cache Key: Protocol + Host + Path (Ignore Query Strings)

    • Compression: Enabled (Brotli & Gzip)

    • Negative Caching: Enabled

    • Serve while stale: Enabled

  • If Workload = Cacheable API:

    • Cache Mode: Use Origin Headers

    • TTL: Managed by Origin (Omitted from configuration to prevent errors)

    • Cache Key: Protocol + Host + Path + Include Query Strings

    • Compression: Enabled (Gzip)

    • Negative Caching: Enabled

    • Serve while stale: Disabled

  • If Workload = Uncacheable API / Transactions:

    • Cache Mode: Disabled (CDN Bypassed)

  • If Workload = Dynamic Web (SSR):

    • Cache Mode: Use Origin Headers

    • TTL: Managed by Origin (Omitted from configuration to prevent errors)

    • Cache Key: Protocol + Host + Path

    • Compression: Enabled (Brotli & Gzip)

    • Cache Bypass: Bypass cache if session cookies (e.g., SESSID, JWT) are present

Step 5: Security (Cloud Armor)

Propose a "Recommended Configuration" based entirely on the Workload Type from Step 2. Keep advanced protection (Bot Management, Threat Intel, Geo-blocking) hidden unless requested.

  • If Workload = Static Images / Objects:

    • Rate Limiting: None (Standard Edge behavior; rate limiting is unsupported on Cloud Armor Edge policies for Cloud Storage buckets).

    • OWASP Protection: Disabled

  • If Workload = Cacheable API:

    • Rate Limiting: 100 requests per minute per client IP (standard baseline to prevent API abuse and DDoS while accommodating normal interactive usage).

    • OWASP Protection: Enabled (SQLi, XSS, Local File Inclusion)

  • If Workload = Uncacheable API / Transactions:

    • Rate Limiting: Strict 30 requests per minute per client IP (tight threshold to protect sensitive transactional endpoints like login/checkout from credential stuffing and brute-force attacks).

    • OWASP Protection: Enabled (SQLi, XSS, Remote Command Execution, Session Fixation)

    • Bot Management & Threat Intel: Enabled (Block malicious bots and known malicious IPs)

  • If Workload = Dynamic Web (SSR):

    • Rate Limiting: 120 requests per minute per client IP (generous threshold to accommodate burst requests for initial page loads and asset hydration in SSR web applications).

    • OWASP Protection: Enabled (SQLi, XSS, CSRF, Shellshock)

    • Geo-blocking: Optional (Restrict/allow specific country access)

Step 6: Review & Deploy
  • Configuration Summary: Generate a complete, formatted markdown table showing all finalized settings from Steps 1 through 5, using Google Cloud product names. Follow this exact template structure:

    ComponentParameter / SettingValue & Justification
    Load BalancerName & Protocol<Name> (HTTP/HTTPS)
    OriginsBackends & Workloads<Backend 1> (<Workload Type>), <Backend 2>...
    Traffic ManagementRouting Rules<Path / Header rules or Default>
    Cloud CDNCache Mode & TTLs<Cache Mode>, Default TTL: <TTL>
    Cloud ArmorRate Limiting & OWASP<RPM Limit>, OWASP Rules: <Enabled/Disabled>
    Service ExtensionsWASM / Callouts<Enabled/Disabled or N/A>
  • Next Action: Ask the user to choose their deployment/generation format (Terraform HCL or gcloud CLI Bash Script) and their next action:

    1. Show Code / Script (Display the HCL code or gcloud bash script. Once displayed, offer options to Download or Deploy/Execute)

    2. Download files (Save main.tf or deploy.sh to the local workspace)

    3. Deploy Configuration: Initiate the deployment via Infrastructure Manager or execute the gcloud script. This should be done using the deployment instructions in references/managed-deployment.md.


Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google
Publisher
Google (Official)
Source
google/skills · skills/cloud/google-cloud-global-frontend-configuration · commit 2194d3b
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download google-cloud-global-frontend-configuration.zip