secrets enable command enables an secrets engine at a given path. If an
secrets engine already exists at the given path, an error is returned. After the
secrets engine is enabled, it usually needs configuration. The configuration
varies by secrets engine.
By default, secrets engines are enabled at the path corresponding to their TYPE,
but users can customize the path using the
Some secrets engines persist data, some act as data pass-through, and some generate dynamic credentials. The secrets engine will likely require configuration after it is mounted. For details on the specific configuration options, please see the secrets engine documentation.
Enable the AWS secrets engine at "aws/":
$ vault secrets enable aws Success! Enabled the aws secrets engine at: aws/
Enable the SSH secrets engine at ssh-prod/:
$ vault secrets enable -path=ssh-prod ssh
Enable the database secrets engine with an explicit maximum TTL of 30m:
$ vault secrets enable -max-lease-ttl=30m database
Enable a custom plugin (after it is registered in the plugin registry):
$ vault secrets enable -path=my-secrets my-plugin
For more information on the specific configuration options and paths, please see the secrets engine documentation.
The following flags are available in addition to the standard set of flags included on all commands.
(duration: "")- The default lease TTL for this secrets engine. If unspecified, this defaults to the Vault server's globally configured default lease TTL.
(string: "")- Human-friendly description for the purpose of this engine.
(bool: false)- Force the secrets engine to disable caching. If unspecified, this defaults to the Vault server's globally configured cache settings. This does not affect caching of the underlying encrypted data storage.
(bool: false)- Mark the secrets engine as local-only. Local engines are not replicated or removed by replication.
(duration: "")The maximum lease TTL for this secrets engine. If unspecified, this defaults to the Vault server's globally configured maximum lease TTL.
(string: "")Place where the secrets engine will be accessible. This must be unique cross all secrets engines. This defaults to the "type" of the secrets engine.