Erica Thompson 0660ea6fac
Update README (#31244)
* Update README

Let contributors know that docs will now be located in UDR

* Add comments to each mdx doc

Comment has been added to all mdx docs that are not partials

* chore: added changelog

changelog check failure

* wip: removed changelog

* Fix content errors

* Doc spacing

* Update website/content/docs/deploy/kubernetes/vso/helm.mdx

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>

---------

Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com>
Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
2025-07-22 08:12:22 -07:00

43 lines
1.5 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
layout: docs
page_title: In-memory storage configuration
description: >-
Configure Vault backend storage to use in-memory storage.
---
> [!IMPORTANT]
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
# In-memory storage configuration for Vault backend storage
The In-Memory storage backend is used to persist Vault's data entirely in-memory
on the same machine in which Vault is running. This is useful for development
and experimentation, but use of this backend is **highly discouraged in
production**. All data is lost when Vault or the machine on which it is running
is restarted.
- **No High Availability** the In-Memory backend does not support high
availability.
- **Not Production Recommended** the In-Memory backend is not recommended for
production installations as data does not persist beyond restarts.
- **HashiCorp Supported** the In-Memory backend is officially supported by
HashiCorp.
```hcl
storage "inmem" {}
```
## `inmem` parameters
The In-Memory storage backend has no configuration parameters.
## `inmem` examples
This example shows activating the In-Memory storage backend.
```hcl
storage "inmem" {}
```