Create Vault

Choose how you manage your Vault

Terraform

Terraform Registry Take a look at Terraform registry

Caution

Sensitive information is also stored in the Terraform state. The Terraform backend is therefore particularly worthy of protection.

Example Git Repo A sample implementation of this Getting Started

Setup

Add the dependency to your main.tf

terraform {
  required_providers {
    cryptvault = {
      source = "cryptvault-cloud/cryptvault"
    }
  }
}

Configure Provider

provider "cryptvault" {}

terraform init

Create your Vault

Two pieces of information are required to create a Vault.

• name a name of your choice to uniquely identify your Vault
• token you created at console.cryptvault.cloud see by previous step

resource "cryptvault_cloud_vault" "my_vault" {
  name  = "name_of_your_vault"
  token = "token_allow_you_to_create_vault"
}

terraform apply

Operator identity

When the cryptvault_cloud_vault resource is created, an operator identity is generated in the background on the client side.

Good to know

Primarily, the key pair (public and private key) is generated on the client side.

This operator has all the rights to:

• create additional identities
• Access all secrets
• manage the Vault itself

Cli

Setup

Tip

with Go

If you have go installed, you can just do

go install github.com/cryptvault-cloud/vault-cli@latest

with Docker

You can also simply use the CLI via Docker image.

Only mount local volume to /work to persist data.

sudo docker run -it --entrypoint='/bin/sh' -w /work -v ./cryptvault:/work ghcr.io/cryptvault-cloud/vault-cli:latest

Now you can run vault-cli commands and files will be saved to the filesystem.

Github Repo of CLI-Tool Download and install binary for your needed OS

In this example we called the binary vault-cli

# free to choose name
export VAULT_CLI_VAULTNAME=name_of_your_vault
# you found this token at https://console.cryptvault.cloud
export VAULT_CLI_VAULTTOKEN=token_allow_you_to_create_vault
vault-cli create_vault

It will create a .cryptvault directory in your current location In this folder you will find information about your Vault and Operator/Identity keys.

Good to know

You can manage more than one Vault locally. To switch between the different vaults, you need to change context. See vault-cli local --help

Operator identity

When the create_vault command is executed, an operator identity is created in the background on the client side.

You can find the keys in the .cryptvault folder

This operator has all the rights to:

• create additional identities
• Access all secrets
• manage the Vault itself

With docker

If you are using Docker CLI, make sure that the .cryptvault folder is successfully available on the host system.

Caution

The .cryptvault folder contains sensitive information and access keys that cannot be recovered if lost. You need to protect the files in this folder from unauthorised access and ensure that this data is not lost by making backups.

Learn more about identities by cryptVault