storage stanza configures the storage backend, which represents the location for the durable storage of Vault's information. Each backend has pros, cons, advantages, and trade-offs. For example, some backends support high availability while others provide a more robust backup and restoration process.
It is also important to note that as of 05/23, only Consul, Integrated Storage (Raft), Filesystem, and In-memory are officially supported by Hashicorp.
In memory storage is not recommended for production installations as data does not persist beyond restarts.
All other storage backends are community supported. This means that while community supported backends have undergone review by HashiCorp employees, they may not be as knowledgeable about the technology. If you encounter problems with this storage backend, you could be referred to the original author for support.
Here's a quick overview of vault storage backends.
|Aerospike||Community||No HA Support|
|Azure||Community||No HA Support|
|Cassandra||Community||No HA Support|
|CockroachDB||Community||No HA Support|
|Consul||Officially Supported||Supports HA|
|CouchDB||Community||No HA Support|
|Filesystem||Officially Supported||No HA Support|
|Google Cloud Spanner||Community||Supports HA|
|Google Cloud Storage||Community||Supports HA|
|In-Memory||Officially Supported||No HA Support|
|Manta||Community||No HA Support|
|MSSQL||Community||No HA Support|
|OCI Object Storage||Community||Supports HA|
|PostgreSQL||Community||Supports HA (9.5+)|
|Integrated Storage (Raft)||Officially Supported||Supports HA|
|S3||Community||No HA Support|
|Swift||Community||No HA Support|