mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
29 lines
1.3 KiB
Plaintext
29 lines
1.3 KiB
Plaintext
---
|
|
title: "Key Management Service (KMS) Configuration"
|
|
sidebarTitle: "Overview"
|
|
description: "Learn how to configure your project's encryption"
|
|
---
|
|
|
|
## Introduction
|
|
|
|
KMS leverages a Key Management Service (KMS) to securely encrypt and decrypt secrets in your projects.
|
|
|
|
## Overview
|
|
|
|
KMS's KMS ensures the security of your project's secrets through the following mechanisms:
|
|
|
|
- Each project is assigned a unique workspace key, which is responsible for encrypting and decrypting secret values.
|
|
- The workspace key itself is encrypted using the project's configured KMS.
|
|
- When secrets are requested, the workspace key is derived from the configured KMS. This key is then used to decrypt the secret values on-demand before sending them to the requesting client.
|
|
|
|
## Configuration
|
|
|
|
You can set the KMS for new projects during project creation.
|
|
|
|
For existing projects, you can configure the KMS from the Project Settings page.
|
|
|
|
|
|
## External KMS
|
|
|
|
KMS supports the use of external KMS solutions to enhance security and compliance. You can configure your project to use services like [AWS Key Management Service](./aws-kms) or [GCP Key Management Service](./gcp-kms) for managing encryption.
|