content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
# S3 configuration for Vault backend storage The S3 storage backend is used to persist Vault's data in an [Amazon S3][s3] bucket. - \*\*No High Availability\*\* β the S3 storage backend does not support high availability. - \*\*Community Supported\*\* β the S3 storage backend is supported by the community. While it has... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/s3.mdx | main | vault | [
0.002895525423809886,
-0.012839984148740768,
-0.10652783513069153,
-0.04559258371591568,
-0.001175698242150247,
-0.025620756670832634,
-0.039634909480810165,
-0.021672289818525314,
0.061586275696754456,
-0.018059231340885162,
0.02855001389980316,
0.009317107498645782,
0.10506828129291534,
... | -0.020928 |
# FoundationDB configuration for Vault backend storage The FoundationDB storage backend is used to persist Vault's data in [FoundationDB][foundationdb]. The backend needs to be explicitly enabled at build time, and is not available in the standard Vault binary distribution. Please refer to the documentation accompanyin... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/foundationdb.mdx | main | vault | [
0.05089815333485603,
-0.041227035224437714,
-0.1004515141248703,
0.014845199882984161,
0.030343323945999146,
-0.06766553223133087,
-0.07726242393255234,
-0.005412998143583536,
0.018701400607824326,
-0.016921062022447586,
0.012502518482506275,
0.004224903415888548,
0.07977739721536636,
-0.0... | -0.014926 |
linker at the location of the primary client library. ```shell-session $ export LD\_LIBRARY\_PATH=/dest/dir/for/primary:$LD\_LIBRARY\_PATH $ export FDB\_NETWORK\_OPTION\_EXTERNAL\_CLIENT\_DIRECTORY=/dest/dir/for/secondary $ /path/to/bin/vault ... ``` #### Client setup with `RPATH` When running Vault with mlock, the Vau... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/foundationdb.mdx | main | vault | [
0.024765584617853165,
-0.04518025740981102,
-0.07073403149843216,
-0.011622103862464428,
0.044284697622060776,
0.014225218445062637,
-0.020548731088638306,
0.07616063952445984,
-0.002490791492164135,
-0.05663721263408661,
0.036159008741378784,
-0.001468649716116488,
0.006068772170692682,
0... | -0.095655 |
# CockroachDB configuration for Vault backend storage The CockroachDB storage backend is used to persist Vault's data in a [CockroachDB][cockroachdb] server or cluster. - \*\*High Availability\*\* β the CockroachDB storage backend supports high availability. - \*\*Community Supported\*\* β the CockroachDB storage backe... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/cockroachdb.mdx | main | vault | [
0.04176817834377289,
-0.045244406908750534,
-0.16137483716011047,
-0.0033968971110880375,
-0.09428346902132034,
-0.0011469871969893575,
-0.04772673174738884,
-0.01991385780274868,
0.019534150138497353,
-0.058075569570064545,
-0.0013215939980000257,
0.027082543820142746,
0.03227076306939125,
... | 0.003942 |
# File system configuration for Vault backend storage The Filesystem storage backend stores Vault's data on the filesystem using a standard directory structure. It can be used for durable single server situations, or to develop locally where durability is not critical. - \*\*No High Availability\*\* β the Filesystem ba... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/filesystem.mdx | main | vault | [
0.006683166138827801,
0.03008272685110569,
-0.11005561053752899,
-0.02072947286069393,
-0.006168747786432505,
-0.04200447350740433,
-0.07571297138929367,
0.08941720426082611,
0.02341998554766178,
-0.034817103296518326,
0.040385302156209946,
0.06202980875968933,
0.0900111123919487,
-0.02358... | -0.029952 |
# Aerospike configuration for Vault backend storage The Aerospike storage backend is used to persist Vault's data in an [Aerospike][aerospike] cluster. - \*\*No High Availability\*\* β the Aerospike backend does not support high availability. - \*\*Community Supported\*\* β the Aerospike storage backend is supported by... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/aerospike.mdx | main | vault | [
0.10308118164539337,
0.0569772832095623,
-0.09458567202091217,
-0.04195693880319595,
-0.008369917050004005,
-0.06506409496068954,
-0.02986093796789646,
-0.01763135939836502,
-0.0005562995211221278,
-0.03329168260097504,
0.04885325953364372,
0.006917462218552828,
0.03429821878671646,
0.0281... | -0.047821 |
# Alicloud OSS configuration for Vault backend storage The Alicloud OSS storage backend is used to persist Vault's data in an [Alicloud OSS][alicloudoss] bucket. - \*\*No High Availability\*\* β the Alicloud OSS storage backend does not support high availability. - \*\*Community Supported\*\* β the Alicloud OSS storage... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/alicloudoss.mdx | main | vault | [
-0.002746745478361845,
0.005378927104175091,
-0.07114766538143158,
-0.015581707470119,
-0.009507364593446255,
-0.06363395601511002,
-0.018168119713664055,
-0.028321225196123123,
0.07237225025892258,
-0.03761472925543785,
0.05666893348097801,
0.02208700217306614,
0.08402712643146515,
-0.061... | 0.011659 |
# `storage` stanza The `storage` stanza configures the storage backend, which represents the location for the durable storage of Vault's information. Each backend has pros, cons, advantages, and trade-offs. For example, some backends support high availability while others provide a more robust backup and restoration pr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/index.mdx | main | vault | [
0.023691587150096893,
0.011750462464988232,
-0.09307105094194412,
-0.002915026852861047,
-0.008602212183177471,
-0.08533427119255066,
-0.04792723059654236,
0.08855360001325607,
0.002167067024856806,
-0.06827102601528168,
0.04398069903254509,
0.03332960233092308,
0.09907462447881699,
-0.048... | 0.019642 |
Storage Reference Architecture](/vault/tutorials/day-one-consul/reference-architecture#recommended-architecture) guide. | | Data location | Data is on disk. | All data is in memory. | | System requirements | [System requirements](/vault/tutorials/day-one-raft/raft-reference-architecture#system-requirements) | [System r... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/index.mdx | main | vault | [
0.041927505284547806,
0.03734256699681282,
-0.1029714047908783,
-0.037240367382764816,
-0.0527348518371582,
-0.11118624359369278,
-0.061600252985954285,
0.09862306714057922,
-0.037441134452819824,
0.013601533137261868,
0.022791050374507904,
0.018405113369226456,
0.04045582190155983,
-0.018... | 0.037298 |
# Etcd configuration for Vault backend storage The Etcd storage backend is used to persist Vault's data in [Etcd][etcd]. It supports both the v2 and v3 Etcd APIs, and the version is automatically detected based on the version of the Etcd cluster. ~> The Etcd v2 API has been deprecated with the release of Etcd v3.5, and... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/etcd.mdx | main | vault | [
-0.046022288501262665,
0.027205048128962517,
-0.039026934653520584,
-0.05146053805947304,
0.058793507516384125,
-0.005660425405949354,
-0.11312149465084076,
-0.0786169096827507,
-0.03175964206457138,
-0.02823960781097412,
0.058069802820682526,
0.08012460172176361,
0.013963124714791775,
0.0... | -0.055588 |
need faster recovery. - `max\_receive\_size` `(int)` β Specifies the client-side response receive limit. Make sure that "max\_receive\_size" >= server-side default send/recv limit. ("--max-request-bytes" flag to etcd or "embed.Config.MaxRequestBytes"). - `max\_send\_size` `(int)` β Specifies the client-side request sen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/etcd.mdx | main | vault | [
-0.023926807567477226,
0.036679793149232864,
0.009507057256996632,
-0.04247356578707695,
-0.022862175479531288,
-0.02739991992712021,
-0.06191137060523033,
0.009555365890264511,
-0.028961917385458946,
-0.009568200446665287,
-0.0012973039411008358,
0.052024513483047485,
0.07047710567712784,
... | -0.04974 |
# DynamoDB configuration for Vault backend storage The DynamoDB storage backend is used to persist Vault's data in [DynamoDB][dynamodb] table. - \*\*High Availability\*\* β the DynamoDB storage backend supports high availability. Because DynamoDB uses the time on the Vault node to implement the session lifetimes on its... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/dynamodb.mdx | main | vault | [
0.01300614420324564,
0.011202788911759853,
-0.07265016436576843,
0.022817514836788177,
-0.0018494587857276201,
-0.05053029581904411,
-0.0747595876455307,
-0.009641676209867,
0.034170616418123245,
-0.005129361059516668,
-0.01131773367524147,
0.02516457438468933,
0.12393757700920105,
-0.0960... | -0.055763 |
also be provided via the environment variable `AWS\_SECRET\_ACCESS\_KEY`. - `session\_token` `(string: "")` β Specifies the AWS session token. This can also be provided via the environment variable `AWS\_SESSION\_TOKEN`. ## Required AWS permissions The governing policy for the IAM user or EC2 instance profile that Vaul... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/dynamodb.mdx | main | vault | [
0.017099682241678238,
0.04521787166595459,
-0.07111866772174835,
0.01019168458878994,
0.014277033507823944,
-0.035922516137361526,
0.022458141669631004,
0.038844913244247437,
0.04552193731069565,
0.005621377844363451,
-0.00969678070396185,
-0.06858974695205688,
0.13588973879814148,
-0.0060... | -0.048263 |
# In-memory storage configuration for Vault backend storage The In-Memory storage backend is used to persist Vault's data entirely in-memory on the same machine in which Vault is running. This is useful for development and experimentation, but use of this backend is \*\*highly discouraged in production\*\*. All data is... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/in-memory.mdx | main | vault | [
0.023756613954901695,
-0.005595484748482704,
-0.13208292424678802,
0.005941454786807299,
-0.029184691607952118,
-0.03396996110677719,
-0.019363585859537125,
0.04507268965244293,
0.008851348422467709,
-0.03331180289387703,
0.06881234049797058,
0.03915902599692345,
0.1129133552312851,
-0.035... | 0.082514 |
# Consul configuration for Vault backend storage The Consul storage backend is used to persist Vault's data in [Consul's][consul] 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. @include 'consul-dataplane-c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/consul.mdx | main | vault | [
0.016983725130558014,
0.004031506832689047,
-0.10491953045129776,
-0.030842449516057968,
-0.03468579053878784,
-0.06228496879339218,
-0.05029745399951935,
0.05076918005943298,
0.01761746034026146,
-0.003580958116799593,
0.03887716308236122,
0.053757015615701675,
0.05820265784859657,
0.0059... | -0.004329 |
allowed [session TTL][consul-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 ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/consul.mdx | main | vault | [
-0.05286034941673279,
0.0173796396702528,
-0.07593048363924026,
-0.05520213022828102,
-0.04445166140794754,
-0.02112872526049614,
0.003368579549714923,
0.05769171938300133,
0.09715759754180908,
0.06855440884828568,
0.03903898596763611,
0.006285918410867453,
-0.012530102394521236,
0.0633828... | 0.032646 |
# 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. - \*\*Com... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/manta.mdx | main | vault | [
0.011947481893002987,
0.021393602713942528,
-0.13131850957870483,
-0.0401272214949131,
-0.10507966578006744,
-0.07933472841978073,
0.007142126094549894,
-0.031499654054641724,
0.0031784935854375362,
-0.028835972771048546,
0.09431052207946777,
-0.032484278082847595,
0.0401151143014431,
0.02... | 0.027322 |
# Integrated storage (Raft) backend The Integrated Storage backend is used to persist Vault's data. Unlike other storage backends, Integrated Storage does not operate from a single source of data. Instead all the nodes in a Vault cluster will have a replicated copy of Vault's data. Data gets replicated across all the n... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/raft.mdx | main | vault | [
0.007829041220247746,
0.01606171764433384,
-0.10173552483320236,
0.007980285212397575,
-0.027707330882549286,
-0.1191788911819458,
-0.06239217147231102,
-0.0027258452028036118,
0.0008788661798462272,
-0.038965124636888504,
0.06531485170125961,
0.014314153231680393,
0.09244614094495773,
-0.... | 0.074159 |
that should rarely need to be changed. Very busy clusters experiencing excessive disk IO may increase this value to reduce disk IO and minimize the chances of all servers taking snapshots at the same time. Increasing this trades off disk IO for disk space since the log will grow much larger and the space in the `raft.d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/raft.mdx | main | vault | [
-0.017170865088701248,
-0.014977577142417431,
-0.026778435334563255,
0.011111581698060036,
0.05331122875213623,
-0.11558207124471664,
-0.04762895777821541,
0.00011282399646006525,
0.01594807393848896,
0.021520616486668587,
0.01780635491013527,
0.08177709579467773,
-0.009921502321958542,
-0... | 0.080098 |
namespace configuration data. If you are reaching limits on the mount table size, you can use this to increase the number of mounts and namespaces that can be stored without the risk of other storage entries becoming too large. All other notes on [`max\_entry\_size`](#max-entry-size) apply. Before changing this, read t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/raft.mdx | main | vault | [
-0.004064538050442934,
-0.018067533150315285,
-0.027098331600427628,
-0.029912235215306282,
-0.030391402542591095,
-0.07816644757986069,
-0.03675340116024017,
0.006991867441684008,
-0.009374051354825497,
0.040749259293079376,
0.013933563604950905,
-0.012913685292005539,
0.06787355244159698,
... | 0.038381 |
with the possible leader node. - `leader\_client\_key` `(string: "")` - Client key for the follower node to establish client authentication with the possible leader node. Each [`retry\_join`](#retry\_join-stanza) block may provide TLS certificates via file paths or as a single-line certificate string value with newline... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/raft.mdx | main | vault | [
-0.01734127849340439,
0.038270678371191025,
-0.014086936600506306,
-0.008994455449283123,
-0.010194685310125351,
-0.046947140246629715,
-0.013300543650984764,
-0.03390806168317795,
0.07125406712293625,
-0.017387576401233673,
0.0017945388099178672,
0.01566363498568535,
0.12808726727962494,
... | -0.08765 |
# Google Cloud Spanner configuration for Vault backend storage The Google Cloud Spanner storage backend is used to persist Vault's data in [Spanner][spanner-docs], a fully managed, mission-critical, relational database service that offers transactional consistency at global scale, schemas, SQL, and automatic, synchrono... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/google-cloud-spanner.mdx | main | vault | [
-0.061895422637462616,
-0.030181657522916794,
-0.046747881919145584,
-0.01563260331749916,
-0.013958917930722237,
-0.0636182501912117,
-0.07402738928794861,
-0.06690561771392822,
0.026786664500832558,
0.004881152883172035,
0.035927366465330124,
0.05972821265459061,
0.11984507739543915,
-0.... | -0.052724 |
with "HA". ## `spanner` examples ### High availability This example shows configuring Google Cloud Spanner with high availability enabled. ```hcl api\_addr = "https://vault-leader.my-company.internal" storage "spanner" { database = "projects/demo/instances/abc123/databases/vault-data" ha\_enabled = "true" } ``` ### Cus... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/google-cloud-spanner.mdx | main | vault | [
-0.051181621849536896,
0.000046878143621142954,
-0.06409275531768799,
-0.00643674423918128,
-0.06428422778844833,
-0.015952736139297485,
-0.029856733977794647,
-0.03818627446889877,
-0.009789064526557922,
0.02127186208963394,
0.05141805112361908,
-0.07000647485256195,
0.11848445981740952,
... | -0.190615 |
# Azure configuration for Vault backend storage The Azure storage backend is used to persist Vault's data in an [Azure Storage Container][azure-storage]. The storage container must already exist and the provided account credentials must have read and write permissions to the storage container. The storage account type ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/azure.mdx | main | vault | [
0.02676217444241047,
0.0109087023884058,
-0.1027078852057457,
0.005196076817810535,
-0.040710724890232086,
-0.01946662925183773,
-0.0005426781135611236,
-0.047202885150909424,
0.03351689502596855,
0.035979993641376495,
0.03771379217505455,
0.012109373696148396,
0.08820907771587372,
0.02409... | -0.033072 |
# Microsoft SQL Server configuration for Vault backend storage The MSSQL storage backend is used to persist Vault's data in a Microsoft SQL Server. - \*\*No High Availability\*\* β the MSSQL storage backend does not support high availability. - \*\*Community Supported\*\* β the MSSQL storage backend is supported by the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/mssql.mdx | main | vault | [
0.041888076812028885,
-0.04297950491309166,
-0.132612407207489,
0.012178360484540462,
-0.08311200141906738,
-0.04102424904704094,
-0.019934337586164474,
-0.018066177144646645,
0.0021635987795889378,
-0.004453569650650024,
0.04328933358192444,
0.061675939708948135,
0.10181601345539093,
0.00... | -0.036393 |
# OCI Object Storage configuration for Vault backend storage The OCI Object Storage backend is used to persist Vault's data in OCI Object Storage. - \*\*High Availability\*\* β the OCI Object Storage backend supports high availability. - \*\*Community Supported\*\* β the OCI Object Storage backend is supported by the c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/oci-object-storage.mdx | main | vault | [
-0.00767291896045208,
0.015524615533649921,
-0.09797090291976929,
-0.010930194519460201,
-0.04320240020751953,
-0.13185690343379974,
-0.022092610597610474,
0.011626889929175377,
0.05762089416384697,
-0.0739416629076004,
0.039838310331106186,
-0.032778069376945496,
0.04754073545336723,
-0.0... | 0.056427 |
# Swift configuration for Vault backend storage The Swift storage backend is used to persist Vault's data in an [OpenStack Swift Container][swift]. - \*\*No High Availability\*\* β the Swift storage backend does not support high availability. - \*\*Community Supported\*\* β the Swift storage backend is supported by the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/swift.mdx | main | vault | [
0.04165767878293991,
-0.04199476167559624,
-0.09611634910106659,
0.02939058095216751,
-0.019041990861296654,
-0.05306657403707504,
-0.006808296777307987,
-0.018656421452760696,
-0.022215433418750763,
-0.05632419511675835,
0.03961081802845001,
-0.0051885261200368404,
0.04067904129624367,
0.... | -0.007028 |
# CouchDB configuration for Vault backend storage The CouchDB storage backend is used to persist Vault's data in [CouchDB][couchdb] table. - \*\*No High Availability\*\* β the CouchDB backend does not support high availability. - \*\*Community Supported\*\* β the CouchDB storage backend is supported by the community. W... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/couchdb.mdx | main | vault | [
0.05376476049423218,
-0.0031127212569117546,
-0.04680856689810753,
-0.021873196586966515,
-0.04331141710281372,
-0.015176458284258842,
-0.09547562897205353,
-0.02190370112657547,
0.030789105221629143,
-0.01989077590405941,
-0.01342400349676609,
0.04978986084461212,
0.1043713167309761,
-0.0... | -0.062331 |
# MySQL configuration for Vault backend storage The MySQL storage backend is used to persist Vault's data in a [MySQL][mysql] server or cluster. - \*\*High Availability\*\* β the MySQL storage backend supports high availability. Note that due to the way mysql locking functions work they are lost if a connection dies. I... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/mysql.mdx | main | vault | [
0.05208033695816994,
0.004342463333159685,
-0.09134716540575027,
0.005461331456899643,
-0.07177850604057312,
-0.050844352692365646,
-0.0165916346013546,
0.01692327670753002,
-0.007583100348711014,
-0.015997756272554398,
0.009906518273055553,
0.026456154882907867,
0.16537757217884064,
-0.03... | 0.008619 |
# Cassandra configuration for Vault backend storage The Cassandra storage backend is used to persist Vault's data in an [Apache Cassandra][cassandra] cluster. - \*\*No High Availability\*\* β the Cassandra storage backend does not support high availability. - \*\*Community Supported\*\* β the Cassandra storage backend ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/cassandra.mdx | main | vault | [
0.03236839175224304,
-0.04398944228887558,
-0.10727027803659439,
0.030877385288476944,
-0.09439080208539963,
-0.029743103310465813,
-0.0923423171043396,
-0.0051570069044828415,
0.031733617186546326,
-0.014853396452963352,
0.03428487852215767,
-0.025759661570191383,
0.13603302836418152,
-0.... | -0.03357 |
# PostgreSQL configuration for Vault backend storage The PostgreSQL storage backend is used to persist Vault's data in a [PostgreSQL][postgresql] server or cluster. - \*\*High Availability\*\* β the PostgreSQL storage backend supports high availability. Requires PostgreSQL 9.5 or later. - \*\*Community Supported\*\* β ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/postgresql.mdx | main | vault | [
0.023434827104210854,
-0.0030335946939885616,
-0.12194448709487915,
0.002332541858777404,
-0.08613991737365723,
-0.049378205090761185,
-0.05163807049393654,
-0.024007588624954224,
0.03401150554418564,
-0.02993692271411419,
0.0045422823168337345,
0.07821713387966156,
0.03402936831116676,
-0... | -0.013951 |
the AWS region where DB is situated. Required when `auth\_mode` is set to `aws\_iam` - `azure\_client\_id` `(string: "")` - Client ID of a user-assigned Managed Service Identity in Azure. System-assigned Managed Service Identity is used if `azure\_client\_id` is not provided and `auth\_mode` is set to `azure\_msi`. ## ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/postgresql.mdx | main | vault | [
0.014385097660124302,
0.0472133569419384,
-0.05092509463429451,
0.025352107360959053,
-0.06175705045461655,
0.0023618757259100676,
0.07202941924333572,
-0.11724192649126053,
0.11321818828582764,
0.06563332676887512,
-0.012487012892961502,
-0.004751661792397499,
0.10472200810909271,
0.05310... | -0.05646 |
# Google Cloud Storage configuration for Vault backend storage The Google Cloud Storage storage backend is used to persist Vault's data in [Google Cloud Storage][gcs-docs]. - \*\*High Availability\*\* β the Google Cloud Storage storage backend supports high availability. Because the Google Cloud Storage storage backend... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/google-cloud-storage.mdx | main | vault | [
-0.03476205840706825,
-0.02405616082251072,
-0.035157665610313416,
-0.03463025018572807,
-0.031165244057774544,
-0.03403192013502121,
-0.031145373359322548,
-0.03636641427874565,
0.03255816176533699,
0.020453525707125664,
0.016789434477686882,
0.03744833171367645,
0.06020129844546318,
-0.0... | -0.084115 |
not retry any failures. If you are not storing large objects in Vault, it is recommended to set this to a low value (minimum is 256), since it will reduce the amount of memory Vault uses. Alternatively, this parameter can be omitted and the `GOOGLE\_STORAGE\_CHUNK\_SIZE` environment variable can be used to set the chun... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/google-cloud-storage.mdx | main | vault | [
-0.026666637510061264,
0.007968921214342117,
-0.00964666623622179,
0.012365109287202358,
-0.04755570366978645,
-0.055814582854509354,
-0.02193298749625683,
-0.01811429299414158,
-0.08919396996498108,
0.009734281338751316,
0.041148941963911057,
-0.01174646895378828,
0.054323501884937286,
-0... | -0.069576 |
# Zookeeper configuration for Vault backend storage The Zookeeper storage backend is used to persist Vault's data in [Zookeeper][zk]. - \*\*High Availability\*\* β the Zookeeper storage backend supports high availability. - \*\*Community Supported\*\* β the Zookeeper storage backend is supported by the community. While... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/zookeeper.mdx | main | vault | [
0.00019613261974882334,
0.056665822863578796,
-0.08330819010734558,
0.004052585456520319,
0.003349174279719591,
-0.07745334506034851,
-0.01649298705160618,
-0.018876969814300537,
-0.006466382183134556,
-0.01344566885381937,
0.007067346479743719,
-0.0356256477534771,
0.10566446185112,
0.042... | 0.00295 |
this is the `ip` no `auth\_info` is required since Zookeeper uses the address of the client for the ACL check. ```hcl storage "zookeeper" { znode\_owner = "ip:127.0.0.1" } ``` ### zNode connection over TLS. This example instructs Vault to connect to Zookeeper using the provided TLS configuration. The host verification ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/storage/zookeeper.mdx | main | vault | [
0.004625020548701286,
0.12010359764099121,
-0.05013526603579521,
-0.006448914296925068,
0.000985868857242167,
-0.11516258120536804,
0.025543542578816414,
-0.05387035757303238,
0.04021043702960014,
-0.010726956650614738,
-0.04363180696964264,
-0.08733465522527695,
0.12403744459152222,
0.092... | -0.069043 |
# Rollback a Vault upgrade Vault supports in-place upgrades but does not support automatic rollbacks. ## Before you start - \*\*You must have `sudo` permissions on the Vault server\*\*. Make sure you have can install binaries on the Vault server. - \*\*You must have admin permissions for Vault\*\*. Make sure you can st... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/upgrade/rollback.mdx | main | vault | [
0.06600480526685715,
0.02995939366519451,
-0.042512260377407074,
-0.036403119564056396,
-0.042501624673604965,
0.005240360274910927,
-0.06405983120203018,
-0.057899557054042816,
-0.03363146260380745,
0.041410770267248154,
0.044118691235780716,
0.06936750560998917,
0.06932828575372696,
0.03... | -0.130804 |
# Upgrade Vault Vault supports in-place upgrades and automatically handles most tasks when you unseal Vault after the upgrade. If you plan to move from Vault Community to Vault Enterprise during your upgrade, make sure to download an enterprise binary and apply your [license file](/vault/api-docs/system/license#install... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/upgrade/index.mdx | main | vault | [
0.061383359134197235,
-0.008312676101922989,
-0.015456793829798698,
-0.05039745196700096,
-0.011779433116316795,
-0.05154387652873993,
-0.08456060290336609,
-0.0395364835858345,
-0.03237350285053253,
-0.02201130799949169,
0.010529067367315292,
-0.0048705837689340115,
0.03520864248275757,
0... | -0.03878 |
# Upgrade replicated Vault deployments Upgrade your replicated Vault deployment. ## HA installations The recommended upgrade procedure depends on the version of Vault you're currently on and the storage backend of Vault. If you're currently running on Vault 1.11 or later with Integrated Storage and you have Autopilot e... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/upgrade/replicated-deployment.mdx | main | vault | [
0.019279982894659042,
-0.0019100402714684606,
-0.03876057639718056,
-0.08301543444395065,
0.01916971616446972,
-0.10534986853599548,
-0.06083272397518158,
0.01309348363429308,
-0.08033549785614014,
0.02638363651931286,
0.065180703997612,
0.016741398721933365,
0.05184468626976013,
-0.018263... | -0.087849 |
ensure that the upgrade will be successful in your environment. The ideal way to do this is to take a snapshot of your data and load it into a test cluster. However, if you are issuing secrets to third party resources (cloud credentials, database credentials, etc.) ensure that you do not allow external network connecti... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/upgrade/replicated-deployment.mdx | main | vault | [
0.05133196339011192,
-0.014172108843922615,
0.03743211552500725,
-0.058521416038274765,
0.04926338046789169,
-0.0811753123998642,
-0.09397907555103302,
-0.09249319136142731,
-0.04330059885978699,
0.050173353403806686,
0.06567289680242538,
0.010989520698785782,
0.013909181579947472,
-0.0513... | -0.048113 |
# Upgrade integrated storage to use Raft WAL @include 'alerts/experimental.mdx' ## Before you start - \*\*You must be using Vault 1.16+\*\*. - \*\*You must be using Raft integrated storage\*\*. ## Step 1: Migrate a single node 1. Take a snapshot of the current node state. Snapshots are completely separate from log stor... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/upgrade/raft-wal.mdx | main | vault | [
0.0404733270406723,
-0.009125027805566788,
-0.050680648535490036,
-0.02336578443646431,
0.05522870272397995,
-0.14104872941970825,
-0.047010909765958786,
0.009295409545302391,
-0.061829373240470886,
0.0156814306974411,
0.0024141890462487936,
0.029011819511651993,
0.09577121585607529,
0.000... | -0.092536 |
# Vault HA upgrades without Autopilot upgrade automation (Pre 1.11) This is our recommended upgrade procedure if \*\*one\*\* of the following applies: - Running Vault version earlier than 1.11 - Opt-out the [Autopilot automated upgrade](/vault/docs/concepts/integrated-storage/autopilot#automated-upgrade) features with ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/upgrade/vault-ha-upgrade.mdx | main | vault | [
-0.03220467269420624,
0.02941274270415306,
-0.06943968683481216,
-0.048936452716588974,
-0.019959568977355957,
-0.0658857673406601,
-0.03217323124408722,
0.024341706186532974,
-0.02569950558245182,
0.03525682911276817,
0.01714514195919037,
0.03678639605641365,
0.06607017666101456,
-0.03064... | -0.028034 |
upgraded standby nodes takes over active duty. Be sure to also read and follow any instructions in the version-specific upgrade notes. ## Enterprise replication installations See the main [upgrading](/vault/docs/upgrading#enterprise-replication-installations) page. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/upgrade/vault-ha-upgrade.mdx | main | vault | [
0.052330419421195984,
-0.06823071837425232,
0.00101707992143929,
-0.0272656437009573,
0.05791323259472847,
-0.05716359242796898,
-0.10898181051015854,
-0.04942910745739937,
-0.06909670680761337,
0.06579194962978363,
0.00866449624300003,
0.14006391167640686,
0.05209220573306084,
-0.10926467... | 0.018155 |
# Why use Agent or Proxy? A valid client token must accompany most requests to Vault. This includes all API requests, as well as via the Vault CLI and other libraries. Therefore, Vault clients must first authenticate with Vault to acquire a token. Vault provides several authentication methods to assist in delivering th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/index.mdx | main | vault | [
-0.03726138174533844,
0.049486130475997925,
-0.0397186279296875,
-0.041670165956020355,
-0.042739253491163254,
-0.052583660930395126,
-0.018902119249105453,
0.06220187991857529,
0.08620642125606537,
-0.05214822664856911,
0.01268771942704916,
0.05150052160024643,
0.09687149524688721,
0.0339... | 0.011917 |
Vault API | Deprecated | β
| | [Static secret caching][static-secret-caching] for KV secrets | β | β
| To learn more, refer to the [Vault Agent][vaultagent] or [Vault Proxy][vaultproxy] documentation page. ## Tutorial Refer to the [Vault Agent](/vault/tutorials/vault-agent) tutorials for end-to-end examples. [autoauth]... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/index.mdx | main | vault | [
-0.011656786315143108,
0.04234005883336067,
-0.08949330449104309,
-0.03759993240237236,
-0.045128822326660156,
-0.0343686006963253,
-0.042636942118406296,
0.012284557335078716,
-0.01030780840665102,
-0.03477020561695099,
-0.002037342404946685,
0.0372975654900074,
0.04045460745692253,
0.016... | 0.00313 |
# What is Auto-authentication? Auto-authentication simplifies client authentication in a wide variety of environments. The following Vault tools come with auto-authentication built in: - Vault Agent - Vault Proxy ## Methods and sinks Auto-auth consists of two parts: - a \*\*method\*\* - the desired authentication metho... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/index.mdx | main | vault | [
-0.08896217495203018,
0.0063955713994801044,
-0.0321439690887928,
0.024456797167658806,
-0.027679195627570152,
-0.033159248530864716,
0.0317218080163002,
-0.0012362124398350716,
0.047957394272089005,
-0.012571373023092747,
0.0034305297303944826,
0.03691672161221504,
0.023866282775998116,
0... | 0.131228 |
is written as part of the AES-GCM tag and must match on both Agent and Proxy and the client. This of course means that protecting this AAD becomes important, but it provides another layer for an attacker to have to overcome. For instance, if the attacker has access to the file system where the token is being written, b... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/index.mdx | main | vault | [
-0.0786648765206337,
0.012711839750409126,
-0.03896121680736542,
0.01029637549072504,
-0.06647700816392899,
-0.005446262191981077,
0.06375094503164291,
-0.040811311453580856,
0.034517429769039154,
0.0852927416563034,
0.013587143272161484,
0.0646289512515068,
0.03791187331080437,
-0.0509765... | 0.042041 |
successive failures, capped by `max\_backoff.` If Agent templating is being used, this value is also used as the min backoff time for the templating server. Uses [duration format strings](/vault/docs/concepts/duration-format). - `max\_backoff` `(string or integer: "5m")` - The maximum time Agent will delay before retry... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/index.mdx | main | vault | [
0.03178982809185982,
0.06195158138871193,
-0.06660132855176926,
-0.006551109254360199,
-0.03876873105764389,
-0.037031907588243484,
-0.024188097566366196,
0.023770146071910858,
0.05855126306414604,
-0.04073278233408928,
0.02318517491221428,
0.0368032306432724,
0.041947439312934875,
-0.0500... | 0.057495 |
following valid HCL omits the wrapping `sinks` object while specifying multiple sinks. ```hcl // Other Vault Agent or Vault Proxy configuration blocks // ... auto\_auth { method { type = "approle" config = { role\_id\_file\_path = "/etc/vault/roleid" secret\_id\_file\_path = "/etc/vault/secretid" } } sink { type = "fil... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/index.mdx | main | vault | [
-0.042676717042922974,
0.06610844284296036,
-0.04312080889940262,
0.01623636856675148,
-0.06390392035245895,
-0.07640357315540314,
-0.027378594502806664,
-0.0012741831596940756,
-0.006608559284359217,
-0.07742989808320999,
-0.02846849337220192,
-0.07696262747049332,
-0.03559543564915657,
0... | -0.016209 |
# Auto-auth method: Oracle Cloud Infrastructure (OCI) The `oci` method performs authentication against the [OCI Auth method](/vault/docs/auth/oci). ## Credentials The method use to authenticate is set using the `type` parameter. Valid values are `apikey` to authenticate using API Key credentials and `instance` for Inst... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/oci.mdx | main | vault | [
-0.030239645391702652,
0.013263924978673458,
-0.08789060264825821,
-0.05884360522031784,
-0.035005781799554825,
-0.0632590651512146,
0.03196926414966583,
0.048304665833711624,
0.050003375858068466,
-0.022061247378587723,
0.04360547661781311,
-0.05175824463367462,
0.07613489776849747,
0.039... | -0.029886 |
# Auto-auth method: Google Cloud Platform (GCP) The `gcp` method performs authentication against the [GCP Auth method](/vault/docs/auth/gcp). Both `gce` and `iam` authentication types are supported. ## Credentials Vault will use the GCP SDK's normal credential chain behavior. You can set a static `credentials` value, b... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/gcp.mdx | main | vault | [
-0.09140224754810333,
-0.04285740852355957,
-0.033225204795598984,
-0.06111731007695198,
-0.07806532829999924,
-0.01072873454540968,
0.06032158061861992,
0.003498190315440297,
-0.015502549707889557,
0.03651898726820946,
-0.0246408823877573,
-0.0610668770968914,
0.03446226194500923,
0.01268... | -0.054244 |
# Auto-auth method: AWS The `aws` method performs authentication against the [AWS Auth method](/vault/docs/auth/aws). Both `ec2` and `iam` authentication types are supported. If `ec2` is used, the agent will store the reauthentication value in memory and use it for reauthenticating, but will not persist it to disk. Due... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/aws.mdx | main | vault | [
-0.017362402752041817,
0.05630906671285629,
-0.06148306652903557,
-0.03981500118970871,
-0.028020260855555534,
0.01740903966128826,
0.016299158334732056,
0.020210810005664825,
0.13151906430721283,
-0.0028967999387532473,
-0.019760966300964355,
0.02285885065793991,
0.1105445846915245,
0.001... | 0.000023 |
# Auto-auth method: Kerberos The `kerberos` auto-auth method provides an automated mechanism to retrieve a Vault token for Kerberos entities. It reads in configuration and identification information from the surrounding environment, and uses it to authenticate to Vault. For more on this auth method, see the [Kerberos a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/kerberos.mdx | main | vault | [
0.004522246308624744,
-0.01379104983061552,
-0.0803411602973938,
-0.10637535154819489,
-0.07290343195199966,
-0.02447868511080742,
0.046945225447416306,
0.024042412638664246,
-0.014260705560445786,
0.009009581059217453,
-0.0064833625219762325,
-0.022650685161352158,
0.04059484973549843,
-0... | 0.006732 |
# Auto-auth method: Kubernetes The `kubernetes` method reads in a Kubernetes service account token from the running pod (via `/var/run/secrets/kubernetes.io/serviceaccount/token`) and sends it to the [Kubernetes Auth method](/vault/docs/auth/kubernetes/). ## Configuration - `role` `(string: required)` - The role to aut... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/kubernetes.mdx | main | vault | [
-0.012321548536419868,
-0.0007957038469612598,
-0.009524082764983177,
-0.051807209849357605,
-0.05732869356870651,
0.005945607088506222,
0.029602237045764923,
0.038357846438884735,
0.08099028468132019,
-0.01327595952898264,
-0.048951659351587296,
-0.018960734829306602,
0.051714345812797546,
... | 0.112517 |
# Auto-auth method: TLS certificates The `cert` method uses the configured TLS certificates from the `vault` stanza of the agent configuration and takes an optional `name` parameter. There is no option to use certificates which differ from those used in the `vault` stanza. It is strongly advised to provide TLS settings... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/cert.mdx | main | vault | [
-0.020987123250961304,
0.07740334421396255,
-0.07587277144193649,
-0.01322187203913927,
-0.04802091792225838,
-0.0779777243733406,
0.0067339674569666386,
-0.03238051012158394,
0.053004179149866104,
-0.05246535688638687,
0.0049520218744874,
0.005469857715070248,
0.10457205027341843,
0.06835... | -0.076654 |
# Auto-auth method: AliCloud The `alicloud` method performs authentication against the [AliCloud Auth method](/vault/docs/auth/alicloud). ## Credentials Auto-auth will use the first credential it can successfully obtain in the following order: 1. [Environment variables](https://github.com/aliyun/alibaba-cloud-sdk-go/bl... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/alicloud.mdx | main | vault | [
-0.03680961951613426,
0.03035055287182331,
-0.07490841299295425,
-0.04431784525513649,
-0.06882619112730026,
0.018247082829475403,
0.0402994267642498,
0.016228629276156425,
0.09092535823583603,
0.012470634654164314,
-0.011493711732327938,
-0.06217500939965248,
0.11287131160497665,
-0.00952... | -0.04566 |
# Auto-auth method: token file This authentication method is tailored for the development experience, and to facilitate getting started with Vault Agent and Vault Proxy. Vault Agent and Vault Proxy should never be configured to use this auto-auth method in a production environment. The `token\_file` method reads in an ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/token_file.mdx | main | vault | [
-0.07672825455665588,
0.025143330916762352,
-0.0758194848895073,
-0.02323629893362522,
-0.03981638327240944,
-0.05978907644748688,
0.028525900095701218,
0.018145207315683365,
0.013461443595588207,
-0.0013918583281338215,
-0.0006626762915402651,
0.09316162765026093,
0.009516649879515171,
0.... | 0.089705 |
# Auto-auth method: JSON web tokens (JSW) The `jwt` method reads in a JWT from a file and sends it to the [JWT Auth method](/vault/docs/auth/jwt). ## Configuration - `path` `(string: required)` - The path to the JWT file - `role` `(string: required)` - The role to authenticate against on Vault - `remove\_jwt\_after\_re... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/jwt.mdx | main | vault | [
-0.0539301373064518,
0.0337846502661705,
0.010271267034113407,
0.009029845707118511,
0.026173224672675133,
-0.06217129901051521,
-0.003718807827681303,
-0.051267098635435104,
0.0005772829172201455,
-0.09678441286087036,
0.024559881538152695,
0.05676265060901642,
0.061464738100767136,
-0.00... | 0.016044 |
# Auto-auth method: Azure The `azure` method reads in Azure instance credentials and uses them to authenticate with the [Azure Auth method](/vault/docs/auth/azure). It reads most parameters needed for authentication directly from instance information based on the value of the `resource` parameter. ## Configuration - `r... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/azure.mdx | main | vault | [
-0.02385157346725464,
0.05123837664723396,
-0.07197536528110504,
0.018714740872383118,
-0.028045780956745148,
0.0020918441005051136,
0.10417080670595169,
-0.022729869931936264,
0.04923398420214653,
0.05662593990564346,
-0.036867957562208176,
-0.0251914169639349,
0.11178982257843018,
0.1128... | -0.00875 |
# Auto-auth method: application roles (AppRole) The `approle` method reads in a role ID and a secret ID from files and sends the values to the [AppRole Auth method](/vault/docs/auth/approle). The method caches values and it is safe to delete the role ID/secret ID files after they have been read. In fact, by default, af... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/approle.mdx | main | vault | [
-0.013025681488215923,
0.07260876893997192,
-0.08362048864364624,
-0.015418502502143383,
-0.005527405999600887,
-0.03446133807301521,
0.062402479350566864,
0.0069990879856050014,
0.0207259152084589,
-0.017870910465717316,
0.031168054789304733,
0.06400242447853088,
0.11296912282705307,
0.02... | -0.037823 |
# Auto-auth method: LDAP The `ldap` method reads in a password from a file and sends it to the [LDAP Auth method](/vault/docs/auth/ldap). ## Configuration - `password\_file\_path` `(string: required)` - The path to the password file - `username` `(string: required)` - The username to authenticate against on Vault - `re... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/methods/ldap.mdx | main | vault | [
-0.002053256845101714,
-0.00630149943754077,
-0.07845646888017654,
-0.0008400391670875251,
-0.016273170709609985,
-0.0246446393430233,
0.024977046996355057,
-0.031197676435112953,
-0.0036633163690567017,
-0.03426438570022583,
0.062268611043691635,
0.0906534418463707,
0.05437004938721657,
-... | -0.040423 |
# Auto-auth sink: File The `file` sink writes tokens, optionally response-wrapped and/or encrypted, to a file. This may be a local file or a file mapped via some other process (NFS, Gluster, CIFS, etc.). Once the sink writes the file, it is up to the client to control lifecycle; generally it is best for the client to r... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/autoauth/sinks/file.mdx | main | vault | [
-0.038478001952171326,
0.030173150822520256,
-0.06533173471689224,
0.028374426066875458,
-0.02342059276998043,
-0.05164390057325363,
-0.0022362894378602505,
0.08074452728033066,
-0.0045125908218324184,
0.014246152713894844,
-0.008516932837665081,
0.04730406776070595,
-0.020557189360260963,
... | 0.112999 |
# What is Vault Proxy? Vault Proxy aims to remove the initial hurdle to adopt Vault by providing a more scalable and simpler way for applications to integrate with Vault. Vault Proxy acts as an [API proxy][apiproxy] for Vault, and can optionally allow or force interacting clients to use its [automatically authenticated... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/index.mdx | main | vault | [
-0.07352592051029205,
0.03073069080710411,
-0.03721636161208153,
-0.023341810330748558,
-0.04622533917427063,
-0.04227546975016594,
0.014421443454921246,
-0.022527111694216728,
0.060641758143901825,
-0.04454293102025986,
-0.05161749944090843,
0.09278325736522675,
0.055996499955654144,
0.01... | 0.072688 |
- to specify the maximum duration a log should be written to before it needs to be rotated. Must be a duration value such as 30s. Defaults to 24h. - `-log-rotate-max-files` ((#\\_log\_rotate\_max\_files)) - to specify the maximum number of older log file archives to keep. Defaults to `0` (no files are ever deleted). Se... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/index.mdx | main | vault | [
-0.014782613143324852,
0.0229021105915308,
-0.05749431252479553,
-0.06000051647424698,
-0.05219209939241409,
-0.049808572977781296,
-0.052820391952991486,
0.006659827660769224,
0.02485014870762825,
0.051279835402965546,
0.009280708618462086,
0.0811804011464119,
0.055937688797712326,
0.0252... | -0.035566 |
on the local disk to a directory of PEM-encoded CA certificates to verify the Vault server's SSL certificate. This value can be overridden by setting the `VAULT\_CAPATH` environment variable. - `client\_cert` `(string: )` - Path on the local disk to a single PEM-encoded CA certificate to use for TLS authentication to t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/index.mdx | main | vault | [
0.022558201104402542,
0.08471547067165375,
-0.06751476973295212,
-0.013594777323305607,
-0.008455544710159302,
-0.07818576693534851,
-0.017638467252254486,
-0.000434192072134465,
0.09047827124595642,
-0.015091047622263432,
0.0520453043282032,
-0.02061680518090725,
0.11291705071926117,
0.07... | -0.141646 |
supports the [telemetry][telemetry] stanza and collects various runtime metrics about its performance, the auto-auth and the cache status: | Metric | Description | Type | | -------------------------------- | ---------------------------------------------------- | ------- | | `vault.proxy.auth.failure` | Number of authen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/index.mdx | main | vault | [
-0.03163422644138336,
0.00467084301635623,
-0.08175129443407059,
-0.03541546314954758,
-0.06771841645240784,
-0.1210126206278801,
0.02151637338101864,
-0.01610605977475643,
0.018964217975735664,
0.006894741673022509,
-0.032370299100875854,
0.029791025444865227,
0.06155257672071457,
-0.0095... | 0.002133 |
# Understand the risks of using inconsistent versions of Proxy and Vault There is no requirement to run identical versions of Vault Proxy and Vault server. It is safe to run different versions. However, you may not be able to take advantage of all the newest features in Vault if you do not upgrade to the most recent ve... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/versions.mdx | main | vault | [
-0.003601777134463191,
-0.0013683389406651258,
0.02198094129562378,
-0.07442567497491837,
-0.023113664239645004,
-0.05992542579770088,
-0.06985357403755188,
-0.08162323385477066,
-0.0013302229344844818,
-0.008456874638795853,
0.012590937316417694,
0.09875788539648056,
0.010801125317811966,
... | -0.123368 |
# Use Vault Proxy as an API proxy Vault Proxy's API proxy functionality allows you to use Vault Proxy's API as a proxy for Vault's API. ## Functionality The [`listener` stanza](/vault/docs/agent-and-proxy/proxy#listener-stanza) for Vault Proxy configures a listener for Vault Proxy. If its `role` is not set to `metrics\... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/apiproxy.mdx | main | vault | [
-0.03766928240656853,
0.013434549793601036,
-0.03963364288210869,
-0.053207334131002426,
-0.06898564845323563,
-0.065413698554039,
0.01049143634736538,
-0.019375747069716454,
0.050129201263189316,
-0.026009241119027138,
-0.06905129551887512,
0.06398797035217285,
0.046618204563856125,
0.048... | -0.008616 |
Enterprise cluster, and are documented as part of its [Eventual Consistency](/vault/docs/enterprise/consistency#vault-proxy-and-consistency-headers) page. - `enforce\_consistency` `(string: "never")` - Set to one of `"always"` or `"never"`. - `when\_inconsistent` `(string: optional)` - Set to one of `"fail"`, `"retry"`... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/apiproxy.mdx | main | vault | [
-0.03486783802509308,
-0.0010148744331672788,
-0.03292170912027359,
-0.022942591458559036,
-0.0738157108426094,
-0.058308932930231094,
0.00773073872551322,
-0.05418465659022331,
0.0249605942517519,
-0.07342597842216492,
-0.008057378232479095,
0.03203040733933449,
0.08815350383520126,
0.003... | 0.069984 |
# Vault Proxy caching overview Vault Proxy caching allows client-side caching of responses containing newly created tokens and responses containing leased secrets generated off of these newly created tokens. The renewals of the cached tokens and leases are also managed by the proxy. Additionally, with `cache\_static\_s... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/index.mdx | main | vault | [
-0.0672840029001236,
-0.006106340792030096,
0.0044168950989842415,
0.016653407365083694,
-0.05343357101082802,
-0.05769822373986244,
0.007667188532650471,
-0.06964493542909622,
0.08006560057401657,
0.0037736757658421993,
-0.031510476022958755,
0.09277947247028351,
0.04175959900021553,
-0.0... | -0.005063 |
the cache, an endpoint `/proxy/v1/cache-clear`(see below) is made available to manually evict cache entries based on some of the query criteria used for indexing the cache entries. ## Request uniqueness In order to detect repeat requests and return cached responses, Proxy needs to have a way to uniquely identify the re... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/index.mdx | main | vault | [
-0.0762908086180687,
0.04494161531329155,
0.049524951726198196,
-0.010855048894882202,
-0.07260652631521225,
-0.06344444304704666,
0.04415206238627434,
-0.08110322803258896,
0.10922073572874069,
0.032492756843566895,
-0.06701245158910751,
0.10183680802583694,
0.014921268448233604,
-0.04924... | 0.028566 |
to `request\_path`. The namespace of which the cache entries to be evicted for the given request path. ### Sample payload ```json { "type": "token", "value": "hvs.rlNjegSKykWcplOkwsjd8bP9" } ``` ### Sample request ```shell-session $ curl \ --request POST \ --data @payload.json \ http://127.0.0.1:1234/proxy/v1/cache-cle... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/index.mdx | main | vault | [
-0.05537557229399681,
0.05259237438440323,
-0.02406078390777111,
-0.010498670861124992,
-0.07321370393037796,
-0.08316679298877716,
-0.020313099026679993,
-0.015197483822703362,
0.036273933947086334,
0.012718859128654003,
-0.03787556663155556,
0.06585689634084702,
-0.044841621071100235,
-0... | 0.013678 |
blocks # ... cache { persist = { type = "kubernetes" path = "/vault/proxy-cache/" keep\_after\_import = true exit\_on\_err = true service\_account\_token\_file = "/tmp/serviceaccount/token" } } listener "tcp" { address = "127.0.0.1:8100" tls\_disable = true } listener "tcp" { address = "127.0.0.1:3000" tls\_disable = t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/index.mdx | main | vault | [
-0.009236440993845463,
0.05738655850291252,
0.015105548314750195,
-0.05619744956493378,
-0.04997656121850014,
-0.06084900721907616,
0.01263724360615015,
-0.055539242923259735,
0.10256798565387726,
-0.00003410807767068036,
-0.022584283724427223,
-0.005559077486395836,
-0.019895952194929123,
... | 0.043266 |
# Improve Vault traffic resiliency with Vault Proxy @include 'alerts/enterprise-only.mdx' Use static secret caching with Vault Proxy to cache KVv1 and KVv2 secrets to minimize requests made to Vault and provide resilient connections for clients. Vault Proxy utilizes the Enterprise only [Vault event notification system]... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/static-secret-caching.mdx | main | vault | [
0.027201315388083458,
0.02559591643512249,
-0.008521793410182,
-0.013683627359569073,
-0.04326310753822327,
-0.051796965301036835,
-0.034990012645721436,
-0.044230177998542786,
0.06496985256671906,
0.00773788383230567,
-0.07073281705379486,
0.11160574853420258,
0.0889078751206398,
-0.01242... | -0.06054 |
serves the cached response rather than forwarding the request to Vault. Vault Proxy does not cache any non-KV API responses. While KV secrets can be retrieved even if Vault is unavailable, other requests cannot be served. As a result, using the `vault kv` CLI command, which sends a request to `/sys/internal/ui/mounts` ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/static-secret-caching.mdx | main | vault | [
-0.021975696086883545,
0.04020735248923302,
-0.005153120495378971,
-0.001460326719097793,
-0.03318682685494423,
-0.05178411677479744,
-0.0486588254570961,
-0.03330797702074051,
0.11767502129077911,
-0.009629880078136921,
-0.022848758846521378,
0.051627278327941895,
0.011648603715002537,
-0... | -0.015486 |
the information is out of date. Vault Proxy continually monitors KV events for updates. A large value for `Age` may simply mean that the secret has not been rotated recently. ## Configuration The top level `cache` block has the following configuration entries relating to static secret caching: - `cache\_static\_secrets... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/static-secret-caching.mdx | main | vault | [
0.011812347918748856,
0.05650859698653221,
-0.05215079337358475,
0.0055549065582454205,
-0.0468723401427269,
-0.024496518075466156,
-0.04939338564872742,
-0.0306327473372221,
0.04012947902083397,
-0.016878096386790276,
0.004981843754649162,
0.05192689970135689,
0.02533654123544693,
0.01527... | -0.013067 |
# Use Vault Proxy built-in persistent caching Vault Proxy can restore tokens and leases from a persistent cache file created by a previous Vault Proxy process. The persistent cache is a BoltDB file that includes tuples encrypted by a generated encryption key. The encrypted tuples include the Vault token used to retriev... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/persistent-caches/index.mdx | main | vault | [
-0.047373805195093155,
0.010251527652144432,
-0.035169001668691635,
0.002934888703748584,
-0.08769334107637405,
-0.011760569177567959,
-0.023668112233281136,
-0.03901974484324455,
0.04946576803922653,
-0.004054076503962278,
-0.05988962948322296,
0.08350379019975662,
0.029721060767769814,
-... | -0.002131 |
# Use Kubernetes persistent cache When `kubernetes` is configured for the persistent cache type, Vault Proxy will optimize the persistent cache specifically for Kubernetes. This type of persistent cache requires a Kubernetes service account token. The service account token is used during encryption and decryption of th... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/proxy/caching/persistent-caches/kubernetes.mdx | main | vault | [
0.027231574058532715,
0.039579834789037704,
-0.012036490254104137,
-0.023030182346701622,
-0.06899941712617874,
-0.008631384931504726,
0.007578341756016016,
-0.007048016879707575,
0.07010094821453094,
0.03452048823237419,
-0.02890479564666748,
0.06507489085197449,
-0.01387707144021988,
-0.... | 0.009453 |
# Run Vault Agent as a Windows service Vault Agent can be run as a Windows service. In order to do this, you need to register Vault Agent with the Windows Service Control Manager. After Vault Agent is registered, it can be started like any other Windows service. While this guide focuses on an example for Vault Agent, t... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/winsvc.mdx | main | vault | [
0.01681743562221527,
-0.04586930200457573,
-0.11887091398239136,
-0.0043183607049286366,
-0.12694963812828064,
0.032473016530275345,
-0.006664506159722805,
0.028133558109402657,
0.010329187847673893,
0.013612545095384121,
-0.04336488991975784,
0.021515769883990288,
0.05565144121646881,
0.0... | -0.100392 |
you need to manually edit the path later, use the Registry Editor to find the following key: `HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Services\VaultAgent`. You can edit the `ImagePath` value at that key to the correct path. ## Start the Vault Agent service There are multiple ways to start the service. - Using the... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/winsvc.mdx | main | vault | [
0.07345611602067947,
-0.03081321157515049,
-0.10848736017942429,
-0.03252817690372467,
-0.01274455338716507,
0.048342324793338776,
-0.02717127464711666,
0.04076780378818512,
0.00985105149447918,
-0.018045343458652496,
0.013567290268838406,
0.023630589246749878,
0.05200791731476784,
0.07686... | -0.101329 |
# What is Vault Agent? Vault Agent aims to remove the initial hurdle to adopt Vault by providing a more scalable and simpler way for applications to integrate with Vault, by providing the ability to render [templates][template] containing the secrets required by your application, without requiring changes to your appli... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/index.mdx | main | vault | [
-0.055590372532606125,
0.025653308257460594,
-0.06186356768012047,
-0.00826359260827303,
-0.05476871505379677,
-0.017786815762519836,
-0.02945917658507824,
0.0017227116040885448,
0.06689727306365967,
-0.03484649956226349,
-0.04203878715634346,
0.058722928166389465,
0.07030779868364334,
0.0... | 0.042264 |
be a duration value such as 30s. Defaults to 24h. - `-log-rotate-max-files` ((#\\_log\_rotate\_max\_files)) - to specify the maximum number of older log file archives to keep. Defaults to `0` (no files are ever deleted). Set to `-1` to discard old log files when a new one is created. ### Configuration file options Thes... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/index.mdx | main | vault | [
-0.0027519611176103354,
0.026787832379341125,
-0.08934351801872253,
-0.041994914412498474,
-0.026785150170326233,
-0.04688199236989021,
-0.042021047323942184,
0.012787985615432262,
0.028375079855322838,
0.023193981498479843,
0.016123605892062187,
0.0707915872335434,
0.07506939768791199,
0.... | 0.017431 |
command-line flag](#\_log\_format). - `log\_file` - Equivalent to the [`-log-file` command-line flag](#\_log\_file). - `log\_rotate\_duration` - Equivalent to the [`-log-rotate-duration` command-line flag](#\_log\_rotate\_duration). - `log\_rotate\_bytes` - Equivalent to the [`-log-rotate-bytes` command-line flag](#\_l... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/index.mdx | main | vault | [
0.04468957334756851,
0.037979673594236374,
-0.12332145124673843,
-0.08160198479890823,
0.015369419008493423,
-0.06481967121362686,
-0.012430048547685146,
0.030164537951350212,
0.03916506841778755,
0.0010774738620966673,
0.045819420367479324,
0.049256570637226105,
0.053419847041368484,
0.00... | -0.026879 |
is used in Vault Enterprise 1.7+ to indicate a stale read due to eventual consistency. Requests coming from the template subsystem are retried regardless of the failure. Second, templating retries may be performed by both the templating engine \_and\_ the cache proxy if Vault Agent [persistent cache][persistent-cache] ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/index.mdx | main | vault | [
-0.0001871541462605819,
0.024485016241669655,
-0.005001236218959093,
-0.03272753208875656,
-0.02606385387480259,
-0.07730119675397873,
-0.05628064647316933,
-0.0497034527361393,
0.09881585836410522,
-0.035409700125455856,
-0.038480304181575775,
0.09798545390367508,
-0.023477237671613693,
-... | -0.00527 |
Agent: 1. [Download](/vault/downloads) the Vault binary where the client application runs (virtual machine, Kubernetes pod, etc.) 1. Create a Vault Agent configuration file. (See the [Example Configuration](#example-configuration) section for an example configuration.) 1. Start a Vault Agent with the configuration file... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/index.mdx | main | vault | [
0.08561652153730392,
0.022527972236275673,
-0.09801708161830902,
-0.06263384968042374,
-0.04729834198951721,
-0.0011144992895424366,
-0.005022506229579449,
0.03890509158372879,
0.04004734754562378,
-0.03354773670434952,
0.030287962406873703,
-0.04247919097542763,
0.08341092616319656,
-0.02... | 0.014153 |
# Understand the risks of using inconsistent versions of Agent and Vault There is no requirement to run identical versions of Vault Agent and Vault server. It is safe to run different versions. However, you may not be able to take advantage of all the newest features in Vault if you do not upgrade to the most recent ve... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/versions.mdx | main | vault | [
0.02491048164665699,
-0.003077870234847069,
-0.019055742770433426,
-0.061653684824705124,
0.011050518602132797,
-0.04938923195004463,
-0.07111381739377975,
-0.06814990192651749,
-0.002064763568341732,
-0.044659215956926346,
0.05920345336198807,
0.05235125496983528,
0.030360357835888863,
0.... | -0.060943 |
not deliberately make a change to templating that breaks existing deployments | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/versions.mdx | main | vault | [
0.00013044706429354846,
0.08623377233743668,
0.088083915412426,
0.002786958124488592,
0.054157499223947525,
-0.04956146702170372,
-0.036518391221761703,
-0.037309903651475906,
-0.025934642180800438,
0.051053933799266815,
0.04775737598538399,
0.000052032879466423765,
-0.0522015206515789,
-0... | -0.056225 |
# Run Vault Agent in process supervisor mode Vault Agent's Process Supervisor Mode allows Vault secrets to be injected into a process via environment variables using [Consul Template markup][consul-templating-language]. -> If you are running your applications in a Kubernetes cluster, we recommend evaluating the [Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/process-supervisor.mdx | main | vault | [
0.012854477390646935,
0.0376434363424778,
-0.02286784164607525,
-0.029372306540608406,
-0.0189878661185503,
-0.02855731174349785,
-0.07615069299936295,
0.02084410935640335,
0.0600338876247406,
0.00958178099244833,
0.013532247394323349,
-0.022161245346069336,
-0.008238381706178188,
0.023056... | 0.051971 |
the child process on secret changes. There are two types of secret changes relevant to this configuration: a static secret update (on [static\_secret\_render\_interval`](/vault/docs/agent-and-proxy/agent/template#static\_secret\_render\_interval)) and dynamic secret being close to its expiration. The configuration supp... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/process-supervisor.mdx | main | vault | [
-0.05334889143705368,
-0.005577816162258387,
-0.051291581243276596,
0.004816573578864336,
0.01781388185918331,
-0.068872831761837,
0.001210068236105144,
0.035908736288547516,
0.07186034321784973,
0.017541293054819107,
0.02005573734641075,
0.035573117434978485,
0.02024266868829727,
-0.00669... | 0.050766 |
# Use Vault Agent templates Vault Agent's Template functionality allows Vault secrets to be rendered to files or environment variables (via the [Process Supervisor Mode](/vault/docs/agent-and-proxy/agent/process-supervisor)) using [Consul Template markup][consul-templating-language]. ## Functionality The `template\_con... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/template.mdx | main | vault | [
-0.026352331042289734,
0.09797553718090057,
-0.05787312239408493,
-0.029054436832666397,
0.03532371297478676,
-0.03536766394972801,
-0.029076198115944862,
0.043330952525138855,
0.025610843673348427,
-0.02752053178846836,
0.013815806247293949,
-0.0009743731352500618,
0.01737380027770996,
-0... | 0.061733 |
If specified, configures how often Vault Agent Template should render non-leased secrets such as KV v2. This setting will not change how often Vault Agent Templating renders leased secrets. Uses [duration format strings](/vault/docs/concepts/duration-format). - `max\_connections\_per\_host` `(int: 10)` - Limits the tot... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/template.mdx | main | vault | [
0.005501913372427225,
0.08885066211223602,
-0.06738287955522537,
-0.003947331104427576,
-0.04535873234272003,
-0.005020079202950001,
-0.0845179334282875,
0.001321703428402543,
0.07746864855289459,
-0.1008361354470253,
0.051700659096241,
-0.00979986134916544,
0.06743225455284119,
0.01595860... | -0.062351 |
useful for short templates. This option is mutually exclusive with the `source` option. - `command`Ξ `(string: "")` - This is the optional command to run when the template is rendered. The command will only run if the resulting template changes. The command must return within 30s (configurable), and it must have a succ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/template.mdx | main | vault | [
0.027768710628151894,
0.0895138680934906,
-0.07883384078741074,
0.01103250402957201,
0.05448678135871887,
-0.026888711377978325,
-0.041532132774591446,
0.03189634531736374,
0.0952959656715393,
-0.054306112229824066,
0.09754669666290283,
-0.01625289022922516,
0.015048283152282238,
-0.059033... | 0.049836 |
Renewals and updating secrets The Vault Agent templating automatically renews and fetches secrets/tokens. Unlike [Vault Agent caching](/vault/docs/agent-and-proxy/agent/caching), the behavior of how Vault Agent templating does this depends on the type of secret or token. The following is a high level overview of differ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/template.mdx | main | vault | [
-0.040235720574855804,
0.02844364382326603,
-0.022857557982206345,
0.015543672256171703,
-0.023846441879868507,
-0.03192880377173424,
-0.07462680339813232,
-0.0493699312210083,
0.08054125308990479,
-0.020092668011784554,
0.014687922783195972,
0.0622897744178772,
0.026249630376696587,
0.002... | 0.004553 |
} env\_template "MY\_ENV\_VAR" { contents = "{{ with secret \"secret/my-secret\" }}{{ .Data.data.foo }}{{ end }}" } env\_template "ENV\_VAR\_FROM\_FILE" { source = "/tmp/agent/template.ctmpl" } ``` [consul-templating-language]: https://github.com/hashicorp/consul-template/blob/v0.28.1/docs/templating-language.md [proce... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/template.mdx | main | vault | [
-0.02219560742378235,
0.11488106846809387,
-0.06909620016813278,
-0.03537185862660408,
-0.0029263796750456095,
-0.05257802829146385,
0.029663704335689545,
0.09017084538936615,
0.023522747680544853,
0.015516111627221107,
0.03528551384806633,
-0.02236027643084526,
0.028132060542702675,
0.033... | 0.030214 |
# Generate a Vault Agent development configuration file Use the Vault CLI to create a basic development configuration file to run Vault Agent in process supervisor mode. Development configuration files include an `auto\_auth` section that reference a token file based on the Vault token used to authenticate the CLI comm... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/generate-config.mdx | main | vault | [
0.02937595546245575,
0.04480474442243576,
-0.11144434660673141,
-0.057855889201164246,
-0.046500541269779205,
-0.008658923208713531,
-0.07404565066099167,
0.050560370087623596,
-0.033521153032779694,
-0.01657610759139061,
0.041317906230688095,
-0.11754879355430603,
0.06352077424526215,
0.0... | -0.028024 |
# Use Vault Agent as an API proxy @include 'alerts/deprecated.mdx' Vault Agent's API proxy functionality allows you to use Vault Agent's API as a proxy for Vault's API. [Static secret caching](/vault/docs/agent-and-proxy/proxy/caching/static-secret-caching) (KVv1 and KVv2) with API proxy minimizes the number of request... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/apiproxy.mdx | main | vault | [
-0.009344187565147877,
0.037594035267829895,
-0.03595093637704849,
-0.07456566393375397,
-0.044226374477148056,
-0.07610567659139633,
-0.028046900406479836,
-0.01498029101639986,
0.0661642774939537,
-0.04698465019464493,
-0.09800244867801666,
0.05206076800823212,
0.08772171288728714,
0.035... | -0.040881 |
# Vault Agent caching overview [Static secret caching](/vault/docs/agent-and-proxy/proxy/caching/static-secret-caching) (KVv1 and KVv2) with API proxy minimizes the number of requests forwarded to Vault. Vault Agent does not support static secret caching with API proxy. We recommend using [Vault Proxy](/vault/docs/agen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/caching/index.mdx | main | vault | [
-0.02090369537472725,
0.0037583704106509686,
-0.0027380678802728653,
-0.00995258055627346,
-0.0488942414522171,
-0.09662255644798279,
-0.05734609439969063,
-0.05435716733336449,
0.09179643541574478,
-0.009511561132967472,
-0.048201363533735275,
0.07713716477155685,
0.03782021626830101,
0.0... | -0.007754 |
the ordering of the request parameters are modified. As long as the requests come in without any change, caching behavior should be consistent. Identical requests with differently ordered request values will result in duplicated cache entries. A heuristic assumption that the clients will use consistent mechanisms to ma... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/caching/index.mdx | main | vault | [
0.0067950766533613205,
0.013937311246991158,
-0.017432458698749542,
-0.019916914403438568,
-0.07808294892311096,
-0.053388770669698715,
-0.05555674433708191,
-0.06216560676693916,
0.10050138831138611,
-0.0166873037815094,
0.015192173421382904,
0.1522337645292282,
0.04508037492632866,
0.011... | 0.029273 |
to maintain backwards compatibility. This configuration \*\*cannot\*\* be specified alongside `api\_proxy` equivalents, should not be preferred over configuring these values in the `api\_proxy` block, and `api\_proxy` should be the preferred place to configure these values. -> \*\*Note:\*\* When the `cache` block is de... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/caching/index.mdx | main | vault | [
0.0013432431733235717,
0.03406134992837906,
-0.03433489799499512,
-0.07087826728820801,
-0.07509168237447739,
-0.0028421503957360983,
-0.0008403268875554204,
-0.04099317267537117,
0.052587155252695084,
-0.03312598913908005,
-0.014674445614218712,
0.029087550938129425,
0.00988475140184164,
... | 0.009989 |
# Use built-in persistent caching Vault Agent can restore tokens and leases from a persistent cache file created by a previous Vault Agent process. The persistent cache is a BoltDB file that includes tuples encrypted by a generated encryption key. The encrypted tuples include the Vault token used to retrieve secrets, l... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/agent-and-proxy/agent/caching/persistent-caches/index.mdx | main | vault | [
-0.035012297332286835,
0.027362307533621788,
-0.046971093863248825,
-0.003266046056523919,
-0.04702198877930641,
0.02618388459086418,
-0.04068436473608017,
-0.01628182642161846,
0.06634858250617981,
-0.02772444672882557,
-0.010886295698583126,
0.04161309078335762,
0.00008932693890528753,
0... | 0.039351 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.