finds.dev

hashicorp/terraform-aws-vault

A Terraform Module for how to run Vault on AWS using Terraform and Packer

View on GitHub

★ 658HCLApache-2.0updated Jan 2023

// the take

A set of Terraform modules from Gruntwork and HashiCorp for standing up a Vault cluster on AWS, backed by Consul for storage, with Packer-built AMIs, an ASG-based cluster, and an optional ELB for public access. It's aimed at teams running Vault on EC2 who want a proven reference architecture rather than hand-rolling one.

The module split (install-vault, run-vault, vault-cluster, vault-elb, private-tls-cert) cleanly separates AMI-build-time concerns from boot-time and infrastructure concerns, so you can reuse pieces independently. It ships actual automated tests via Terratest covering S3 backend, DynamoDB backend, private/public clusters, and auto-unseal, not just examples that run once and rot. The docs are explicit about production pitfalls, like warning you off the public sample AMIs and spelling out the two-cluster (Consul + Vault) topology instead of hand-waving it.

The README leads with its own deprecation notice: HashiCorp stopped supporting this in 2022 and the last push was January 2023, so there's no one fixing bugs, CVEs in the bundled scripts, or Terraform/provider compatibility issues going forward. It hard-requires a separate Consul cluster as the storage backend, which doubles your operational surface versus just pointing Vault at S3/DynamoDB/Raft integrated storage directly. Anyone adopting this today is building on dead infrastructure code when HashiCorp's own replacement (vault-starter) is sitting right there in the same README; there's no migration path documented between the two.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
658
Forks
445
Language
HCL
License
Apache-2.0
Last commit
25 Jan 2023

// nearby

If terraform-aws-vault isn't quite it.

All repos →