# Google Cloud Daily Brief: 8 service updates

- Cloud: Google Cloud
- Date: 2026-11-07
- Canonical page: https://jonathanglass.cloud/whats-new/gcp/2026-11-07.html
- Dataset: https://jonathanglass.cloud/data/gcp/daily_summaries.json

Good morning team, here's a comprehensive overview of the latest Google Cloud updates and their Terraform availability, focusing on security, compliance, and infrastructure as code.

### **1. Cloud Trace: Data Residency and CMEK for Trace Buckets**

*   **Feature & Security Summary**: Cloud Trace now supports reprovisioning of trace buckets to meet stringent data residency and Customer-Managed Encryption Keys (CMEK) requirements. This update is crucial for organizations operating under strict regulatory frameworks (e.g., GDPR, HIPAA) that mandate data localization and customer control over encryption keys. By allowing buckets to be reprovisioned to align with the organization's default observability bucket settings, it ensures that trace data, which can contain sensitive operational insights, adheres to defined geographic boundaries and is encrypted with keys managed by the customer. This significantly enhances the compliance posture and data sovereignty for critical observability data.
*   **Terraform Availability**: Supported in the `hashicorp/google` provider. While the specific resource for 'trace bucket reprovisioning' is not explicitly named in the provided `terraformSupport` block, the service generally has support. The `terraformSupport` block indicates general Cloud Trace support from version `4.50+` (first) to `5.0+` (latest). For more details, refer to the [Cloud Trace provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/cloud_trace).

### **2. Cloud Bigtable: Automated Daily Hot Backups (GA)**

*   **Feature & Security Summary**: Cloud Bigtable has announced the General Availability (GA) of automated backup policy configuration for daily hot backups on SSD instances, complete with configurable retention. This is a critical enhancement for data resilience and disaster recovery. Automated daily hot backups minimize Recovery Point Objective (RPO) by ensuring frequent, consistent data snapshots with minimal performance impact on live instances. Configurable retention policies empower organizations to meet specific regulatory compliance requirements for data archival and retention, while also optimizing storage costs. This feature significantly strengthens the data protection strategy for Bigtable workloads.
*   **Terraform Availability**: Supported in the `hashicorp/google` provider via the `google_bigtable_instance` resource. This feature is supported from version `4.0+` (first) to `5.0+` (latest). For more details, refer to the [Bigtable Instance provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/bigtable_instance).

### **3. Artifact Registry: Assured Open Source Software Premium Tier Expansion**

*   **Feature & Security Summary**: The Assured Open Source Software (AOSS) Premium tier now extends its support to Google Cloud regions and multi-regions for remote/proxy Artifact Registry repositories. This is a pivotal update for enhancing software supply chain security. AOSS provides curated, vulnerability-scanned, and signed open-source packages, mitigating risks associated with untrusted or compromised open-source dependencies. By expanding this coverage to regional and multi-regional proxy repositories, organizations can ensure that all their consumed open-source components, regardless of their origin or caching location, benefit from Google's rigorous security vetting. This directly contributes to a more secure software development lifecycle (SSDLC) and helps meet compliance standards requiring robust supply chain integrity.
*   **Terraform Availability**: Supported in the `hashicorp/google` provider via the `google_artifact_registry_repository` resource. This feature is supported from version `4.0+` (first) to `5.0+` (latest). For more details, refer to the [Artifact Registry Repository provider documentation](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/artifact_registry_repository).

### **4. Cloud Load Balancing: IPv6 Frontend Configuration (GA)**

*   **Feature & Security Summary**: Google Cloud Load Balancing now offers General Availability (GA) for frontend configuration to handle incoming IPv6 traffic across various regional and cross-region external/internal Application and Network Load Balancers. This update is essential for organizations transitioning to or operating in IPv6-enabled environments, addressing IPv4 address exhaustion and supporting modern network designs. From a security and operational standpoint, it ensures that critical load balancing functionalities, including traffic distribution, SSL termination, and WAF policies, can be consistently applied to both IPv4 and IPv6 traffic. This helps maintain a unified security posture across dual-stack deployments and supports compliance with IPv6 readiness mandates. To enable this, the associated proxy-only subnet must be configured with a `IPV4_IPV6` (dual-stack) type.
*   **Terraform Availability**: Supported in the `hashicorp/google` provider. This feature is supported from version `3.4.0` (first) to `5.0.0` (latest). Relevant resources for configuring IPv6 frontends and dual-stack subnets would include `google_compute_forwarding_rule` (for load balancer frontend configuration) and `google_compute_subnetwork` (for setting the `stack_type` on proxy-only subnets). A specific provider documentation URL was not provided in the input.

As a Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's your daily summary of critical Google Cloud updates and their IaC availability:

### BigQuery: Enhanced Analytics, Model Governance, and Data Transfer Updates

