diff --git a/docs/integrations/app-connections/hashicorp-vault.mdx b/docs/integrations/app-connections/hashicorp-vault.mdx index de38f24f9..eb4420d5d 100644 --- a/docs/integrations/app-connections/hashicorp-vault.mdx +++ b/docs/integrations/app-connections/hashicorp-vault.mdx @@ -39,19 +39,28 @@ Infisical supports two methods for connecting to Hashicorp Vault. You may name your policy whatever you want, but remember the name as it will be used in future steps. - - Ensure that you replace the policy path so that it matches with an existing KV Secrets Engine mount and path. - + Depending on your use case, you may have different policy configurations: - ```hcl - path "demo_mount/data/demo_path/demo_subpath" { - capabilities = [ "create", "read", "update" ] - } + + + ```hcl + path "demo_mount/data/demo_path/demo_subpath" { + capabilities = [ "create", "read", "update" ] + } - path "sys/mounts" { - capabilities = ["read"] - } - ``` + path "sys/mounts" { + capabilities = ["read"] + } + ``` + + - **demo_mount**: The name of the target secrets engine (e.g., 'secret', 'kv'). + - **demo_path/demo_subpath**: The specific path within the secrets engine where secrets are stored. + + + Ensure that you replace the policy path so that it matches with an existing KV Secrets Engine mount and path. + + + ![Vault Create Policy](/images/app-connections/hashicorp-vault/vault-create-policy.png)