Type '/' to Search

»Consul Storage Backend

The Consul storage backend is used to persist Vault's data in Consul's key-value store. In addition to providing durable storage, inclusion of this backend will also register Vault as a service in Consul with a default health check.

  • High Availability – the Consul storage backend supports high availability.

  • HashiCorp Supported – the Consul storage backend is officially supported by HashiCorp.

storage "consul" {
  address = "127.0.0.1:8500"
  path    = "vault"
}

storage "consul" {  address = "127.0.0.1:8500"  path    = "vault"}

Once properly configured, an unsealed Vault installation should be available and accessible at:

active.vault.service.consul

active.vault.service.consul

Unsealed Vault instances in standby mode are available at:

standby.vault.service.consul

standby.vault.service.consul

All unsealed Vault instances are available as healthy at:

vault.service.consul

vault.service.consul

Sealed Vault instances will mark themselves as unhealthy to avoid being returned at Consul's service discovery layer.

Note that if you have configured multiple listeners for Vault, you must specify which one Consul should advertise to the cluster using api_addr and cluster_addr (example).

»consul Parameters

  • address (string: "127.0.0.1:8500") – Specifies the address of the Consul agent to communicate with. This can be an IP address, DNS record, or unix socket. It is recommended that you communicate with a local Consul agent; do not communicate directly with a server.

  • check_timeout (string: "5s") – Specifies the check interval used to send health check information back to Consul. This is specified using a label suffix like "30s" or "1h".

  • consistency_mode (string: "default") – Specifies the Consul consistency mode. Possible values are "default" or "strong".

  • disable_registration (string: "false") – Specifies whether Vault should register itself with Consul.

  • max_parallel (string: "128") – Specifies the maximum number of concurrent requests to Consul. Make sure that your Consul agents are configured to support this level of parallelism, see http_max_conns_per_client.

  • path (string: "vault/") – Specifies the path in Consul's key-value store where Vault data will be stored.

  • scheme (string: "http") – Specifies the scheme to use when communicating with Consul. This can be set to "http" or "https". It is highly recommended you communicate with Consul over https over non-local connections. When communicating over a unix socket, this option is ignored.

  • service (string: "vault") – Specifies the name of the service to register in Consul.

  • service_tags (string: "") – Specifies a comma-separated list of tags to attach to the service registration in Consul.

  • service_address (string: nil) – Specifies a service-specific address to set on the service registration in Consul. If unset, Vault will use what it knows to be the HA redirect address - which is usually desirable. Setting this parameter to "" will tell Consul to leverage the configuration of the node the service is registered on dynamically. This could be beneficial if you intend to leverage Consul's translate_wan_addrs parameter.

  • token (string: "") – Specifies the Consul ACL token with permission to read and write from the path in Consul's key-value store. This is not a Vault token. This can also be provided via the environment variable CONSUL_HTTP_TOKEN. See the ACL section below for help.

  • session_ttl (string: "15s") - Specifies the minimum allowed session TTL. Consul server has a lower limit of 10s on the session TTL by default. The value of session_ttl here cannot be lesser than 10s unless the session_ttl_min on the consul server's configuration has a lesser value.

  • lock_wait_time (string: "15s") - Specifies the wait time before a lock acquisition is made. This affects the minimum time it takes to cancel a lock acquisition.

The following settings apply when communicating with Consul via an encrypted connection. You can read more about encrypting Consul connections on the Consul encryption page.

  • tls_ca_file (string: "") – Specifies the path to the CA certificate used for Consul communication. This defaults to system bundle if not specified. This should be set according to the ca_file setting in Consul.

  • tls_cert_file (string: "") (optional) – Specifies the path to the certificate for Consul communication. This should be set according to the cert_file setting in Consul.

  • tls_key_file (string: "") – Specifies the path to the private key for Consul communication. This should be set according to the key_file setting in Consul.

  • tls_min_version (string: "tls12") – Specifies the minimum TLS version to use. Accepted values are "tls10", "tls11", "tls12" or "tls13".

  • tls_skip_verify (string: "false") – Disable verification of TLS certificates. Using this option is highly discouraged.

»ACLs

If using ACLs in Consul, you'll need appropriate permissions. For Consul 0.8, the following will work for most use-cases, assuming that your service name is vault and the prefix being used is vault/:

{
  "key": {
    "vault/": {
      "policy": "write"
    }
  },
  "node": {
    "": {
      "policy": "write"
    }
  },
  "service": {
    "vault": {
      "policy": "write"
    }
  },
  "agent": {
    "": {
      "policy": "write"
    }
  },
  "session": {
    "": {
      "policy": "write"
    }
  }
}

{  "key": {    "vault/": {      "policy": "write"    }  },  "node": {    "": {      "policy": "write"    }  },  "service": {    "vault": {      "policy": "write"    }  },  "agent": {    "": {      "policy": "write"    }  },  "session": {    "": {      "policy": "write"    }  }}

For Consul 1.4+, the following example takes into account the changed ACL language:

{
  "key_prefix": {
    "vault/": {
      "policy": "write"
    }
  },
  "node_prefix": {
    "": {
      "policy": "write"
    }
  },
  "service": {
    "vault": {
      "policy": "write"
    }
  },
  "agent_prefix": {
    "": {
      "policy": "write"
    }
  },
  "session_prefix": {
    "": {
      "policy": "write"
    }
  }
}

{  "key_prefix": {    "vault/": {      "policy": "write"    }  },  "node_prefix": {    "": {      "policy": "write"    }  },  "service": {    "vault": {      "policy": "write"    }  },  "agent_prefix": {    "": {      "policy": "write"    }  },  "session_prefix": {    "": {      "policy": "write"    }  }}

»consul Examples

»Local Agent

This example shows a sample physical backend configuration which communicates with a local Consul agent running on 127.0.0.1:8500.

storage "consul" {}

storage "consul" {}

»Detailed Customization

This example shows communicating with Consul on a custom address with an ACL token.

storage "consul" {
  address = "10.5.7.92:8194"
  token   = "abcd1234"
}

storage "consul" {  address = "10.5.7.92:8194"  token   = "abcd1234"}

»Custom Storage Path

This example shows storing data at a custom path in Consul's key-value store. This path must be readable and writable by the Consul ACL token, if Consul configured to use ACLs.

storage "consul" {
  path = "vault/"
}

storage "consul" {  path = "vault/"}

»Consul via Unix Socket

This example shows communicating with Consul over a local unix socket.

storage "consul" {
  address = "unix:///tmp/.consul.http.sock"
}

storage "consul" {  address = "unix:///tmp/.consul.http.sock"}

»Custom TLS

This example shows using a custom CA, certificate, and key file to securely communicate with Consul over TLS.

storage "consul" {
  scheme        = "https"
  tls_ca_file   = "/etc/pem/vault.ca"
  tls_cert_file = "/etc/pem/vault.cert"
  tls_key_file  = "/etc/pem/vault.key"
}

storage "consul" {  scheme        = "https"  tls_ca_file   = "/etc/pem/vault.ca"  tls_cert_file = "/etc/pem/vault.cert"  tls_key_file  = "/etc/pem/vault.key"}