• HashiCorp Developer

  • HashiCorp Cloud Platform
  • Terraform
  • Packer
  • Consul
  • Vault
  • Boundary
  • Nomad
  • Waypoint
  • Vagrant
Vault
  • Install
  • Tutorials
  • Documentation
  • API
  • Integrations
  • Try Cloud(opens in new tab)
  • Sign up
Vault Home

Documentation

Skip to main content
  • Documentation
  • What is Vault?
  • Use Cases

  • Browser Support
  • Installing Vault
    • Overview
    • replication
    • sentinel
      • Overview
      • Aerospike
      • Alicloud OSS
      • Azure
      • Cassandra
      • CockroachDB
      • Consul
      • CouchDB
      • DynamoDB
      • Etcd
      • Filesystem
      • FoundationDB
      • Google Cloud Spanner
      • Google Cloud Storage
      • In-Memory
      • Manta
      • MSSQL
      • MySQL
      • OCI Object Storage
      • PostgreSQL
      • Integrated Storage (Raft)
      • S3
      • Swift
      • Zookeeper
    • telemetry
    • ui
    • Log Completed Requests
    • Entropy Augmentation
      ENTENT
    • kms_library
      ENTENT

  • Vault Integration Program
  • Vault Interoperability Matrix
  • Troubleshoot






  • Glossary


  • Resources

  • Tutorial Library
  • Certifications
  • Community Forum
    (opens in new tab)
  • Support
    (opens in new tab)
  • GitHub
    (opens in new tab)
  1. Developer
  2. Vault
  3. Documentation
  4. Configuration
  5. storage
  6. Manta
  • Vault
  • v1.11.x
  • v1.10.x
  • v1.9.x
  • v1.8.x
  • v1.7.x
  • v1.6.x
  • v1.5.x
  • v1.4.x

»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 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.

storage "manta" {
  directory    = "vault-storage-directory"
  max_parallel = 512
}
Edit this page on GitHub

On this page

  1. Manta Storage Backend
  2. manta Parameters
  3. manta Examples
Give Feedback(opens in new tab)
  • Certifications
  • System Status
  • Terms of Use
  • Security
  • Privacy
  • Trademark Policy
  • Trade Controls
  • Give Feedback(opens in new tab)