As your Google Cloud Security Architect, DevSecOps Lead, and Terraform Specialist, here's a comprehensive summary of today's key Google Cloud updates and their Infrastructure as Code (IaC) availability:
- AlloyDB for PostgreSQL: This update introduces direct Iceberg access (Preview), syncing data from BigQuery (GA), and AlloyDB Express (Preview). These features enhance AlloyDB's capabilities for integrated analytics and high-performance operational workloads. Direct Iceberg access enables unified data lake integration, streamlining data governance and potentially reducing data movement, which improves data integrity and security posture by centralizing access control. Syncing data from BigQuery ensures data consistency across analytical and operational stores, critical for compliance and accurate reporting. AlloyDB Express offers specialized performance profiles, crucial for sensitive, high-throughput applications requiring stringent SLAs and consistent performance for security operations. Terraform support is available via the
google_alloydb_clusterresource, supported from provider version4.0.0to5.45.0+. Terraform Provider Documentation
- Cloud SQL for SQL Server: The new Read pool autoscaling (GA) feature allows automatic adjustment of read replica capacity based on CPU usage and/or client connections. This is crucial for maintaining application availability and performance under varying loads, directly supporting business continuity and meeting RTO/RPO objectives. By preventing performance degradation, it indirectly supports compliance requirements for system availability and reliable data access. Terraform support is available via the
google_sql_database_instanceresource, supported from provider version4.50+to5.0+. Terraform Provider Documentation
- API Gateway: Streaming gateways can now securely call Google Cloud APIs, such as
aiplatform.googleapis.com, using service-account access tokens for*.googleapis.comand*.vertexai.googhosts. This significantly enhances the security posture by leveraging Google's IAM for fine-grained access control to backend services. It ensures that API Gateway acts as a secure front-door, authenticating and authorizing requests to internal GCP APIs using established service identity, thereby reducing the risk of unauthorized access and improving auditability. Terraform support is available via thegoogle_api_gateway_gatewayresource, supported from provider version4.0+to5.0+. Terraform Provider Documentation
- Cloud Storage: A critical new feature allows pausing the permanent deletion of objects that have been soft-deleted from a Cloud Storage bucket. When enabled, this setting prevents objects from being irrevocably removed even after their configured
softDeletePolicy.retentionDurationhas expired. This provides administrators with additional time to restore soft-deleted objects, offering a critical safety net against accidental or malicious deletions. This functionality is configured as part of the bucket'ssoftDeletePolicyand complements the existing soft delete retention duration, allowing for a more flexible and robust data recovery strategy. This is a vital security and compliance feature, significantly enhancing data recoverability and acting as an extended recovery window for soft-deleted data. It directly supports compliance requirements for data retention, e-discovery, and disaster recovery, mitigating the impact of human error or insider threats, and adding a layer of protection against ransomware or malicious deletion attempts. Terraform support is available via thegoogle_storage_bucketresource, supported from provider version5.1.0to5.1.0+. Terraform Provider Documentation
Today's Google Cloud updates bring significant enhancements across security, operations, and database management, with a strong focus on hardening infrastructure and streamlining administrative experiences. As a DevSecOps Lead and Terraform Specialist, I've analyzed these updates for their security implications and Infrastructure as Code (IaC) availability.
- Apigee Operator for Kubernetes v1.1.2: This update introduces critical security enhancements by upgrading several core internal libraries, including Netty, Jackson, Jetty, Vert.x, and Guava. These upgrades collectively address numerous CVEs, substantially improving the overall security posture and stability of the Apigee Operator. This proactive patching is vital for maintaining a secure API gateway environment. Terraform support: Not currently available in the
hashicorp/googleprovider.
- Google SecOps - Consolidated Settings and Navigation: The platform now features a unified 'Settings' menu, replacing separate SIEM and SOAR settings. This new menu is logically organized into Administration, Access Management, Investigation, Detection, and Data Management categories, complemented by an updated left navigation. This streamlines the user experience and improves operational efficiency. Crucially, permissions are strictly enforced via Cloud IAM, with Cloud IAM Viewer and Editor roles gaining read-only access to specific SOAR settings, enhancing visibility for broader teams while maintaining robust access control. Terraform support: Not currently available in the
hashicorp/googleprovider.
- Google Distributed Cloud (software only) for VMware - Security & Stability Enhancements: Version 1.35.700-gke.124 delivers significant security and stability improvements. Key updates include the removal of distrusted eMudhra (emSign) and AAA Certificate Services root CAs from system components, container base images, Container-Optimized OS (COS), and Ubuntu node/admin workstation images. This action mitigates risks associated with compromised certificate authorities. The release also includes fixes for various vulnerabilities and resolves issues such as excessive audit logging traffic and cluster upgrade failures. This update is critical for maintaining a hardened hybrid cloud environment. Terraform support: Available via
google_gkeonprem_vmware_clusterin thehashicorp/googleprovider (latest version, e.g., 5.x.x). Documentation.
- AlloyDB for PostgreSQL - Default to PostgreSQL Major Version 18: New AlloyDB for PostgreSQL clusters will now default to PostgreSQL major version 18 upon provisioning if no specific version is declared. This ensures that new deployments automatically benefit from the latest performance, security, and feature enhancements offered by PostgreSQL 18, promoting best practices for database deployments. Terraform support: While the
google_alloydb_clusterresource exists for managing AlloyDB clusters, this specific update regarding the *defaulting* of new clusters to PostgreSQL major version 18 is not directly configurable or managed as a default behavior via thehashicorp/googleprovider. Documentation.