Vault Associate Studying - Setup

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/7

flashcard set

Earn XP

Description and Tags

Installing and testing the Vault binary

8 Terms

1
New cards

(T/F) Vault is platform agnostic

True. Vault can run on bare metal, virtual machines, within Kubernetes, locally, etc.

2
New cards

Order of operations for installing and setting up Vault

  1. Install Vault (brew, build, package manager, etc.)

  2. Create configuration file(s)

  3. Initialize vault (vault init)

  4. Unseal vault


3
New cards

Benefits of Vault Dev mode. (vault server -dev)

  • Quickly run Vault without configuration

  • Automatically initialize and unseal

  • Enables the UI

  • Provides an unseal key

  • Automatically logs in as root


In short, this is great for trying out new features in Vault or POCing


4
New cards

Drawbacks of Vault Dev mode.

  • Non-persistent, in-memory storage

  • Insecure/No TLS

  • Sets listener to localhost:8200

  • Always mounts a kv v2 secret engine

  • provides a root token


TLDR, this is insecure and brittle.


5
New cards

Running Vault in Production

  1. Deploy one or more persistent nodes via HCL configuration files

  2. Select a storage backend based on preference/requirements

  3. Multiple Vault nodes will be configured as a cluster

  4. Deploy “close” to applications


Ideally, the provisioning of Vault will be automated in some manner


6
New cards

How to manage running Vault service

SystemCTL or Windows service manager


For linux, you’ll need a systemd file.

7
New cards

(T/F) Single node Vault is a recommended configuration for production Vault

FALSE. There is no redundancy or scalability here.

8
New cards