*   **Feature & Security Summary**: BigQuery introduces Graph capabilities and GQL support for on-demand pricing, significantly boosting its analytical power for connected datasets. A new custom organization policy (`constraints/bigquery.restrictModelOperations`) is in preview, enabling administrators to enforce granular controls over operations on BigQuery ML models. This is a crucial security enhancement for governing machine learning assets and ensuring compliance. Additionally, a breaking change for the BigQuery Data Transfer Service Shopify connector deprecates `legacyMode` and `permitSkuSharing` fields by January 31, 2027, requiring users to update configurations. 
    *   **Terraform Availability**: The custom organization policy for BigQuery models is supported via the `google_organization_policy` resource in the `hashicorp/google` provider, available from version `3.50.0` up to `5.28.0`. [Learn more](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/organization_policy).

### Gemini Enterprise Agent Platform: Dedicated Memory Bank Management

*   **Feature & Security Summary**: The Gemini Enterprise Agent Platform now features a dedicated Memory Bank page in the Google Cloud console. This update provides comprehensive management capabilities for memory banks, including creation (with Google-managed or Cloud KMS encryption), viewing, editing, and deletion. Users can inspect and filter memories (unstructured/structured), view revision history, and configure generation, retrieval, and retention policies. The platform also offers agent integration snippets and enhanced memory management controls for deployed agents. While not a direct security feature, the ability to manage encryption for memory banks is a key security control for sensitive AI data. 
    *   **Terraform Availability**: Direct Terraform support for managing Gemini Enterprise Agent Platform Memory Banks is currently not available in the `hashicorp/google` provider.

### Config Controller: Underlying Config Connector Upgrade

*   **Feature & Security Summary**: Config Controller has been updated to integrate Config Connector v1.159.0. This is an internal component upgrade that transparently enhances Config Controller's capabilities. Users will benefit from managing a broader set of Google Cloud resources, new features for existing resources, and general performance improvements and bug fixes inherited from the updated Config Connector version. This ensures that Config Controller remains a robust tool for declarative management of Google Cloud resources, aligning with DevSecOps principles by enabling consistent and auditable infrastructure as code. 
    *   **Terraform Availability**: Managing Config Controller instances is supported via the `google_config_controller_instance` resource in the `hashicorp/google` provider, available from version `4.40.0` up to `5.20.0`. [Learn more](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/config_controller_instance).

### Apigee hybrid: Critical Stability and Security Patch Update

*   **Feature & Security Summary**: This release for Apigee hybrid is a significant patch update focused on enhancing stability, reliability, and security. Key improvements include: correct processing of `HTTPS_PROXY` environment variables by `apigee-connect-agent` for egress, removal of compromised emSign and Comodo AAA Services roots from trust stores to bolster security, and a fix for incorrect `x-envoy-decorator-operation` header forwarding. The `apigee-redis` container has been updated to the Valkey engine (v8.1.10) while maintaining compatibility. Policy execution issues (e.g., `AssignMessage`, `OASValidation`) and Kubernetes configuration persistence problems have been resolved. A crucial security enhancement is the dynamic SSLContext rebuild for multi-certificate truststore changes, eliminating manual restarts. Most importantly, numerous security vulnerabilities (CVEs) have been addressed across a wide array of Apigee hybrid components, significantly improving the platform's overall security posture. 
    *   **Terraform Availability**: While `google_apigee_instance` exists for managing Apigee instances, specific configurations related to these detailed patch updates for Apigee hybrid components are generally managed within the Kubernetes cluster or via Apigee's own configuration mechanisms, and are not directly exposed as configurable resources in the `hashicorp/google` provider. [Learn more about Apigee instance management](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/apigee_instance).

## Announcements in this summary

- [Cloud Trace](https://docs.cloud.google.com/release-notes?product=cloud-trace#November_06_2026) (Operations)
- [Cloud Bigtable](https://docs.cloud.google.com/release-notes?product=bigtable#November_06_2026) (Databases)
- [Artifact Registry](https://docs.cloud.google.com/release-notes?product=assured-open-source-software#November_06_2026) (DevOps)
- [Cloud Load Balancing](https://docs.cloud.google.com/release-notes?product=cloud-load-balancing#November_06_2026) (Networking)
- [BigQuery](https://docs.cloud.google.com/release-notes?product=bigquery#November_06_2026) (Analytics & Data)
- [Gemini Enterprise Agent Platform](https://docs.cloud.google.com/release-notes?product=gemini-enterprise-agent-platform#November_06_2026) (AI & Machine Learning)
- [Config Controller](https://docs.cloud.google.com/release-notes?product=config-controller#November_06_2026) (Management Tools)
- [Apigee hybrid](https://docs.cloud.google.com/release-notes?product=apigee-hybrid#November_05_2026) (Networking)
