IaC Bazaar
Google CloudLive-tested

Cloud SQL (PostgreSQL/MySQL) HA Instance

Regional-HA Cloud SQL with private IP (PSA/PSC), automated backups, PITR, read replicas and IAM database auth.

terraformGoogle Cloud#gcp

Compare Managed Relational Database across clouds →

Part of: GCP Production Landing Zone, GCP Kubernetes Platform

gcp-cloud-sqlterraform v1.7

Verification

Live-tested

Really deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.

Conformance

  • Static validation (fmt · validate · tflint)
  • Security scan clean (Checkov)
  • Plan tests (mocked: validation rules · outputs)

Provenance

Functional

  • Live-tested - applied, verified, destroyed

Last verified 2026-06-30 · how we verify

Verify this download

cosign · sha-256

Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.

# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub

# 2. This module's Sigstore bundle
curl -o gcp-cloud-sql-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/gcp-cloud-sql/signature

# 3. Verify the tarball you downloaded
cosign verify-blob \
  --key cosign.pub \
  --bundle gcp-cloud-sql-1.0.0.sigstore.json \
  gcp-cloud-sql-1.0.0.tar.gz
# → Verified OK

# 4. (optional) confirm the checksum too
echo "717f41b9135caebbb22b0839a0a82bdea2fd0d62586982a41fabc1a5e7b9044a  gcp-cloud-sql-1.0.0.tar.gz" | sha256sum -c
Signature bundlePublic keyMachine-readable receiptHow we verify

Use it from the registry

terraform · opentofu
module "cloud_sql" {
  source  = "www.iac-bazaar.com/iac-bazaar/gcp-cloud-sql/gcp"
  version = "1.0.0"
}

Paid module — needs a purchase (or a subscription that covers it) plus a registry token from /account/tokens. Full setup: registry docs.

Inputs & outputs

Create a free account to read this module's contract

The declared contract — every input name, type, default and description, plus every output — is shown to signed-in accounts, not to anonymous visitors.

A free account sees the contract of every Free module. This one is Premium, so its contract unlocks when you buy it.

Create a free account →Sign in

Documentation

gcp-cloud-sql

Regional-HA Cloud SQL (PostgreSQL/MySQL) with private IP via Private Service Access, automated backups, point-in-time recovery, read replicas and IAM database auth — the PSA networking footgun solved for you. Works with Terraform and OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.

Secure defaults:

  • No public IP (ipv4_enabled = false); private IP through a PSA peering the module can create for you (reserved range + servicenetworking connection)
  • TLS-only client connections (ssl_mode = "ENCRYPTED_ONLY")
  • deletion_protection = true
  • Regional HA (availability_type = "REGIONAL"), daily backups + PITR (engine-aware: WAL on PostgreSQL, binlog on MySQL)
  • IAM database authentication on, with the engine-correct flag spelling
  • On PostgreSQL, the four low-cost CIS-recommended log flags default to on (log_checkpoints, log_connections, log_disconnections, log_lock_waits); your database_flags entries override them

Requirements

  • Terraform or OpenTofu >= 1.6
  • hashicorp/google >= 7.0, < 8.0
  • APIs: sqladmin.googleapis.com, plus servicenetworking.googleapis.com and compute.googleapis.com when using private IP

Upgrade note (1.0.x)

  • create_private_service_access now defaults to false and must be set explicitly for private-IP deployments. The old default (true behind a private_network != null test) made the resource count depend on an apply-time value, which broke any composition that creates the VPC and the instance in one apply (e.g. the GCP landing-zone stack). If you set private_network and relied on the implicit PSA creation, add create_private_service_access = true.
  • PostgreSQL instances now get four low-cost CIS-recommended log flags by default (log_checkpoints, log_connections, log_disconnections, log_lock_waits). Database flag changes restart the instance; override any of them explicitly via database_flags (buyer entries win the merge).

License

Commercial — IaC Bazaar EULA. © IaC Bazaar. Original work (not derived from a third-party module).

Usage code & full reference unlock after purchase

The complete copy-paste usage, the full input/output reference, and operational notes ship with your licence - shown here and bundled in the download.

  • Usage
  • Inputs
  • Outputs
  • Notes

Related modules

Google Cloud✓ live-tested

AlloyDB for PostgreSQL Cluster

AlloyDB cluster with primary + read-pool instances, PSC connectivity, automated backups and columnar/vector engine flags.

$179.00v1.0.0
Google Cloud✓ live-tested

BigQuery Dataset & Tables

Datasets with partitioned/clustered tables, authorized views, CMEK and dataset-level access controls.

$179.00v1.0.0
Google Cloud✓ live-tested

Cloud Bigtable Instance & Table

A single-cluster Cloud Bigtable instance (one 1-node SSD cluster, the smallest footprint) plus a table with column families, IAM-only access, optional CMEK, and deletion protection on.

$179.00v1.0.0
Google Cloud✓ live-tested

Cloud Spanner Instance & Database

A regional Cloud Spanner instance at the smallest billable size (100 processing units) plus a database with optional starter schema, drop protection, and Terraform deletion protection on.

$179.00v1.0.0
Google Cloud✓ live-tested

Memorystore Redis/Valkey

Private Memorystore instance or cluster (Redis or Valkey) with auth, TLS and maintenance policy on your VPC.

$179.00v1.0.0
AWS✓ live-tested

Aurora Cluster (Serverless v2 ready)

Aurora PostgreSQL/MySQL cluster with instances, parameter groups, Serverless v2 scaling, and enhanced monitoring.

$179.00v1.0.0