Vault Proxy Configuration
Configuring Secrets with HashiCorp Vault Proxy
Configuring HashiCorp Vault Proxy
-
Set the
VAULT_ADDRenvironment variable to point to your proxy endpointCustom Endpoint:
export VAULT_ADDR=https://your_gw_url:8200Akeyless SaaS Proxy:
export VAULT_ADDR=https://hvp.akeyless.io
Note: Custom Gateways require port :8200 for Vault Proxy traffic.
-
Now, you'll need to configure the authentication token that would be used by Vault CLI to fetch secrets from Akeyless.
Set your Akeyless token in
~/.vault-token:Access Id..Access Key, for example:AccessID..AccessKey -
Verify
"hvp_route_version"is set to2on the gateway (Custom Gateway Only):akeyless gateway get defaults --gateway-url <your_gateway_url>
For Custom Gateways, ensure that hvp_route_version is set to 2.
Legacy Route Version 1:If your environment strictly requires
hvp_route_version": 1, please refer to our Legacy HVP Configuration Guide.
Examples
The following section shows the usage of working with the vault CLI to manage resources in your Akeyless account:
Fetching Secrets:
To retrieve a Dynamic, Rotated and Static using the Vault CLI via HashiCorp Vault Proxy, run:
vault read /<full_secret_name>Create or Update a Static Secret
Create a new static secret in Akeyless. If it already exists, it will add a new version of that secret.
Usage
vault kv put secret/{secret-name} {my-key}={my-value}
Delete a Static Secret
To delete a secret from Akeyless:
vault kv delete secret/{secret-name}
Updated about 5 hours ago
