open-vault/website/source/docs/configuration/storage/postgresql.html.md
Seth Vargo 624c6eab20 Separate backend configurations into their own pages (#2454)
* Clean vertical lines

* Make sidebar slightly larger on bigger displays

* Separate backend configurations into their own pages
2017-03-07 21:47:23 -05:00

2.4 KiB
Raw Blame History

layout page_title sidebar_current description
docs PostgreSQL - Storage Backends - Configuration docs-configuration-storage-postgresql The PostgreSQL storage backend is used to persist Vault's data in a PostgreSQL server or cluster.

PostgreSQL Storage Backend

The PostgreSQL storage backend is used to persist Vault's data in a PostgreSQL server or cluster.

  • No High Availability the PostgreSQL storage backend does not support high availability.

  • Community Supported the PostgreSQL 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.

backend "postgresql" {
  connection_url = "postgres://user123:secret123!@localhost:5432/vault"
}

The PostgresSQL storage backend does not automatically create the table. Here is some sample SQL to create the schema and indexes.

CREATE TABLE vault_kv_store (
  parent_path TEXT COLLATE "C" NOT NULL,
  path        TEXT COLLATE "C",
  key         TEXT COLLATE "C",
  value       BYTEA,
  CONSTRAINT pkey PRIMARY KEY (path, key)
);

CREATE INDEX parent_path_idx ON vault_kv_store (parent_path);

postgresql Parameters

  • connection_url (string: <required>)  Specifies the connection string to use to authenticate and connect to PostgreSQL. A full list of supported parameters can be found in the pq library documentation. For example connection string URLs, see the examples section below.

  • table (string: "vault_kv_store") Specifies the name of the table in which to write Vault data. This table must already exist (Vault will not attempt to create it).

postgresql Examples

Custom SSL Verification

This example shows connecting to a PostgresSQL cluster using full SSL verification (recommended).

backend "postgresql" {
  connection_url = "postgres://user:pass@localhost:5432/database?sslmode=verify-full"
}

To disable SSL verification (not recommended), replace verify-full with disable:

backend "postgresql" {
  connection_url = "postgres://user:pass@localhost:5432/database?sslmode=disable"
}