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 |
|---|---|---|---|---|---|
# Configuration Entries ## Background Consul's catalog was designed to store node, service, and check registrations. An instance of a service is defined by a combination of a node and a service registered against that node. Each of these service registrations is considered to be an \_instance\_ of a logical service. Lo... | https://github.com/hashicorp/consul/blob/main//docs/service-mesh/config-entries/README.md | main | consul | [
-0.05784619599580765,
-0.04735412821173668,
-0.020249852910637856,
-0.042605701833963394,
0.029325274750590324,
-0.054322876036167145,
0.05219185724854469,
-0.005180567968636751,
0.027227113023400307,
0.0449976846575737,
0.008804934099316597,
0.046784669160842896,
0.04096080735325813,
0.01... | 0.157646 |
ones that will likely require code or test updates when modifying a config entry or adding a new config entry kind.  | https://github.com/hashicorp/consul/blob/main//docs/service-mesh/config-entries/README.md | main | consul | [
-0.05829719826579094,
-0.0368487611413002,
-0.03938121721148491,
0.0030828521121293306,
0.10032156109809875,
-0.08678068965673447,
-0.0007706924807280302,
-0.018847059458494186,
-0.05302707850933075,
0.0033345886040478945,
0.08606134355068207,
0.04477539286017418,
0.006941115017980337,
-0.... | 0.156412 |
# Configuration Entries ## Merging Service Config Merging data from defaults in config entries is roughly a two-step process: 1. Flatten central configuration for proxies at a Consul server. Resolving config is done on behalf of a specific service, and this merge considers multiple config entries, such as proxy-default... | https://github.com/hashicorp/consul/blob/main//docs/service-mesh/config-entries/config-resolution.md | main | consul | [
-0.03567613288760185,
-0.044448692351579666,
-0.03980657458305359,
-0.020502058789134026,
-0.058841247111558914,
-0.0614781528711319,
0.007760792039334774,
0.003782328451052308,
-0.02184303291141987,
-0.00047305948100984097,
0.06030191853642464,
0.04756147786974907,
0.016930609941482544,
-... | 0.064825 |
# Controller Testing For every controller we want to enable 3 types of testing. 1. Unit Tests - These should live alongside the controller and utilize mocks and the controller.TestController. Where possible split out controller functionality so that other functions can be independently tested. 2. Lightweight integratio... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/testing.md | main | consul | [
-0.062248341739177704,
-0.036674946546554565,
-0.06158321350812912,
0.04523981735110283,
0.07069957256317139,
-0.07593712955713272,
0.0014673580881208181,
-0.00707611721009016,
-0.0023413582239300013,
0.0523744598031044,
0.06415560841560364,
-0.01606387086212635,
0.028048057109117508,
0.01... | 0.1265 |
suite.ctl = controller.NewTestController(Controller(), client) suite.client = rtest.NewClient(suite.ctl.Runtime().Client) } // Implement tests on the suite as needed. func (suite \*reconcileSuite) TestSomething() { // Setup Mock expectations // Push resources into the resource service as needed. // Issue the Reconcile ... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/testing.md | main | consul | [
-0.11172664910554886,
-0.003225985448807478,
-0.06948446482419968,
0.021627511829137802,
-0.03848050907254219,
-0.0896981805562973,
-0.05658944323658943,
0.0023527522571384907,
-0.012486276216804981,
-0.014470292255282402,
0.025719257071614265,
0.019400808960199356,
0.033629100769758224,
0... | 0.033699 |
# Overview > \*\*Note\*\* > Looking for guidance on adding new resources and controllers to Consul? Check > out the [developer guide](guide.md). Consul 1.16 introduced a set of [generic APIs] for managing resources, and a [controller runtime] for building functionality on top of them. [generic APIs]: ../../../proto-pub... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/README.md | main | consul | [
-0.07628940790891647,
-0.03096657432615757,
-0.10341750085353851,
-0.025288017466664314,
0.007891999557614326,
-0.07818520069122314,
-0.0405859537422657,
0.10512033849954605,
0.04570074379444122,
0.06838307529687881,
0.0020745510701090097,
-0.0024496617261320353,
-0.02244810201227665,
0.07... | 0.16765 |
too. #### Steps 10 & 11 Asynchronously, the log is replicated to followers and applied to their storage backends. | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/README.md | main | consul | [
-0.04821121692657471,
-0.041695792227983475,
0.012303330935537815,
0.044247932732105255,
0.09133654087781906,
-0.06586120277643204,
-0.036984626203775406,
-0.07839993387460709,
0.0841631293296814,
0.05515119433403015,
0.05217801779508591,
0.059796445071697235,
0.07338147610425949,
-0.05879... | 0.067861 |
# Resource and Controller Developer Guide This is a whistle-stop tour through adding a new resource type and controller to Consul 🚂 ## Resource Schema Adding a new resource type begins with defining the object schema as a protobuf message, in the appropriate package under [`proto-public`](../../../proto-public). ```sh... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/guide.md | main | consul | [
-0.001556942705065012,
0.00882788933813572,
-0.1101638451218605,
-0.043280474841594696,
-0.054066479206085205,
-0.006264182738959789,
0.04393761232495308,
0.04914586991071701,
0.025334123522043228,
0.0315278097987175,
-0.011156014166772366,
-0.11630560457706451,
-0.045413702726364136,
0.08... | 0.056152 |
it will not start unless the Initialize method is successful. The controller does not have retry logic for the initialize method specifically, but the controller is restarted on error. When restarted, the controller will attempt to execute the initialization again. The example below has the controller creating a defaul... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/guide.md | main | consul | [
-0.003994133323431015,
-0.06668936461210251,
-0.14189477264881134,
-0.022275691851973534,
-0.08444336801767349,
0.005116449203342199,
-0.005693524610251188,
0.10603468865156174,
-0.019007794559001923,
-0.014397803694009781,
0.065218485891819,
0.032217442989349365,
-0.03154463693499565,
0.0... | 0.003942 |
client.Write(ctx, &pbresource.WriteRequest{ Resource: &pbresource.Resource{, Owner: ownerID, // … }, }) ``` ## Testing Now that you have created your controller its time to test it. The types of tests each controller should have and boiler plat for test files is documented [here](./testing.md) | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/guide.md | main | consul | [
-0.04146971553564072,
-0.020030921325087547,
-0.07742869853973389,
0.03989420086145401,
-0.07237834483385086,
-0.005392084829509258,
-0.02798861265182495,
0.0770164430141449,
0.03374486044049263,
0.023429064080119133,
-0.027680182829499245,
-0.012359353713691235,
-0.03721291944384575,
0.00... | -0.056205 |
# Controllers This page describes how to write controllers in Consul's new controller architecture. -> \*\*Note\*\*: This information is valid as of Consul 1.17 but some portions may change in future releases. ## Controller Basics A controller consists of several parts: 1. \*\*The watched type\*\* - This is the main ty... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/controllers.md | main | consul | [
-0.06334958225488663,
-0.02436438389122486,
-0.09624622017145157,
-0.015373065136373043,
-0.0318802110850811,
-0.007305466569960117,
-0.003522571874782443,
0.026241330429911613,
0.05746360495686531,
0.07562762498855591,
0.07420005649328232,
0.023843299597501755,
-0.042879022657871246,
0.04... | 0.107529 |
we can map them with a built-in function: ```go func barController() controller.Controller { return controller.NewController("bar", pbexample.BarType). WithWatch(pbexample.FooType, controller.ReplaceType(pbexample.BarType)). WithReconciler(barReconciler{}) } ``` Here, all we need to do is replace the type of the `Foo` ... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/controllers.md | main | consul | [
-0.007419871632009745,
-0.0627046450972557,
-0.06304830312728882,
0.027151457965373993,
-0.0006681735976599157,
0.03569350391626358,
0.12431507557630539,
0.0004149499291088432,
0.043300312012434006,
-0.004678947851061821,
-0.0008958937833085656,
-0.02147323451936245,
-0.037580426782369614,
... | 0.002271 |
r.Data.GetFooName(), }) return true, idx, nil } func barController() controller.Controller { fooIndex := indexers.DecodedSingleIndexer( "foo", index.ReferenceOrIDFromArgs, fooReferenceFromBar, ) return controller.NewController("bar", pbexample.BarType, fooIndex). WithWatch( pbexample.FooType, dependency.CacheListMapper... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/controllers.md | main | consul | [
-0.08209636062383652,
-0.06035211682319641,
-0.04468844085931778,
0.06686052680015564,
-0.01717647723853588,
-0.010591241531074047,
0.11950013786554337,
-0.019441787153482437,
0.03257664665579796,
-0.014741641469299793,
-0.014230256900191307,
0.07967046648263931,
-0.04416436329483986,
-0.0... | 0.003438 |
needs a `BoundReferences []\*pbresource.Reference` field. 2. Use a `\*resource.BoundReferenceCollector` to capture any resource during `Reconcile` that directly contributes to the final output resource data payload. 3. Call `brc.List()` on the above and set it to the `BoundReferences` field on the computed resource bef... | https://github.com/hashicorp/consul/blob/main//docs/v2-architecture/controller-architecture/controllers.md | main | consul | [
-0.08264043927192688,
0.005738481879234314,
-0.04158724844455719,
0.05345524102449417,
0.04005451500415802,
0.024695754051208496,
0.04938244819641113,
-0.03492560610175133,
0.024247057735919952,
0.02344248630106449,
-0.07840629667043686,
-0.008543305099010468,
-0.017532160505652428,
-0.018... | 0.027961 |
# V2 Service Mesh Architecture In Consul 1.16 and 1.17 releases, Consul's service mesh has been rewritten to use the controller architecture and the resource APIs. At a high level, the service mesh consists of resources and controllers living in three groups: `catalog`, `mesh`, and `auth`. . [HTTP API]: ../http-api [RPC]: ../rpc ## ACL Entities There are many entities in the ACL subsystem. The diagram below shows the relationship between the enti... | https://github.com/hashicorp/consul/blob/main//docs/acl/README.md | main | consul | [
-0.13890235126018524,
0.0029976728837937117,
-0.07503633946180344,
0.02107854187488556,
0.05094261094927788,
-0.03432806581258774,
0.048367347568273544,
0.0009664528770372272,
0.1032254621386528,
-0.03726722300052643,
-0.011189424432814121,
0.008651403710246086,
0.06051843240857124,
0.0068... | 0.183336 |
# pprof > A Profile is a collection of stack traces showing the call sequences that led to instances of a particular event, such as allocation. ## Installation `go install github.com/google/pprof@latest` ### CPU Profiles \* Every 10ms the CPU profiler interrupts a thread in the program and records the stack traces of \... | https://github.com/hashicorp/consul/blob/main//docs/debug/pprof.md | main | consul | [
-0.04890674352645874,
-0.04980441927909851,
-0.1370190680027008,
-0.001281672390177846,
0.03571663796901703,
-0.05703239515423775,
0.10809805244207382,
0.08365878462791443,
-0.026460127905011177,
-0.004502128344029188,
0.04615169018507004,
0.01130166556686163,
-0.002816947177052498,
-0.028... | 0.170428 |
3. \* \*\*Path Value\*\* \* The cumulative value of the following node. \* \*\*Node Color\*\*: \* large positive cumulative values are red. \* cumulative values close to zero are grey. \* large negative cumulative values are green; negative values are most likely to appear during profile comparison. \* \*\*Node Font Si... | https://github.com/hashicorp/consul/blob/main//docs/debug/pprof.md | main | consul | [
-0.04717232286930084,
0.04595109075307846,
0.019300296902656555,
0.0272988174110651,
0.026037676259875298,
-0.036819715052843094,
0.023019181564450264,
0.026717370375990868,
0.008783986791968346,
-0.023491371423006058,
-0.0029085783753544092,
-0.049588993191719055,
0.059293221682310104,
-0... | 0.130171 |
# Cluster membership This section is a work in progress. It will contain topics like the following: - hashicorp/serf - hashicorp/memberlist - network coordinates - consul events - consul exec Both client and server mode agents participate in a [Gossip Protocol](https://developer.hashicorp.com/docs/internals/gossip.html... | https://github.com/hashicorp/consul/blob/main//docs/cluster-membership/README.md | main | consul | [
0.006564974319189787,
-0.04458777979016304,
-0.0549563392996788,
-0.0014350690180435777,
0.05090070143342018,
-0.06559066474437714,
0.00857737846672535,
0.007790117058902979,
0.05099840462207794,
0.0186585895717144,
-0.006607417482882738,
0.03160981461405754,
0.027499154210090637,
0.010527... | 0.234994 |
# Glossary This page collects brief definitions of some of the technical terms used in the documentation for Vault. - [Audit Device](#audit-device) - [Auth Method](#auth-method) - [Barrier](#barrier) - [Client Token](#client-token) - [Plugin](#plugin) - [Request](#request) - [Secret](#secret) - [Secrets Engine](#secret... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/glossary.mdx | main | vault | [
-0.023865262046456337,
0.04318315535783768,
-0.08097125589847565,
-0.04070809856057167,
0.032016441226005554,
-0.0650472566485405,
0.05988619104027748,
-0.025712255388498306,
0.06478744000196457,
-0.02114681713283062,
0.0012356170918792486,
0.030224772170186043,
0.05002949759364128,
0.0113... | 0.128397 |
for further information on how [Namespaces can be specified](/vault/docs/enterprise/namespaces#vault-api-and-namespaces) as part of a request. #### Operation The request's operation can be one of the following: `alias-lookahead`, `create`, `delete`, `header`, `help`, `list`, `patch`, `read`, `renew`, `resolve-role`, `r... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/glossary.mdx | main | vault | [
-0.10599129647016525,
0.028712643310427666,
-0.05577635020017624,
0.041635386645793915,
-0.04344058036804199,
-0.037908293306827545,
-0.010743871331214905,
-0.024420902132987976,
0.06791052222251892,
-0.03635376691818237,
0.015065731480717659,
0.06895454227924347,
0.057075414806604385,
-0.... | 0.034029 |
# Manage custom messages in the Vault UI @include 'alerts/enterprise-only.mdx' Use custom banners and modals in the Vault UI to share system-wide alerts for all Vault UI users. 1. \*\*Messages are sticky\*\*. Users can only dismiss messages \*\*temporarily\*\*. The message reappears if the user refreshes their browser ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/ui/custom-messages.mdx | main | vault | [
0.07177893072366714,
0.05618564784526825,
0.004372387658804655,
0.0003068168880417943,
0.0188436321914196,
-0.0844498872756958,
0.07423075288534164,
-0.030310094356536865,
0.06998554617166519,
-0.03391267731785774,
-0.0003405787283554673,
0.02959585003554821,
0.1098490059375763,
0.05884343... | 0.052814 |
new message. Your new message only appears when a user logs into the targeted namespace or one of its child namespaces. You can verify that your message has the correct behavior by logging into an admin or parent namespace. The message should only appear when you switch to the targeted namespace.  option in the Vault server configuration. The UI runs on the same port as the Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/ui/index.mdx | main | vault | [
0.04772054776549339,
0.03335332125425339,
-0.05341806635260582,
-0.0785585269331932,
-0.04197118058800697,
-0.08500351756811142,
-0.05641968175768852,
-0.0461227186024189,
0.03213650733232498,
-0.08290950953960419,
-0.003792169503867626,
0.009406567551195621,
0.06627768278121948,
0.0216106... | -0.055004 |
# Manage custom login settings for the Vault GUI @include 'alerts/enterprise-and-hcp.mdx' Use can use the Vault CLI or API to customize a default and one or more back up login method for the Vault GUI login form. ## Before you start - \*\*You must have Vault Enterprise 1.20.0 or higher installed.\*\* - \*\*You must hav... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/ui/custom-login.mdx | main | vault | [
0.08297882974147797,
0.03605697304010391,
-0.0821637511253357,
-0.08400208503007889,
-0.06922726333141327,
0.00459644291549921,
-0.002685536164790392,
0.0297293271869421,
0.005384184420108795,
-0.03700977563858032,
-0.024755127727985382,
-0.005530175287276506,
0.11532290279865265,
0.054485... | -0.081752 |
`listing\_visibility` parameter to `unauth`. For example: ```json { "description": "Default GUI auth method", "config": { "listing\_visibility": "unauth" } } ``` 1. Make a `POST` call to [`/sys/auth/{plugin\_mount\_path}`](/vault/api-docs/system/auth#enable-auth-method) with the JSON data: ```shell-session $ curl \ --r... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/ui/custom-login.mdx | main | vault | [
-0.015611873008310795,
0.07384109497070312,
-0.12256666272878647,
0.011018174700438976,
0.0020079496316611767,
-0.05261518806219101,
-0.016549836844205856,
0.051306236535310745,
0.0062491195276379585,
-0.0030566544737666845,
0.05095751956105232,
-0.0585000216960907,
0.05115167424082756,
0.... | -0.051379 |
``` For example, to customize the login options for the `dev` namespace and set `userpass` as the default authentication method with `ldap` and `token` as additional, backup options: ```json { "namespace\_path": "dev", "default\_auth\_type": "userpass", "disable\_inheritance": false, "backup\_auth\_types": ["ldap", "to... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/ui/custom-login.mdx | main | vault | [
-0.010231636464595795,
0.021296868100762367,
-0.08483753353357315,
0.0007556682685390115,
-0.08125567436218262,
-0.04227510094642639,
-0.02348712645471096,
0.07724384218454361,
-0.04188496246933937,
0.004767395090311766,
-0.004850730765610933,
-0.047286346554756165,
0.06138339266180992,
0.... | -0.075996 |
# Manage namespaces in the Vault GUI @include 'alerts/enterprise-only.mdx' Use namespaces in Vault Enterprise to create isolated environments within a single Vault cluster. You can use namespaces to organize teams, projects, or environments, and delegate management to different administrators. For guidance on structuri... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/ui/namespaces.mdx | main | vault | [
0.05953887104988098,
-0.07714719325304031,
-0.08657261729240417,
-0.024561481550335884,
-0.027486082166433334,
-0.07564388960599899,
-0.0073561654426157475,
-0.02507045865058899,
0.052695974707603455,
-0.0073083690367639065,
-0.023190774023532867,
-0.046880658715963364,
0.13092133402824402,
... | -0.009198 |
# Vault GUI browser support Using the Vault GUI with an unsupported browser can degrade functionality for some features and render others nonfunctional. We strongly encourage using the latest version one of the following, supported browsers: - [Chrome](https://www.google.com/chrome) - [Firefox](https://www.mozilla.org/... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/ui/browser-support.mdx | main | vault | [
-0.07123596221208572,
-0.021347135305404663,
-0.059167154133319855,
-0.0266557764261961,
0.022545404732227325,
-0.09541329741477966,
-0.0744955763220787,
-0.02000194787979126,
0.028956998139619827,
-0.09604722261428833,
0.02872488833963871,
0.06938917934894562,
0.01465193834155798,
0.06224... | -0.037834 |
# Configure completed request logging Vault can be configured to log completed requests using the `log\_requests\_level` configuration parameter. ## Activating logging completed requests By default, logging completed requests is disabled. To activate request logging, set the `log\_requests\_level` configuration option ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/log-requests-level.mdx | main | vault | [
0.05395360291004181,
0.021881910040974617,
-0.056756649166345596,
-0.011669619008898735,
-0.017184920608997345,
-0.12235347926616669,
-0.015666792169213295,
-0.025525443255901337,
0.017168637365102768,
-0.0069796182215213776,
-0.02240675315260887,
-0.02141941525042057,
0.054247207939624786,
... | -0.055215 |
# Rate limit quotas - collective, by IP, by entity As the number of Vault client applications increases, the incoming requests to Vault can degrade Vault's performance. To protect your Vault environment's stability and network, as well as storage resource consumption, use [rate limit quotas](/vault/docs/configuration/c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/identity-based-rate-limit.mdx | main | vault | [
0.014215459115803242,
0.039543770253658295,
-0.05033828318119049,
-0.02424449473619461,
-0.03199584409594536,
-0.08233499526977539,
-0.044909603893756866,
-0.02379661239683628,
0.10655829310417175,
0.012226061895489693,
-0.026392508298158646,
0.014072109945118427,
0.09600792825222015,
0.02... | 0.01877 |
[Terraform Vault provider](https://registry.terraform.io/providers/hashicorp/vault/latest/docs/resources/quota\_rate\_limit) to configure and implement quotas instead of making API calls. - Define at least one lease count quota to protect your Vault cluster from [lease explosions](/vault/docs/configuration/prevent-leas... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/identity-based-rate-limit.mdx | main | vault | [
0.017960641533136368,
0.06575218588113785,
-0.012928348034620285,
-0.02829081565141678,
0.01320950873196125,
-0.10009191930294037,
-0.04289153963327408,
-0.017200909554958344,
0.05192552134394646,
0.0017902000108733773,
-0.015945281833410263,
-0.028873445466160774,
0.06920070201158524,
0.0... | 0.082937 |
# Prevent lease explosions As your Vault environment scales to meet deployment needs, you run the risk of lease explosions. Lease explosions can occur when a Vault cluster is over-subscribed and clients overwhelm system resources with consistent, high-volume API requests Unchecked lease explosions create a memory drain... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/prevent-lease-explosions.mdx | main | vault | [
0.06011548265814781,
0.01262736413627863,
0.002180008916184306,
0.016865024343132973,
0.003822796745225787,
-0.06491206586360931,
-0.045408714562654495,
-0.024589134380221367,
0.06702680885791779,
0.01379475835710764,
0.026270559057593346,
0.0611579455435276,
0.06363546848297119,
0.0202329... | 0.020497 |
Learn how to [query audit device logs](/vault/tutorials/monitoring/query-audit-device-logs). - Review [recommended Vault lease limits](/vault/docs/internals/limits#lease-limits). - Review [lease anti-patterns](/well-architected-framework/operational-excellence/security-vault-anti-patterns#not-adjusting-the-default-leas... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/prevent-lease-explosions.mdx | main | vault | [
0.09704069793224335,
0.03231055289506912,
-0.03914406895637512,
-0.023402253165841103,
0.006710889749228954,
-0.08813998103141785,
-0.03198530524969101,
-0.03608083724975586,
0.02392350696027279,
0.00714728282764554,
0.03943924605846405,
0.020177572965621948,
0.029032684862613678,
0.067640... | -0.017065 |
# `adaptive\_overload\_protection` stanza @include 'alerts/enterprise-only.mdx' As of Vault 1.18.0, adaptive overload protection is enabled by default Configure the `adaptive\_overload\_protection` stanza to control overload protection features for your Vault server. @include 'config-reload-supported.mdx' Do not disabl... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/adaptive-overload-protection.mdx | main | vault | [
0.03145549073815346,
0.05714399367570877,
-0.02816460095345974,
-0.018371209502220154,
0.008563225157558918,
-0.04461279883980751,
-0.028266312554478645,
-0.035831425338983536,
-0.009948919527232647,
-0.04059694707393646,
-0.005995703395456076,
0.07693812996149063,
0.11453831940889359,
-0.... | -0.033117 |
# Create a lease count quota Use lease count quotas to limit the number of leases generated on a per-mount basis and control resource consumption for your Vault instance where hard limits makes sense. ## Before you start - \*\*Confirm you have access to the root or administration namespace for your Vault instance\*\*. ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/create-lease-count-quota.mdx | main | vault | [
0.06562022864818573,
0.03517674654722214,
-0.06239312142133713,
-0.0023139326367527246,
-0.052041955292224884,
-0.031025493517518044,
0.0038481561932712793,
0.019051754847168922,
0.04102593660354614,
0.03919079899787903,
-0.0099562993273139,
-0.036829326301813126,
0.12009641528129578,
0.05... | -0.041495 |
# Vault configuration parameters Outside of development mode, Vault servers are configured using a file. The format of this file is [HCL](https://github.com/hashicorp/hcl) or JSON. @include 'plugin-file-permissions-check.mdx' An example configuration is shown below: For multi-node clusters, replace the loopback address... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
0.0582319013774395,
0.06183676794171333,
-0.11647748202085495,
-0.01266662310808897,
-0.007424511015415192,
-0.10237675905227661,
-0.07689278572797775,
-0.036094047129154205,
-0.008346159011125565,
-0.04910312220454216,
0.03158096596598625,
0.0119099710136652,
0.08365174382925034,
-0.00687... | -0.019003 |
use swap at all. Vault only supports memory locking on UNIX-like systems that support the mlock() syscall (Linux, FreeBSD, etc). Non UNIX-like systems (e.g. Windows, NaCL, Android) lack the primitives to keep a process's entire memory address space from spilling to disk and is therefore automatically disabled on unsupp... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
-0.0016332893865182996,
-0.020722646266222,
-0.031281545758247375,
-0.01281894464045763,
-0.028951989486813545,
-0.011924286372959614,
-0.04580153897404671,
0.033179521560668945,
0.04197927936911583,
0.009228161536157131,
-0.028223857283592224,
0.13411906361579895,
0.011684060096740723,
-0... | -0.031892 |
cancels the request. This can be overridden per listener via the `max\_request\_duration` value. - `detect\_deadlocks` `(string: "")` - A comma separated string that specifies the internal mutex locks that should be monitored for potential deadlocks. Currently supported values include `statelock`, `quotas` and `expirat... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
-0.05936064198613167,
0.019744738936424255,
-0.06855085492134094,
-0.02939850278198719,
0.018589407205581665,
-0.0540924146771431,
0.04333372041583061,
-0.028673944994807243,
0.08709237724542618,
0.04285048693418503,
0.02864326909184456,
0.021336903795599937,
-0.003524717641994357,
-0.0302... | 0.132747 |
counting by role if there are no role based quotas enabled. When `imprecise\_lease\_role\_tracking` is set to true and a new role-based quota is enabled, subsequent lease counts start from 0. `imprecise\_lease\_role\_tracking` affects role-based lease count quotas, but reduces latencies when not using role based quotas... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
0.011642820201814175,
-0.004481527954339981,
-0.08135325461626053,
0.03781462460756302,
-0.0027074378449469805,
-0.029453884810209274,
0.037867363542318344,
-0.016553444787859917,
0.057044871151447296,
-0.053304191678762436,
0.05403309315443039,
-0.018689727410674095,
0.06751829385757446,
... | 0.048043 |
leases. When the configured duration exceeds the expiry time of an irrevocable lease, Vault deletes the lease. The minimum value for `remove\_irrevocable\_lease\_after` is 2 days (`2d`). If you set the removal window to a value less than the minimum, Vault overwrites the value to `2d`. Deleting a lease may cause Vault ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/index.mdx | main | vault | [
-0.0038601229898631573,
0.05057786405086517,
-0.04009915143251419,
0.03936944901943207,
-0.009577600285410881,
-0.0665016695857048,
-0.0436953566968441,
-0.026552021503448486,
0.10660791397094727,
0.007603909820318222,
0.07613047957420349,
0.09513875097036362,
0.006825835909694433,
0.01621... | -0.010312 |
# Manage Vault resources programmatically with Terraform Use Terraform to manage policies, namespaces, and plugins in Vault. ## Before you start - \*\*You must have [Terraform installed](/terraform/install)\*\*. - \*\*You must have the [Terraform Vault provider](https://registry.terraform.io/providers/hashicorp/vault/l... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/programmatic-management.mdx | main | vault | [
0.018897706642746925,
-0.04246021807193756,
-0.04571843519806862,
-0.03437473252415657,
-0.04754451662302017,
-0.05122414231300354,
-0.05556400120258331,
-0.054076556116342545,
0.008566935546696186,
0.040761448442935944,
-0.014186250045895576,
-0.08451095223426819,
0.07152599096298218,
0.0... | -0.052292 |
your existing, non-root policies to the file: ```shell-session for vpolicy in $(vault policy list | grep -vw root) ; do echo "resource \"vault\_policy\" \"vault\_$vpolicy\" {" echo " name = \"$vpolicy\"" echo " policy = < vault\_policies.tf ``` 1. Update the `vault\_policies.tf` file with any new policies you want to a... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/programmatic-management.mdx | main | vault | [
0.05547720938920975,
0.061494555324316025,
-0.10419806838035583,
-0.07983382791280746,
0.00022806857305113226,
-0.006539654452353716,
-0.015485187061131,
0.021968204528093338,
-0.02733953669667244,
-0.007770889438688755,
0.05355622246861458,
-0.030110670253634453,
0.09462600201368332,
-0.0... | -0.109859 |
# Configure entropy augmentation Entropy augmentation enables Vault to sample entropy from external cryptographic modules. Sourcing external entropy is done by configuring a supported [Seal](/vault/docs/configuration/seal) type which include: [PKCS11 seal](/vault/docs/configuration/seal/pkcs11), [AWS KMS](/vault/docs/c... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/entropy-augmentation.mdx | main | vault | [
-0.018313074484467506,
0.044980488717556,
-0.044656191021203995,
-0.058773212134838104,
0.024760132655501366,
-0.04423467442393303,
-0.0028126463294029236,
-0.005074229557067156,
0.0875319316983223,
-0.022877860814332962,
0.008609520271420479,
-0.020570242777466774,
0.027879495173692703,
-... | 0.020506 |
# `reporting` stanza @include 'alerts/enterprise-only.mdx' The `reporting` stanza specifies various parameters for tuning replication related values. Please see the pages relating to [license utilization reporting](/vault/docs/enterprise/license/utilization-reporting) and [product usage reporting](/vault/docs/enterpris... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/reporting.mdx | main | vault | [
-0.005350665654987097,
0.0447847917675972,
-0.10831283032894135,
-0.061874810606241226,
-0.007034048903733492,
0.014400292187929153,
-0.007002305705100298,
-0.005165732000023127,
0.01806764304637909,
-0.051105763763189316,
0.002038906794041395,
0.050714410841464996,
0.11705193668603897,
-0... | 0.003517 |
# `telemetry` stanza The `telemetry` stanza specifies various configurations for Vault to publish metrics to upstream systems. Available Vault metrics can be found in the [Telemetry internals documentation](/vault/docs/internals/telemetry). ```hcl telemetry { statsite\_address = "statsite.company.local:8125" } ``` Metr... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
-0.03781546279788017,
0.02916000969707966,
-0.07043176144361496,
0.014217264950275421,
-0.022314157336950302,
-0.04986916482448578,
0.04251649230718613,
0.014439529739320278,
0.05346587300300598,
-0.045800693333148956,
0.03569598123431206,
-0.040283411741256714,
0.046443626284599304,
-0.03... | 0.067952 |
`false` with no filters, no metrics will be sent. - `prefix\_filter` `(string array: [])` - This is a list of filter rules to apply for allowing/blocking metrics by prefix in the following format: ```json ["+vault.token", "-vault.expire", "+vault.expire.num\_leases"] ``` A leading "\*\*+\*\*" will enable any metrics wi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
-0.09214483201503754,
0.0644342377781868,
-0.06919080764055252,
-0.045034151524305344,
-0.05283873528242111,
-0.10041496157646179,
0.02170594222843647,
-0.06035730987787247,
0.05047710984945297,
-0.04418705403804779,
0.051899414509534836,
-0.034413643181324005,
0.039114873856306076,
0.0129... | 0.059227 |
- `circonus\_broker\_select\_tag` `(string: "")` - Specifies a special tag which will be used to select a Circonus Broker when a Broker ID is not provided. The best use of this is to as a hint for which broker should be used based on \_where\_ this particular instance is running (e.g. a specific geo location or datacen... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
-0.02688385732471943,
0.03188660740852356,
-0.08947198837995529,
-0.010829371400177479,
-0.07483652979135513,
-0.0753350779414177,
0.03479069098830223,
0.007299258839339018,
0.03479297459125519,
-0.02909131534397602,
0.08256962895393372,
-0.04611716791987419,
0.07264672219753265,
-0.050079... | 0.109971 |
option `disable\_hostname` to avoid having prefixed metrics with hostname and enable instead `enable\_hostname\_label`. ```hcl telemetry { stackdriver\_project\_id = "my-test-project" stackdriver\_location = "us-east1-a" stackdriver\_namespace = "vault-cluster-a" disable\_hostname = true enable\_hostname\_label = true ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/telemetry.mdx | main | vault | [
0.021441075950860977,
-0.0020431929733604193,
-0.04620515927672386,
0.0006146475207060575,
-0.09280321002006531,
-0.08797341585159302,
-0.006869607605040073,
-0.0663195475935936,
0.06872949749231339,
-0.06448927521705627,
-0.002712228102609515,
-0.09904929250478745,
0.07334352284669876,
0.... | -0.029898 |
# `kms\_library` stanza The `kms\_library` stanza isolates platform specific configuration for managed keys. It defines logical names that are referenced within an API configuration keeping cluster and node specific details separated along with deployment concerns for each. At the moment managed keys are only available... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/kms-library.mdx | main | vault | [
0.029952822253108025,
-0.009159587323665619,
-0.06233848258852959,
-0.025673164054751396,
-0.003311904612928629,
0.004533294588327408,
-0.010967778041958809,
0.0031645020935684443,
-0.0042692930437624454,
-0.016195407137274742,
0.012918048538267612,
-0.006363046355545521,
0.10081566125154495... | -0.044214 |
# Create a rate limit quota Vault's rate limit quotas allow Vault admins to control how traffic enters the Vault cluster by setting a limit on the target namespace, mount, path, or role. It is a part of Vault's core feature set available in both Community and Enterprise Editions. The default behavior of rate limit quot... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.05283866450190544,
0.02414560317993164,
-0.06088511645793915,
-0.026955660432577133,
-0.021909769624471664,
-0.05767678841948509,
-0.03441347926855087,
-0.01752243936061859,
0.07880014181137085,
0.016510581597685814,
-0.01703115925192833,
-0.0007691740756854415,
0.07907666265964508,
0.04... | -0.028103 |
requests. Refer to the [identity-based rate limit quotas](/vault/docs/configuration/identity-based-rate-limit) for more details. - `secondary\_rate` `(float: 0.0)` – Can only be set for the `group\_by` modes `entity\_then\_ip` or `entity\_then\_none`. This is the rate limit applied to the requests that fall under the "... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.0094365319237113,
0.04009907692670822,
-0.08217041939496994,
-0.014381512999534607,
-0.05825721099972725,
-0.06994182616472244,
-0.0024060618598014116,
-0.029050830751657486,
0.11461034417152405,
0.04543719440698624,
0.023635275661945343,
-0.05140990391373634,
0.09096704423427582,
0.0106... | -0.01011 |
inheritably by setting the `inheritable` parameter to `true`. By default, it is set to `false`. 1. Create a quota rule on the `us-west` namespace which its child namespaces will inherit. The rate limit is 500 requests per minute. ```shell-session $ vault write sys/quotas/rate-limit/us-west \ path="us-west" \ rate=500 \... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.016778789460659027,
0.06106724590063095,
-0.08004773408174515,
-0.019187333062291145,
-0.09519747644662857,
-0.0876707062125206,
-0.0019981099758297205,
0.023972079157829285,
0.02340131811797619,
0.050611600279808044,
-0.023434115573763847,
-0.06155097857117653,
0.07622362673282623,
-0.0... | 0.039035 |
applied to its child namespaces inheritably by setting the `inheritable` parameter to `true`. By default, it is set to `false`. 1. Create a quota rule on the `us-west` namespace which its child namespace inherits. The rate limit is 500 requests per minute. ```shell-session $ curl --header "X-Vault-Token: $VAULT\_TOKEN"... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
0.008406303822994232,
0.06850894540548325,
-0.07854478806257248,
-0.0052254702895879745,
-0.04528937488794327,
-0.08389075845479965,
-0.04696280509233475,
-0.015486280433833599,
0.08732763677835464,
0.02220851369202137,
0.014059695415198803,
-0.06769710034132004,
0.0513586699962616,
0.0033... | -0.024523 |
└── parent └── child └── grand-child ``` Under the `root` namespace, you have a `parent` namespace, and then `parent/child` and `parent/child/grand-child` namespaces. You can set the resource quota on the `parent` namespace which gets applied to its child namespaces inheritably by setting the `inheritable` parameter to... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/create-rate-limit-quota.mdx | main | vault | [
-0.021922517567873,
0.013291507959365845,
-0.026718679815530777,
-0.0060752336867153645,
-0.05087820068001747,
-0.09081543982028961,
-0.01529412530362606,
-0.05275540426373482,
0.044657934457063675,
0.05332913249731064,
-0.02272237092256546,
-0.10295838117599487,
0.10753782838582993,
0.011... | -0.030378 |
# Vault GUI configuration Vault features a user interface (web interface) for interacting with Vault. Easily create, read, update, and delete secrets, authenticate, unseal, and more with the Vault GUI. ## Activating the Vault GUI The Vault GUI is not activated by default. To activate the UI, set the `ui` configuration ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/ui.mdx | main | vault | [
0.02943335846066475,
0.06233282759785652,
-0.06348975002765656,
-0.03828999400138855,
-0.0744810625910759,
-0.03158342465758324,
-0.020300885662436485,
-0.015994779765605927,
0.033977389335632324,
-0.1064913272857666,
-0.017919443547725677,
-0.03394866734743118,
0.10026779025793076,
0.0121... | -0.075758 |
## CLI emulation in the Vault GUI The Vault GUI includes an interactive Web REPL to interact with Vault's API much like the Vault CLI. For more on that, see the [Web REPL documentation](/vault/docs/commands/web). | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/ui.mdx | main | vault | [
-0.024710051715373993,
-0.00008089302718872204,
-0.085415780544281,
-0.06857939064502716,
-0.0021297908388078213,
-0.07792704552412033,
-0.015150637365877628,
0.0027639265172183514,
0.04871037229895592,
-0.07811383157968521,
0.02246944047510624,
-0.008513863198459148,
0.08616872876882553,
... | 0.046994 |
# Best practices for programmatic Vault management It can be a challenge to enforce appropriate governance policies on resources created directly from the Vault CLI or API. The best way to manage Vault at scale is to [codify resource management](/vault/tutorials/operations/codify-mgmt-vault-terraform) with [Terraform](... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/programmatic-best-practices.mdx | main | vault | [
-0.011991173960268497,
0.03186320513486862,
-0.05410736799240112,
-0.003710889257490635,
-0.01179052609950304,
-0.05888250097632408,
-0.03231543302536011,
-0.03545102849602699,
0.014629954472184181,
0.05965316295623779,
-0.011079696007072926,
-0.02437603659927845,
0.06931296736001968,
0.02... | 0.035009 |
# `sentinel` stanza The sentinel stanza specifies configurations for [Vault's Sentinel](/vault/docs/enterprise/sentinel) integration. ```hcl sentinel { additional\_enabled\_modules = ["http"] } ``` ## Requirements A valid Vault Enterprise license is required for use of Sentinel policies. ## `sentinel` parameters The se... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/sentinel.mdx | main | vault | [
-0.014911076053977013,
-0.04459461569786072,
-0.0745411142706871,
0.0005832649185322225,
0.024792181327939034,
-0.04375647380948067,
-0.04614683613181114,
-0.0011500556720420718,
-0.02514147199690342,
-0.04973187670111656,
0.03711269050836563,
0.02291623316705227,
0.02562699094414711,
0.02... | 0.128476 |
# User lockout @include 'user-lockout.mdx' ## `user\_lockout` stanza The `user\_lockout` stanza specifies various configurations for user lockout behaviour for failed logins in vault. They can be configured for all supported auth methods (userpass, ldap and approle) using "all" user\_lockout stanza name or for a specif... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/user-lockout.mdx | main | vault | [
0.030426092445850372,
0.0339098758995533,
-0.07269202172756195,
-0.08103005588054657,
-0.043861024081707,
0.05009986087679863,
0.047063447535037994,
-0.0316699855029583,
0.012210729531943798,
-0.06327623873949051,
0.00602179067209363,
0.012011383660137653,
0.11800964176654816,
-0.035606160... | -0.022947 |
# `replication` stanza @include 'alerts/enterprise-only.mdx' The `replication` stanza specifies various parameters for tuning replication related values. ```hcl replication { resolver\_discover\_servers = true logshipper\_buffer\_length = 1000 logshipper\_buffer\_size = "5gb" allow\_forwarding\_via\_header = false best... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/replication.mdx | main | vault | [
0.027811303734779358,
-0.019720183685421944,
-0.003167880466207862,
0.019893663004040718,
0.019345775246620178,
-0.059568390250205994,
-0.01421947218477726,
-0.07457607239484787,
-0.01877947337925434,
0.04685792326927185,
-0.04195335507392883,
0.056110624223947525,
0.08535664528608322,
-0.... | 0.043987 |
# `service\_registration` stanza The optional `service\_registration` stanza configures Vault's mechanism for service registration. The `service\_registration` stanza is designed for use cases where you would like to use a system like [Consul][consul] for [service discovery][consul-discovery], but use a different syste... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/service-registration/index.mdx | main | vault | [
-0.05812311917543411,
-0.021956032142043114,
-0.07800236344337463,
-0.026908332481980324,
-0.05602024868130684,
-0.06243481487035751,
0.03059390000998974,
0.025736631825566292,
0.05087931081652641,
-0.06591092050075531,
0.026591312140226364,
0.003549599088728428,
0.0748240277171135,
0.0229... | -0.011254 |
# Configure Kubernetes service registration Kubernetes Service Registration tags Vault pods with their current status for use with selectors. Service registration is only available when Vault is running in [High Availability mode](/vault/docs/concepts/ha). - \*\*HashiCorp Supported\*\* – Kubernetes Service Registration... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/service-registration/kubernetes.mdx | main | vault | [
0.02659476548433304,
-0.023034904152154922,
0.003937062807381153,
-0.03366535156965256,
-0.05264073610305786,
-0.01381799578666687,
0.035960689187049866,
-0.00047097206697799265,
0.047202788293361664,
-0.024934496730566025,
0.006604693830013275,
-0.08853239566087723,
0.048525527119636536,
... | 0.053336 |
will always reach the active node. When setting up Vault replication, it can be used as the primary address: ```shell-session $ vault write -f sys/replication/performance/primary/enable \ primary\_cluster\_addr='https://vault-active-us-east:8201' ``` ### Example upgrades In conjunction with the pod labels and the `OnDe... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/service-registration/kubernetes.mdx | main | vault | [
0.06473488360643387,
0.00510204816237092,
-0.009762274101376534,
-0.0003775805816985667,
0.02756202034652233,
-0.03687169775366783,
-0.04407820478081703,
-0.08102715015411377,
0.0868649110198021,
0.04505341872572899,
0.02278134413063526,
0.022670987993478775,
0.061757054179906845,
-0.05671... | 0.08452 |
# Configure Consul service registration Consul Service Registration registers Vault as a service in [Consul][consul] with a default health check. When Consul is configured as the storage backend, the stanza `service\_registration` is not needed as it will automatically register Vault as a service. ~> \*\*Version inform... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/service-registration/consul.mdx | main | vault | [
0.016596633940935135,
0.005621016025543213,
-0.08050315827131271,
-0.07004525512456894,
-0.05013389140367508,
-0.047093138098716736,
-0.05822043865919113,
0.025693682953715324,
0.03497995436191559,
-0.031112072989344597,
0.037854962050914764,
0.0013785905903205276,
0.05179879441857338,
0.0... | -0.042381 |
- `tls\_key\_file` `(string: "")` – Specifies the path to the private key for Consul communication. This should be set according to the [`key\_file`](/consul/docs/agent/config/config-files#key\_file) setting in Consul. - `tls\_min\_version` `(string: "tls12")` – Specifies the minimum TLS version to use. Accepted values... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/service-registration/consul.mdx | main | vault | [
-0.02642488107085228,
0.06038400158286095,
-0.11217403411865234,
-0.06655445694923401,
-0.04060027375817299,
-0.06918976455926895,
-0.036895543336868286,
0.049284663051366806,
0.06538191437721252,
0.03134752810001373,
0.03422768786549568,
0.019892431795597076,
0.05193187668919563,
0.085865... | -0.027128 |
# Unix listener configuration The Unix listener configures Vault to listen on the specified Unix domain socket. ```hcl listener "unix" { address = "/run/vault.sock" } ``` The `listener` stanza may be specified more than once to make Vault listen on multiple sockets. ## `unix` listener parameters - `address` `(string: "... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/unix.mdx | main | vault | [
0.026009175926446915,
-0.039074625819921494,
-0.12333937734365463,
-0.05912921205163002,
-0.06909554451704025,
-0.06883317977190018,
0.002954215044155717,
-0.024613266810774803,
0.06472719460725784,
-0.06551828980445862,
-0.014675363898277283,
0.039281945675611496,
0.08616958558559418,
-0.... | 0.018644 |
# TCP listener configuration @include 'alerts/ipv6-compliance.mdx' The TCP listener configures Vault to listen on a TCP address/port. ```hcl listener "tcp" { address = "127.0.0.1:8200" } ``` The `listener` stanza may be specified more than once to make Vault listen on multiple interfaces. If you configure multiple list... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
0.030847907066345215,
0.04129592329263687,
-0.05912288650870323,
-0.03599588945508003,
-0.021437954157590866,
-0.05052659660577774,
-0.016251537948846817,
-0.08030369132757187,
0.03309942036867142,
-0.08410768955945969,
-0.03281055763363838,
-0.01092996820807457,
0.11227881908416748,
-0.01... | 0.016221 |
to the Vault process. If a header is defined in the configuration file and the same header is used by the internal processes of Vault, the configured header is not accepted. For example, a custom header which has the `X-Vault-` prefix will not be accepted. A message will be logged in the Vault's logs upon start up indi... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
0.016935832798480988,
0.08846042305231094,
-0.06184414401650429,
-0.04884708672761917,
0.022439725697040558,
-0.08304256945848465,
-0.018995940685272217,
0.010761690326035023,
0.07065674662590027,
-0.0264739952981472,
0.024899378418922424,
-0.01053489837795496,
0.08469170331954956,
0.05412... | -0.061248 |
specified, enables a PROXY protocol behavior for the listener (version 1 and 2 are both supported). Accepted Values: - \_use\_always\_ - The client's IP address will always be used. - \_allow\_authorized\_ - If the source IP address is in the `proxy\_protocol\_authorized\_addrs` list, the client's IP address will be us... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.07511527091264725,
0.016101906076073647,
-0.01758570410311222,
-0.06814295798540115,
-0.017458703368902206,
-0.027603961527347565,
0.10056792944669724,
-0.07217590510845184,
-0.050833024084568024,
-0.003491257783025503,
0.01585470326244831,
0.0018721242668107152,
0.036397844552993774,
-... | 0.051727 |
post][go-tls-blog]. - `tls\_prefer\_server\_cipher\_suites` `(string: "false")` – Specifies to prefer the server's ciphersuite over the client ciphersuites. ~> \*\*Warning\*\*: The `tls\_prefer\_server\_cipher\_suites` parameter is deprecated. Setting it has no effect. See the above [Go blog post][go-tls-blog] for more... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.0460059717297554,
0.08412587642669678,
-0.017151150852441788,
-0.022402862086892128,
-0.02897672913968563,
-0.04793436452746391,
-0.0024151932448148727,
-0.048793528228998184,
0.08283785730600357,
-0.03485516086220741,
0.04931119829416275,
0.03155790641903877,
0.046173345297575,
0.10544... | -0.0591 |
range of use cases. The primary constraints on parsing limits are available RAM and CPU. We recommend tuning your JSON parsing limits down from the defaults to match your specific application needs and available resourcess. Due to the way the parsing limits interact, running with permissive defaults in a low-resource e... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.04581805691123009,
0.029611850157380104,
-0.018575862050056458,
-0.04984840750694275,
-0.05692698806524277,
-0.08651188760995865,
-0.09637178480625153,
0.09918943792581558,
-0.03874925151467323,
-0.061918601393699646,
-0.000827662879601121,
0.02634434774518013,
-0.036365609616041183,
0.... | 0.163674 |
"tcp" { address = "10.0.0.5:8200" } # Advertise the non-loopback interface api\_addr = "https://10.0.0.5:8200" cluster\_addr = "https://10.0.0.5:8201" ``` ### Configuring unauthenticated metrics access This example shows enabling unauthenticated metrics access. ```hcl listener "tcp" { telemetry { unauthenticated\_metri... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
-0.03209865838289261,
0.05737840011715889,
-0.08623365312814713,
0.0002169426588807255,
-0.04697224870324135,
-0.043177831918001175,
0.037208884954452515,
-0.020961549133062363,
-0.018317092210054398,
-0.06506765633821487,
0.0068515571765601635,
-0.09010101109743118,
0.014451220631599426,
... | 0.076615 |
the empty string (`""`). ```shell-session $ curl -s https://127.0.0.1:8200/v1/sys/leader | jq`: { "ha\_enabled": true, "is\_self": false, "active\_time": "0001-01-01T00:00:00Z", "leader\_address": "", "leader\_cluster\_address": "", "performance\_standby": false, "performance\_standby\_last\_remote\_wal": 0, "raft\_com... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/index.mdx | main | vault | [
0.007730503566563129,
0.09243987500667572,
-0.031068049371242523,
0.049571238458156586,
0.007623335346579552,
-0.036094531416893005,
0.003158936044201255,
-0.004710685927420855,
0.07354097068309784,
0.029801782220602036,
0.04940853640437126,
-0.04261910542845726,
-0.01590455323457718,
-0.0... | 0.10659 |
# Configure TLS for your Vault TCP listener You can configure your TCP listener to use specific versions of TLS and specific ciphersuites. ## Assumptions - \*\*Your Vault instance is not currently running\*\*. If your Vault cluster is running, you must [restart the cluster gracefully](https://support.hashicorp.com/hc/e... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/tcp-tls.mdx | main | vault | [
0.02572096511721611,
0.09567283093929291,
-0.05080467835068703,
-0.039730288088321686,
-0.05935975909233093,
-0.05986936762928963,
-0.04426915571093559,
-0.09500715881586075,
0.09855443239212036,
-0.042961347848176956,
-0.01972632296383381,
-0.010749632492661476,
0.06467457860708237,
0.058... | -0.065138 |
Jun 16 17:27:29 2024 GMT ``` ```shell-session sslscan 127.0.0.1:8200 Testing SSL server 127.0.0.1 on port 8200 using SNI name 127.0.0.1 SSL/TLS Protocols: SSLv2 disabled SSLv3 disabled TLSv1.0 disabled TLSv1.1 disabled TLSv1.2 enabled TLSv1.3 enabled Supported Server Cipher(s): Preferred TLSv1.3 128 bits TLS\_AES\_128\... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/listener/tcp/tcp-tls.mdx | main | vault | [
-0.02160682901740074,
0.04955637454986572,
-0.01149672456085682,
-0.05653521791100502,
-0.006894958671182394,
-0.06312467902898788,
-0.08993086218833923,
-0.05383281037211418,
0.014467752538621426,
-0.013610700145363808,
-0.03848320245742798,
0.011209607124328613,
0.054925624281167984,
0.0... | -0.04568 |
# HSM PKCS11 seal configuration Auto-unseal \*\*and\*\* seal wrapping for PKCS11 require Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap](/vault/docs/enterprise/sealwrap) overvie... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
-0.021711446344852448,
0.07144170254468918,
-0.051441583782434464,
-0.046088092029094696,
-0.02047378569841385,
-0.01055874302983284,
-0.06764049082994461,
-0.0018079286674037576,
-0.0265251062810421,
-0.060622796416282654,
-0.018289482221007347,
-0.031969621777534485,
0.016783244907855988,
... | -0.056771 |
The PIN for login. May also be specified by the `VAULT\_HSM\_PIN` environment variable. \_If set via the environment variable, it will need to be re-set if Vault is restarted.\_ - `key\_label` `(string: )`: The label of the key to use. If the key does not exist and generation is enabled, this is the label that will be ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
0.019291263073682785,
0.006980872713029385,
-0.09116773307323456,
-0.02532137557864189,
-0.005535396747291088,
0.006318764295428991,
0.023848757147789,
-0.002282863948494196,
0.024110127240419388,
-0.08382820338010788,
0.08678536862134933,
0.01582108624279499,
0.0421769954264164,
0.0131379... | -0.050532 |
has occurred post cluster initialization, it is advisable to disable this flag to prevent any unintended key creation in the future. - `force\_rw\_session` `(string: "false")`: Force all operations to open up a read-write session to the HSM. This is a boolean expressed as a string (e.g. `"true"`). May also be specified... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
0.010972626507282257,
0.025288695469498634,
-0.06864384561777115,
0.02081952430307865,
0.006673204712569714,
0.0014257647562772036,
-0.03610968589782715,
-0.053435612469911575,
0.015028933063149452,
0.037485551089048386,
0.03245283290743828,
0.004540190100669861,
0.04338419437408447,
-0.05... | -0.060161 |
be used for decryption) - `CKA\_UNWRAP`: `true` (Key can be used for unwrapping) - `CKA\_TOKEN`: `true` (Key persists to the slot/token rather than being for one session only) - `CKA\_EXTRACTABLE`: `false` (Key cannot be exported) ### HMAC key - `CKA\_CLASS`: `CKO\_SECRET\_KEY` (It's a secret key) - `CKA\_KEY\_TYPE`: `... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/pkcs11.mdx | main | vault | [
-0.06063961237668991,
0.052827347069978714,
-0.056782227009534836,
-0.03401210904121399,
-0.05237428843975067,
0.006144052371382713,
0.02873484417796135,
0.01809934712946415,
0.03447206690907478,
0.004333398770540953,
0.02713899500668049,
-0.03712794929742813,
0.03846263140439987,
-0.01963... | 0.01073 |
# GCP Cloud KMS seal configuration All Vault versions support \*\*auto-unseal\*\* for GCP Cloud, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wra... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/gcpckms.mdx | main | vault | [
0.029614461585879326,
0.03446095064282417,
0.04886431246995926,
-0.03495578467845917,
-0.044739626348018646,
-0.023747658357024193,
0.019563887268304825,
-0.029528072103857994,
0.002185753546655178,
0.0009675213950686157,
-0.004511355888098478,
-0.02655891329050064,
0.046880170702934265,
0... | -0.031004 |
the primary key version. ## Tutorial Refer to the [Auto-unseal using GCP Cloud KMS](/vault/tutorials/auto-unseal/autounseal-gcp-kms) guide for a step-by-step tutorial. | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/gcpckms.mdx | main | vault | [
-0.018333913758397102,
-0.0017206190386787057,
0.05682714655995369,
-0.05147380381822586,
-0.009952244348824024,
0.003218343248590827,
-0.017145531252026558,
-0.07634814828634262,
-0.03567852824926376,
0.007740985602140427,
-0.00134040298871696,
0.016923420131206512,
0.05004924163222313,
-... | 0.047653 |
# Auto-unseal best practices for the Transit plugin This document provides a framework for creating a usable solution for auto-unseal using Vault when HSM or cloud-based KMS auto-unseal mechanism is not available for your environment, such as in an internal data center deployment. ## Glossary - \*\*Region\*\*: A networ... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/transit-best-practices.mdx | main | vault | [
0.002218099543824792,
-0.03113570623099804,
-0.0069619398564100266,
0.022187991067767143,
-0.02252938225865364,
-0.018742157146334648,
-0.0730876699090004,
-0.049020346254110336,
-0.020017625764012337,
-0.006346658803522587,
0.0008545549935661256,
0.005180048290640116,
0.06270409375429153,
... | 0.156532 |
material. You can deploy the unsealing Vault cluster on a small virtual machine or container. To minimize the resource, it can run as a single-node cluster. For simplicity, using a non-HA supporting backend, such as a [filesystem storage backend](/vault/docs/configuration/storage/filesystem), is a common practice. ## P... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/transit-best-practices.mdx | main | vault | [
0.03461167588829994,
0.023069282993674278,
-0.042117223143577576,
0.036398984491825104,
-0.009872774593532085,
-0.015308146364986897,
-0.09167428314685822,
0.0063255359418690205,
-0.009279544465243816,
-0.05363130196928978,
-0.0296795517206192,
-0.02053782343864441,
0.1062435507774353,
-0.... | 0.000446 |
# `seal` stanza The `seal` stanza configures the seal type to use for additional data protection, such as using HSM or Cloud KMS solutions to encrypt and decrypt the root key. This stanza is optional, and in the case of the root key, Vault will use the Shamir algorithm to cryptographically split the root key if this is... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/index.mdx | main | vault | [
0.02277611941099167,
0.05584424361586571,
-0.05160444974899292,
-0.05859784409403801,
-0.014870254322886467,
-0.044520679861307144,
-0.02017020806670189,
0.06300445646047592,
-0.007211979012936354,
-0.03173276409506798,
0.02019442990422249,
0.010042322799563408,
0.08324022591114044,
-0.024... | -0.055752 |
# Transit seal configuration All Vault versions support \*\*auto-unseal\*\* for Transit, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap](/vaul... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/transit.mdx | main | vault | [
0.02140001580119133,
0.036544069647789,
0.022094186395406723,
0.006936412304639816,
-0.05859516188502312,
-0.01868620328605175,
-0.031200705096125603,
-0.04075445979833603,
0.01459153275936842,
-0.06902629137039185,
-0.022683236747980118,
-0.03393150120973587,
0.043980661779642105,
0.00808... | 0.008403 |
values must be provided, either as environment variables or as configuration parameters. ~> \*\*Note:\*\* Although the configuration file allows you to pass in `VAULT\_TOKEN` as part of the seal's parameters, it is \_strongly\_ recommended to set these values via environment variables. The Vault token used to authentic... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/transit.mdx | main | vault | [
-0.01214801799505949,
0.016273362562060356,
-0.02812868356704712,
-0.036143530160188675,
-0.0392707884311676,
-0.03716304898262024,
-0.007802185136824846,
0.044222909957170486,
0.017810489982366562,
-0.05884043127298355,
0.04029103368520737,
-0.01685134880244732,
0.08554520457983017,
0.009... | -0.018471 |
# AliCloud KMS seal configuration All Vault versions support \*\*auto-unseal\*\* for AliCloud, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap]... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/alicloudkms.mdx | main | vault | [
0.015069933608174324,
0.05747523158788681,
-0.0042375982739031315,
-0.024957867339253426,
-0.013188374228775501,
-0.038128580898046494,
0.024172158911824226,
-0.040303025394678116,
0.026881271973252296,
-0.027114873751997948,
0.009871067479252815,
-0.029610153287649155,
0.05380389094352722,
... | 0.001708 |
# OCI KMS seal configuration All Vault versions support \*\*auto-unseal\*\* for OCI KMS, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap](/vaul... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/ocikms.mdx | main | vault | [
0.009411443024873734,
0.05026582255959511,
-0.007920225150883198,
0.003633439540863037,
-0.018410181626677513,
-0.12250761687755585,
-0.0023707037325948477,
-0.01098855771124363,
0.025710875168442726,
-0.09262057393789291,
0.017059404402971268,
-0.03644894063472748,
0.029513277113437653,
0... | 0.034448 |
KMS's keys in tenant B: ```text define tenancy tenantB as endorse dynamic-group to use keys in tenancy tenantB ``` ```text define tenancy tenantA as define dynamic-group as admit dynamic-group of tenancy tenantA to use keys in compartment ``` ## `ocikms` rotate OCI KMS master key For the [OCI KMS key rotation feature][... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/ocikms.mdx | main | vault | [
0.01978830061852932,
0.03508500009775162,
-0.050891708582639694,
-0.030392292886972427,
-0.043866999447345734,
-0.05154058709740639,
0.022530430927872658,
-0.046460505574941635,
0.06411480158567429,
-0.0061933547258377075,
0.09843463450670242,
-0.016294313594698906,
0.12485042959451675,
-0... | -0.039313 |
# Sealing best practices This documentation explains the concepts, options, and considerations for unsealing a production Vault cluster. It builds on the [Reference Architecture](/vault/tutorials/raft/raft-reference-architecture) and [Deployment Guide](/vault/tutorials/day-one-raft/raft-deployment-guide) for Vault to d... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/seal-best-practices.mdx | main | vault | [
-0.028943441808223724,
0.038316722959280014,
-0.034163717180490494,
-0.0018937085988000035,
0.024615488946437836,
-0.07030964642763138,
-0.07974770665168762,
-0.031979043036699295,
0.00951209757477045,
-0.03428906202316284,
0.018740857020020485,
0.07212212681770325,
0.016514647752046585,
-... | 0.003422 |
unseal operation. - [AWS KMS](/vault/docs/configuration/seal/awskms) - [Azure Key Vault](/vault/docs/configuration/seal/azurekeyvault) - [GCP Cloud KMS](/vault/docs/configuration/seal/gcpckms) - [AliCloud KMS](/vault/docs/configuration/seal/alicloudkms) - [OCI KMS](/vault/docs/configuration/seal/ocikms) For all of thes... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/seal-best-practices.mdx | main | vault | [
-0.0653766617178917,
0.020931296050548553,
0.005564069375395775,
-0.009609443135559559,
-0.012532238848507404,
-0.005829912144690752,
0.008759445510804653,
-0.011654405854642391,
0.07090180367231369,
0.046146124601364136,
0.032997842878103256,
0.04681063070893288,
0.10623950511217117,
-0.0... | 0.047817 |
for production use - Recommended Pattern - Vault Centralized Secrets Management - [K/V Secrets Engine](/vault/docs/secrets/kv) is used to store static secrets within the configured physical storage for Vault - [Auth Methods](/vault/docs/auth) are used to authenticate users and machines with Vault - [Auto unseal tutoria... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/seal-best-practices.mdx | main | vault | [
-0.07906097173690796,
0.061806339770555496,
-0.11598116904497147,
-0.06597098708152771,
-0.008348613977432251,
-0.015463178046047688,
-0.041949380189180374,
0.03283917158842087,
0.02414747141301632,
-0.01316280011087656,
0.04229159653186798,
0.0680132508277893,
-0.026730140671133995,
-0.01... | 0.245415 |
# AWS KMS seal configuration All Vault versions support \*\*auto-unseal\*\* for AWS, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [Seal wrap](/vault/do... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/awskms.mdx | main | vault | [
0.02226714976131916,
0.08540806919336319,
-0.009141035377979279,
-0.0055274348706007,
-0.009991112165153027,
-0.026269618421792984,
0.0020642185118049383,
-0.03868705406785011,
0.036301642656326294,
-0.00955238938331604,
-0.013587803579866886,
-0.059440307319164276,
0.07512105256319046,
-0... | -0.008862 |
- `kms:DescribeKey` These can be granted via IAM permissions on the principal that Vault uses, on the KMS key policy for the KMS key, or via KMS Grants on the key. ## `awskms` environment variables Alternatively, the AWS KMS seal can be activated by providing the following environment variables. Vault Seal specific val... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/awskms.mdx | main | vault | [
0.017070988193154335,
0.08809676766395569,
-0.0592554435133934,
-0.06996452808380127,
-0.012819320894777775,
-0.008188973180949688,
-0.002573678269982338,
-0.003679397515952587,
0.06350766867399216,
0.07178211957216263,
0.05688244104385376,
0.016950547695159912,
0.11959816515445709,
-0.072... | -0.039609 |
# Azure Key Vault seal configuration All Vault versions support \*\*auto-unseal\*\* for Azure Key Vault, but \*\*seal wrapping\*\* requires Vault Enterprise. Vault Enterprise enables seal wrapping by default, which means the KMS service must be available at runtime and not just during the unseal process. Refer to the [... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/azurekeyvault.mdx | main | vault | [
0.028827914968132973,
0.04628301039338112,
-0.011322308331727982,
0.01461789757013321,
-0.04421829804778099,
-0.001176034682430327,
0.01730998419225216,
-0.04956029728055,
0.025620216503739357,
0.0391957126557827,
0.011625318787992,
-0.024481577798724174,
0.08509298413991928,
0.02475428208... | -0.039572 |
the Azure Key Vault seal can be activated by providing the following environment variables: - `VAULT\_AZUREKEYVAULT\_VAULT\_NAME` - `VAULT\_AZUREKEYVAULT\_KEY\_NAME` ## Key rotation This seal supports rotating keys defined in Azure Key Vault. Key metadata is stored with the encrypted data to ensure the correct key is u... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/azurekeyvault.mdx | main | vault | [
-0.008169807493686676,
-0.033643946051597595,
-0.06510496139526367,
-0.008014204911887646,
-0.04478095471858978,
0.04078412428498268,
0.04113692417740822,
-0.052402984350919724,
0.07662921398878098,
0.0889093354344368,
0.060658734291791916,
0.06736587733030319,
0.09193592518568039,
0.00588... | -0.071817 |
# Configure high availability for Vault seals @include 'alerts/enterprise-only.mdx' [Seal High Availability](/vault/docs/concepts/seal#seal-high-availability-enterprise) provides the means to configure at least two auto-seals (and no more than three) in order to have resilience against outage of a seal service or mecha... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/seal-ha.mdx | main | vault | [
0.0472058430314064,
0.03963659703731537,
-0.04843145236372948,
-0.03940819576382637,
-0.03301442414522171,
-0.043486595153808594,
-0.003865982173010707,
-0.00872052926570177,
0.003302019787952304,
-0.06107572093605995,
-0.00956355407834053,
0.02802235446870327,
0.05876225233078003,
0.00616... | -0.032908 |
a seal, remove the corresponding seal stanza and restart. There must be at least one seal remaining. It is highly recommended to take a snapshot of your Vault storage before applying any seal configuration change. Once Vault unseals with the new seal configuration, it will be available to process traffic even as re-wra... | https://github.com/hashicorp/web-unified-docs/blob/main//content/vault/v1.21.x/content/docs/configuration/seal/seal-ha.mdx | main | vault | [
0.006636202801018953,
0.06999906152486801,
-0.004088564310222864,
0.016519226133823395,
-0.028392590582370758,
-0.03598595783114433,
0.0210864394903183,
-0.07947809249162674,
0.020762011408805847,
0.05627913028001785,
0.03135716915130615,
-0.010520058684051037,
0.10101081430912018,
-0.0218... | -0.082459 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.