Skip to main content
In this guide, you’ll walk through unsealing a Vault server using Vault’s default Shamir Secret Sharing mechanism. We’ll cover checking the Vault status, reviewing configuration, initializing Vault to generate key shards, unsealing with those shards, and finally authenticating and listing secrets engines.

Prerequisites

Ensure you have write permissions to /etc/vault.d and that Vault can read this directory.

1. Check Vault Status

Before initialization, verify Vault is neither initialized nor unsealed:
Expected output:

2. Review Vault Configuration

Vault uses Shamir’s Secret Sharing by default, so you don’t need a seal stanza. Confirm your config resembles:
You can find more on Vault seal configurations in the Vault Seal/Unseal Concepts guide.

3. Initialize Vault

Initialization generates the unseal key shares (5 shares, threshold 3) and the initial root token. Keep these secrets secure—any 3 shares will unseal the Vault.
Sample output:
After initialization, Vault remains sealed:
Store unseal keys and root tokens in a secure location. Exposure of these allows full control over your Vault.

4. Unseal Vault

Run the unseal command three times, providing a different key each time:
Repeat until Unseal Progress reaches 3/3:
Vault is now unsealed and ready for operations.

5. Authenticate and List Secrets Engines

Log in with your initial root token, then view the enabled secrets engines:
Expected output:

Watch Video