← All insightsIntegration

How to use HashiCorp Vault with Terraform

Nir Geier, CodeWizard · 28 April 2025 · 3 min read · Intermediate

HashiCorp Vault and Terraform are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.

Where HashiCorp Vault fits

Vault stores and controls access to secrets, issues short-lived dynamic credentials for databases and clouds, and provides encryption-as-a-service - all behind identity-based policies and a full audit log.

bash
vault secrets enable -path=secret kv-v2
vault kv put secret/app/db password=s3cr3t

cat <<EOF | vault policy write app -
path "secret/data/app/*" { capabilities = ["read"] }
EOF

Where Terraform fits

Terraform describes infrastructure as declarative HCL, builds a dependency graph, and shows a plan of exactly what will change before it applies - across AWS, Azure, GCP and hundreds of providers.

hcl
terraform {
  required_providers { aws = { source = "hashicorp/aws", version = "~> 5.0" } }
  backend "s3" {
    bucket = "acme-tfstate"
    key    = "prod/network.tfstate"
    region = "eu-west-1"
  }
}

variable "env" { type = string, default = "prod" }

resource "aws_s3_bucket" "assets" {
  bucket = "acme-${var.env}-assets"
  tags   = { Environment = var.env }
}

Making them work together

  • Use auth methods (Kubernetes, OIDC, AppRole) with least-privilege policies
  • Prefer dynamic secrets with short TTLs over static ones
  • Remote, locked state; separate state per environment/component
  • Pin provider and module versions; commit .terraform.lock.hcl

Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both HashiCorp Vault and Terraform have active community groups you can join for free.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult