2017-03-08 02:47:23 +00:00
|
|
|
|
---
|
|
|
|
|
layout: "docs"
|
|
|
|
|
page_title: "In-Memory - Storage Backends - Configuration"
|
New Docs Website (#5535)
* conversion stage 1
* correct image paths
* add sidebar title to frontmatter
* docs/concepts and docs/internals
* configuration docs and multi-level nav corrections
* commands docs, index file corrections, small item nav correction
* secrets converted
* auth
* add enterprise and agent docs
* add extra dividers
* secret section, wip
* correct sidebar nav title in front matter for apu section, start working on api items
* auth and backend, a couple directory structure fixes
* remove old docs
* intro side nav converted
* reset sidebar styles, add hashi-global-styles
* basic styling for nav sidebar
* folder collapse functionality
* patch up border length on last list item
* wip restructure for content component
* taking middleman hacking to the extreme, but its working
* small css fix
* add new mega nav
* fix a small mistake from the rebase
* fix a content resolution issue with middleman
* title a couple missing docs pages
* update deps, remove temporary markup
* community page
* footer to layout, community page css adjustments
* wip downloads page
* deps updated, downloads page ready
* fix community page
* homepage progress
* add components, adjust spacing
* docs and api landing pages
* a bunch of fixes, add docs and api landing pages
* update deps, add deploy scripts
* add readme note
* update deploy command
* overview page, index title
* Update doc fields
Note this still requires the link fields to be populated -- this is solely related to copy on the description fields
* Update api_basic_categories.yml
Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages.
* Add bottom hero, adjust CSS, responsive friendly
* Add mega nav title
* homepage adjustments, asset boosts
* small fixes
* docs page styling fixes
* meganav title
* some category link corrections
* Update API categories page
updated to reflect the second level headings for api categories
* Update docs_detailed_categories.yml
Updated to represent the existing docs structure
* Update docs_detailed_categories.yml
* docs page data fix, extra operator page remove
* api data fix
* fix makefile
* update deps, add product subnav to docs and api landing pages
* Rearrange non-hands-on guides to _docs_
Since there is no place for these on learn.hashicorp, we'll put them
under _docs_.
* WIP Redirects for guides to docs
* content and component updates
* font weight hotfix, redirects
* fix guides and intro sidenavs
* fix some redirects
* small style tweaks
* Redirects to learn and internally to docs
* Remove redirect to `/vault`
* Remove `.html` from destination on redirects
* fix incorrect index redirect
* final touchups
* address feedback from michell for makefile and product downloads
2018-10-19 15:40:11 +00:00
|
|
|
|
sidebar_title: "In-Memory"
|
2017-03-08 02:47:23 +00:00
|
|
|
|
sidebar_current: "docs-configuration-storage-in-memory"
|
|
|
|
|
description: |-
|
|
|
|
|
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
|
2017-03-08 14:17:00 +00:00
|
|
|
|
in production except in very specific use-cases.
|
2017-03-08 02:47:23 +00:00
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# In-Memory Storage Backend
|
|
|
|
|
|
|
|
|
|
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
|
2017-03-08 14:17:00 +00:00
|
|
|
|
storage "inmem" {}
|
2017-03-08 02:47:23 +00:00
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
## `inmem` Parameters
|
|
|
|
|
|
|
|
|
|
The In-Memory storage backend has no configuration parameters.
|
|
|
|
|
|
|
|
|
|
## `inmem` Examples
|
|
|
|
|
|
|
|
|
|
This example shows activating the In-Memory storage backend.
|
|
|
|
|
|
|
|
|
|
```hcl
|
2017-03-08 14:17:00 +00:00
|
|
|
|
storage "inmem" {}
|
2017-03-08 02:47:23 +00:00
|
|
|
|
```
|