Cloud KMS Keyring & Keys
Keyrings and rotation-enabled crypto keys with per-key IAM for CMEK across GCS, BigQuery, Cloud SQL and disks.
Compare Secrets & Key Management across clouds →
Part of: GCP Production Landing Zone
Verification
Live-testedReally 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
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-08-03 · how we verify
Verify this download
cosign · sha-256Don'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-kms-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-kms/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-kms-1.0.0.sigstore.json \
gcp-kms-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "ad696276cf5cc0bc334c002d03ae6ecedb6f50b4ace4be179207ca72d665e2bd gcp-kms-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "kms" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-kms/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 Basic, so its contract unlocks when you buy it.
Documentation
gcp-kms
A Cloud KMS key ring and its crypto keys, with automatic rotation on
by default for symmetric keys and least-privilege per-key IAM for CMEK
across GCS, BigQuery, Cloud SQL, Compute disks, and any other service that
accepts a customer-managed encryption key. Works with Terraform and
OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.
Status: static-validated, live-test pending. Ships under live-test quarantine — validated with
tofu fmt,tofu validate, andtflint. Real apply → verify → destroy against a GCP project is pending a cloud sandbox. KMS live-testing is special: key rings and keys are not deletable, so a live lane must randomize names and treat "destroy" as versions scheduled for destruction — see the lifecycle note below.
Secure defaults
- Rotation on by default — symmetric
ENCRYPT_DECRYPTkeys rotate every 90 days (7776000s) unless you overriderotation_period. Rotation only applies to symmetric keys; the module auto-nullsrotation_periodfor asymmetric/MAC keys, so their minimal config applies without having to setrotation_period = nullyourself. - Least-privilege per-key IAM — grants are additive
google_kms_crypto_key_iam_memberbindings scoped to a single key, so a CMEK consumer gets exactlycryptoKeyEncrypterDecrypteron the one key it needs, never broad ring-wide access. destroy_scheduled_duration(default 30 days) — the real deletion guard: a destroy only schedules key-version destruction, cancellable for 30 days before material is irreversibly gone. The module deliberately does NOT hardcodelifecycle.prevent_destroy(lifecycle meta-args can't be made configurable, and a hardcodedtrueblocks teardown in composition roots and CI) — wrap the module and add your own lifecycle block if you also want plan-time protection.- Regional location encouraged — keep key material within a jurisdiction;
HSM protection (
protection_level = "HSM", FIPS 140-2 L3) available per key.
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/google>= 7.0, < 8.0
License
Commercial — LicenseRef-IaCBazaar-Commercial.
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.
- Lifecycle caveat (important)
- Usage
- Inputs
- Outputs
Related modules
Certificate Manager (certificate map)
A Certificate Manager certificate map for external HTTPS load balancers, with an optional Google-managed certificate and DNS authorization provisioned when you supply a domain you control.
Secret Manager Secrets
Secrets with versions, replication policy, rotation schedules, expiry and accessor IAM.
Azure Key Vault
RBAC-mode Key Vault with private endpoint, diagnostics, and managed keys/secrets/certificates scaffolding.
KMS Key with Policy Patterns
Customer-managed KMS keys with sane key policies, aliases, rotation, and multi-region replicas.
Secrets Manager Secret
Secrets with versioning, resource policies, replication, and optional Lambda rotation scaffolding.
Vault Policies & Auth
Vault policies, auth backends, and secret engine configuration as code.