Vault Secrets Engines Concepts
What you'll learn: How HashiCorp Vault organizes and manages different types of secrets through its secrets engine architecture.
What Are Secrets Engines?
Think of secrets engines as specialized plugins that sit behind different paths in Vault, each designed to handle specific types of secrets or credentials. Just like different departments in an office building occupy different floors, each secrets engine operates at its own distinct path (like /database/, /aws/, or /kv/), and each knows how to work with particular kinds of credentials.
When you mount a secrets engine, you're essentially telling Vault: "At this path, use this specialized handler for these types of secrets."
The Architecture
Vault's secrets engines aren't just storage buckets—they're active components that can:
- Generate dynamic credentials on-demand (database passwords, cloud IAM keys)
- Store static secrets with versioning (the
kvengine) - Encrypt data as a service (the
transitengine) - Issue certificates (the
pkiengine)
Each engine operates independently at its mounted path. For example:
/secret/might host a key-value store for application passwords/database/might dynamically generate MySQL credentials that expire after one hour/aws/might create temporary AWS access keys tied to specific IAM policies
Path-Based Organization
The mounting system means you can have multiple instances of the same engine type at different paths. You might mount separate database/ engines for production and development databases, keeping credentials completely isolated:
/prod-db/→ production database credentials/dev-db/→ development database credentials
Key Takeaway: Vault's secrets engines are specialized, path-mounted components that don't just store secrets—they actively manage, generate, and lifecycle credentials based on the engine type you choose.