ec620a7765
* implement mdx remote * fix an unfenced code block * fix partials path Co-authored-by: Jim Kalafut <jkalafut@hashicorp.com>
34 lines
1 KiB
Plaintext
34 lines
1 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: secrets disable - Command
|
|
sidebar_title: <code>disable</code>
|
|
description: |-
|
|
The "secrets disable" command disables an secrets engine at a given PATH. The
|
|
argument corresponds to the enabled PATH of the engine, not the TYPE! All
|
|
secrets created by this engine are revoked and its Vault data is removed.
|
|
---
|
|
|
|
# secrets disable
|
|
|
|
The `secrets disable` command disables an secrets engine at a given PATH. The
|
|
argument corresponds to the enabled PATH of the engine, not the TYPE! All
|
|
secrets created by this engine are revoked and its Vault data is removed.
|
|
|
|
When a secrets engine is disabled, **all secrets generated via the secrets
|
|
engine are immediately revoked.** Care should be taken when disabling a
|
|
secret mount with a large number of secrets, as it can cause a high load on
|
|
the system during revocation time.
|
|
|
|
## Examples
|
|
|
|
Disable the secrets engine enabled at aws/:
|
|
|
|
```shell-session
|
|
$ vault secrets disable aws/
|
|
```
|
|
|
|
## Usage
|
|
|
|
There are no flags beyond the [standard set of flags](/docs/commands)
|
|
included on all commands.
|