* 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
5.1 KiB
layout | page_title | sidebar_title | sidebar_current | description |
---|---|---|---|---|
docs | Google Cloud Spanner - Storage Backends - Configuration | Google Cloud Spanner | docs-configuration-storage-spanner | The Google Cloud Spanner storage backend is used to persist Vault's data in Spanner, a fully managed, mission-critical, relational database service that offers transactional consistency at global scale. |
Google Cloud Spanner Storage Backend
The Google Cloud Spanner storage backend is used to persist Vault's data in Spanner, a fully managed, mission-critical, relational database service that offers transactional consistency at global scale, schemas, SQL, and automatic, synchronous replication for high availability.
-
High Availability – the Google Cloud Spanner storage backend supports high availability. Because the Google Cloud Spanner storage backend uses the system time on the Vault node to acquire sessions, clock skew across Vault servers can cause lock contention.
-
Community Supported – the Google Cloud Spanner 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 "spanner" {
database = "projects/my-project/instances/my-instance/databases/my-database"
}
For more information on schemas or Google Cloud Spanner, please see the Google Cloud Spanner documentation.
spanner
Setup
To use the Google Cloud Spanner Vault storage backend, you must have a Google Cloud Platform account. Either using the API or web interface, create a database and the following tables:
-> You can choose "Edit as text" and copy-paste the following as the schema. These are the default table names. If you choose to use different table names, you will need to update the configuration accordingly.
CREATE TABLE Vault (
Key STRING(MAX) NOT NULL,
Value BYTES(MAX),
) PRIMARY KEY (Key);
CREATE TABLE VaultHA (
Key STRING(MAX) NOT NULL,
Value STRING(MAX),
Identity STRING(36) NOT NULL,
Timestamp TIMESTAMP NOT NULL,
) PRIMARY KEY (Key);
The Google Cloud Spanner storage backend does not support creating the table automatically at this time, but this could be a future enhancement. For more information on schemas or Google Cloud Spanner, please see the Google Cloud Spanner documentation.
spanner
Authentication
The Google Cloud Spanner Vault storage backend uses the official Google Cloud Golang SDK. This means it supports the common ways of providing credentials to Google Cloud.
-
The environment variable
GOOGLE_APPLICATION_CREDENTIALS
. This is specified as the path to a Google Cloud credentials file, typically for a service account. If this environment variable is present, the resulting credentials are used. If the credentials are invalid, an error is returned. -
Default instance credentials. When no environment variable is present, the default service account credentials are used.
For more information on service accounts, please see the Google Cloud Service Accounts documentation.
To use this storage backend, the service account must have the following minimum scope(s):
https://www.googleapis.com/auth/google-cloud-spanner.data
spanner
Parameters
-
database
(string: <required>)
– Specifies the name of the database. Note that this is specified as a "path" including the project ID and instance, for example:projects/my-project/instances/my-instance/databases/my-database
-
table
(string: "Vault")
- Specifies the name of the table where data will be stored and retrieved. -
max_parallel
(int: 128)
- Specifies the maximum number of parallel operations to take place.
High Availability Parameters
-
ha_enabled
(string: "false")
- Specifies if high availability mode is enabled. This is a boolean value, but it is specified as a string like "true" or "false". -
ha_table
(string: "VaultHA")
- Specifies the name of the table to use for storing high availability information. By default, this is the name of thetable
suffixed with "HA".
spanner
Examples
High Availability
This example shows configuring Google Cloud Spanner with high availability enabled.
api_addr = "https://vault-leader.my-company.internal"
storage "spanner" {
database = "projects/demo/instances/abc123/databases/vault-data"
ha_enabled = "true"
}
Custom Tables
This example shows listing custom table names for data and HA with the Google Cloud Spanner Vault storage backend.
storage "spanner" {
database = "projects/demo/instances/abc123/databases/vault-data"
table = "VaultData"
ha_table = "VaultLeader"
}