a3dfde5cec
* 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
2.4 KiB
| layout | page_title | sidebar_title | sidebar_current | description |
|---|---|---|---|---|
| docs | Manta - Storage Backends - Configuration | Manta | docs-configuration-storage-manta | The Manta storage backend is used to persist Vault's data in Triton's Manta Object Storage. The storage folder must already exist. |
Manta Storage Backend
The Manta storage backend is used to persist Vault's data in Triton's Manta Object Storage. The storage folder must already exist.
-
No High Availability – the Manta storage backend does not support high availability.
-
Community Supported – the Manta storage backend is supported by the community. While it has undergone review by HashiCorp employees, they may not be as knowledgeable about the technology. If you encounter problems with them, you may be referred to the original author.
storage "manta" {
directory = "manta-directory"
user = "myuser"
key_id = "40:9d:d3:f9:0b:86:62:48:f4:2e:a5:8e:43:00:2a:9b"
}
manta Parameters
directory(string: <required>)– Specifies the name of the manta directory to use. This will be in the/stor/folder in the specific manta account
The following settings are used for authenticating to Manta.
-
user(string: <required>)– Specifies the Manta user account name. This can also be provided via the environment variableMANTA_USER. -
key_id(string: <required>)– The fingerprint of the public key of the SSH key pair to use for authentication with the Manta API. It is assumed that the SSH agent has the private key corresponding to this key ID loaded. This can also be provided via the environment variableMANTA_KEY_ID. -
subuser- The name of a subuser that has been granted access to the Manta account. This can also be provided via the environment variableMANTA_SUBUSER. -
url– Specifies the Manta URL. Defaults tohttps://us-east.manta.joyent.com. This can also be provided via the environment variableMANTA_URL. -
max_parallel(string: "128")– Specifies The maximum number of concurrent requests to Manta.
manta Examples
This example shows configuring the Azure storage backend with a custom number of maximum parallel connections.
storage "manta" {
directory = "vault-storage-directory"
max_parallel = 512
}