As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive daily summary of the latest Google Cloud updates and their Infrastructure as Code (IaC) availability:
Bigtable: Apache Avro Schema Bundles (Preview)
- Feature & Security Summary: Bigtable now supports creating and managing Apache Avro schema bundles via the Google Cloud console and viewing definitions in Bigtable Studio (Preview). This enhancement was introduced to bolster data governance and interoperability. Avro schemas provide a robust, language-agnostic framework for defining data structures, ensuring data consistency, and simplifying data evolution. From a security and compliance perspective, well-defined schemas are critical for data validation, preventing malformed or unauthorized data from entering the system, and ensuring adherence to expected formats, which is vital for regulatory compliance and maintaining data integrity. Bigtable Studio's viewing capability further aids in auditing and understanding the structure of data within your Bigtable instances.
- Terraform Availability: Fully supported. You can manage Bigtable tables, which will implicitly support schema definitions, using the
google_bigtable_tableresource. Supported inhashicorp/googleprovider versions5.35.0and later. Documentation Link
Pathways on Cloud: General Availability on GKE
- Feature & Security Summary: Pathways on Cloud is now generally available on GKE, offering resilient training, elastic scaling, hot-swapping, colocated sidecars, Shared Pathways Service, single-process profiling, and agentic debugging capabilities for TPU v5e, v5p, v6e, and TPU7x. This update marks a significant advancement in providing a more robust, scalable, and manageable infrastructure for advanced AI/ML training workloads. The emphasis on resilient training and elastic scaling directly contributes to operational security by ensuring workloads can withstand failures and dynamically adapt to demand, thereby reducing the risk of service disruption. Features like hot-swapping and agentic debugging improve reliability and enable quicker recovery from issues, which is paramount for maintaining the integrity and availability of high-value AI computations. While not a direct security feature, enhanced stability and manageability reduce the attack surface associated with misconfigurations or unpatched systems due to operational overhead.
- Terraform Availability: Supported for managing the underlying GKE clusters. The
google_container_clusterresource can be used to provision and configure GKE clusters that can host Pathways on Cloud. Supported inhashicorp/googleprovider versions4.50+and later. Documentation Link
Cloud Run: Vulnerability Assessment (Preview)
- Feature & Security Summary: Cloud Run has introduced a preview release of Vulnerability Assessment. This capability empowers users to detect vulnerabilities and exposed secrets directly within the container images deployed to their Cloud Run services, jobs, and worker pools. This is a critical security enhancement, designed to provide developers and security teams with early and continuous visibility into potential security risks within their serverless container deployments. By identifying vulnerabilities (e.g., outdated libraries, known CVEs) and exposed secrets (e.g., hardcoded credentials) proactively, organizations can mitigate risks, enforce security policies, and significantly improve their overall security posture. This directly aligns with DevSecOps principles by integrating security scanning into the deployment pipeline, reducing the likelihood of vulnerable applications reaching production, and aiding compliance efforts.
- Terraform Availability: While Terraform can manage Cloud Run services via
google_cloud_run_v2_service, this specific vulnerability assessment *feature* is a capability of the service itself and is not directly exposed as a configurable resource within thehashicorp/googleprovider at this time. Documentation Link
Anthos Config Management: Security Patch Update
- Feature & Security Summary: Anthos Config Management has received a security patch, focusing on upgrading two key internal dependencies to address CVEs. Specifically, the
git-syncdependency has been updated from v4.4.2 to v4.5.0, and theOpen Telemetryimage has been upgraded from 0.152.0 to 0.159.0. This update is purely for security and robustness, without introducing new user-facing functionalities. It was implemented to patch known vulnerabilities in these critical components, thereby enhancing the overall security posture of Anthos Config Management.git-syncis fundamental for synchronizing configurations from Git repositories, making any vulnerability a potential vector for unauthorized configuration changes or data exfiltration. Open Telemetry is used for observability, and patching it helps prevent potential exploits that could compromise monitoring data or introduce side-channel attacks. By upgrading these dependencies, Google ensures that ACM remains a secure and reliable platform for GitOps-driven configuration management, which is vital for maintaining compliance and preventing configuration drift that could introduce security gaps. - Terraform Availability: This specific security patch for internal dependencies is managed by the Anthos Config Management service itself and is not directly configurable via Terraform. Terraform is used to manage the deployment and configuration of Anthos Config Management features (e.g.,
google_gke_hub_feature), but not the underlying service's internal patching. Documentation Link
Google Cloud Daily Brief: Concurrency Controls, API Gateway Security & IaC Updates
As a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's your daily summary of critical Google Cloud updates and their Infrastructure as Code (IaC) availability.
---
#### Analytics & Data
- BigQuery: Pipeline Concurrency Control (GA)
- Feature & Security Summary: This new Generally Available (GA) feature allows users to define the maximum number of concurrently executed pipeline tasks during the creation or scheduling of a BigQuery pipeline. This was introduced to provide finer-grained control over resource allocation and parallel processing, preventing resource contention and ensuring predictable performance for data transformations. From a security and compliance perspective, managing concurrency is vital for maintaining service stability, preventing potential denial-of-service scenarios due to uncontrolled resource consumption, and ensuring that data processing adheres to operational resilience requirements.
- Terraform Availability: Direct Terraform support for configuring BigQuery pipeline concurrency limits is not yet available in the
hashicorp/googleprovider. While resources likegoogle_bigquery_data_transfer_configexist for data transfers, this specific concurrency feature is not exposed. - Provider:
hashicorp/google - Resource: N/A (for this specific feature)
- Versions: N/A
- Provider Documentation
- Dataform: Workflow Concurrency Limits (GA)
- Feature & Security Summary: Dataform now supports defining a maximum limit for concurrent actions within a workflow execution or scheduled configuration. This feature is crucial for optimizing performance, managing resource allocation, and ensuring stability, particularly for complex data pipelines or when sharing BigQuery resources. By limiting concurrency, organizations can prevent excessive parallel processing that might lead to resource contention, rate limit issues with underlying services, or unexpected costs. This enhances operational security by preventing self-inflicted outages and ensuring predictable resource usage.
- Terraform Availability: This feature is supported via the
hashicorp/googleprovider. - Provider:
hashicorp/google - Resource:
google_dataform_repository_workflow_config - Versions: Supported since
4.67.0, latest4.67.0. - Provider Documentation
---
#### Networking
- Apigee Edge Microgateway: Version 3.3.12 Release & Security Fixes
- Feature & Security Summary: Apigee Edge Microgateway version 3.3.12 is now available, bringing critical updates. Key changes include updated component versions (
microgateway3.3.12,plugins3.3.9,edgeauth3.2.2), revised Node.js support (now exclusively 22, 24, and 26; Node.js 20 support removed, 26 added), and modifications to the Docker image. The Docker image (gcr.io/apigee-microgateway/edgemicro:3.3.12) no longer includesnpmandnpx, requiring custom plugin dependencies to be installed *before* adding plugins to the container. Most importantly, this release addresses multiple critical security vulnerabilities (e.g., CVE-2026-12590, CVE-2026-14257, CVE-2026-111497). The Docker image is built onnode:24.22.1-trixie-slimwith Node.js fixes, and npm installations require upgrading Node.js runtime to specific patched versions (22.23.4, 24.22.1, or 26.12.1 or later). These security fixes are paramount for maintaining the integrity and confidentiality of API traffic, reducing the attack surface, and ensuring compliance with security best practices for API gateways. The Docker image changes promote a more secure build process by encouraging pre-installation of dependencies, mitigating potential runtime supply chain risks. - Terraform Availability: While Apigee Edge Microgateway itself doesn't have a dedicated Terraform resource for its configuration, its deployment targets (e.g., Cloud Run, GKE, Compute Engine) can be managed by Terraform. The provided Terraform support link refers to
google_cloud_run_service, which could be used to deploy Apigee Edge Microgateway in a containerized environment. - Provider:
hashicorp/google - Resource:
google_cloud_run_service(for deployment target, not direct Microgateway configuration) - Versions: Supported since
1.0.0, latest5.0.0. - Provider Documentation