mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 23:21:08 +02:00
0660ea6fac
* 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>
67 lines
2.7 KiB
Plaintext
67 lines
2.7 KiB
Plaintext
---
|
||
layout: docs
|
||
page_title: Manta configuration
|
||
description: >-
|
||
Configure Vault backend storage to use Manta Object Storage from Triton.
|
||
---
|
||
|
||
> [!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.
|
||
|
||
# Manta Object Storage configuration for Vault backend storage
|
||
|
||
The Manta storage backend is used to persist Vault's data in [Triton's Manta Object
|
||
Storage][manta-object-store]. 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.
|
||
|
||
```hcl
|
||
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 variable `MANTA_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 variable `MANTA_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 variable `MANTA_SUBUSER`.
|
||
- `url` – Specifies the Manta URL. Defaults to `https://us-east.manta.joyent.com`. This can also be provided via
|
||
the environment variable `MANTA_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.
|
||
|
||
```hcl
|
||
storage "manta" {
|
||
directory = "vault-storage-directory"
|
||
max_parallel = 512
|
||
}
|
||
```
|
||
|
||
[manta-object-store]: https://www.joyent.com/triton/object-storage
|