mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
- 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
33 lines
2.6 KiB
Plaintext
33 lines
2.6 KiB
Plaintext
---
|
|
title: "Secrets Management"
|
|
sidebarTitle: "Overview"
|
|
description: "Learn how to securely store, access, and manage sensitive application secrets."
|
|
---
|
|
|
|
KMS provides a flexible platform for managing secrets such as API keys, database credentials, and application configuration across every stage of the development lifecycle — from local development to production. It enables teams to eliminate hardcoded secrets, enforce fine-grained access controls, deliver secrets across their infrastructure, and adopt secure workflows like secret rotation and dynamic secrets.
|
|
|
|
The short video below provides a guided overview of KMS's secrets management capabilities and key concepts, helping you build the right mental model before diving into the rest of the documentation.
|
|
|
|
<br />
|
|
|
|
|
|
<div style={{ position: "relative", paddingBottom: "56.25%", height: 0, overflow: "hidden", maxWidth: "100%" }}>
|
|
<iframe
|
|
src="https://www.youtube.com/embed/BMeng7nkRYs"
|
|
title="YouTube video player"
|
|
style={{ position: "absolute", top: 0, left: 0, width: "100%", height: "100%", border: 0 }}
|
|
allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
|
|
allowfullscreen
|
|
></iframe>
|
|
</div>
|
|
|
|
<br />
|
|
|
|
KMS's core secrets management capabilities include:
|
|
|
|
- Secret Stores: Secure, versioned storage scoped by [project](/documentation/platform/secrets-mgmt/project), [environment](/documentation/platform/secrets-mgmt/project#project-environments), and [path](/documentation/platform/folder).
|
|
- [Access Control](/documentation/platform/access-controls/overview): Fine-grained, identity-aware permissions for users and machines
|
|
- [Secret Delivery](/documentation/platform/secrets-mgmt/concepts/secrets-delivery): Access secrets via [CLI](/cli/overview), [SDKs](/sdks/overview) (Go, Node.js, Python, etc.), [HTTP API](/api-reference/overview/introduction), [agents](/integrations/platforms/kms-agent), [Kubernetes Operator](/integrations/platforms/kubernetes/overview), [External Secrets Operator (ESO)](https://external-secrets.io/latest/provider/kms), and more.
|
|
- Lifecycle Automation: Automate [secret rotation](/documentation/platform/secrets-mgmt/concepts/secrets-rotation), generate [dynamic secrets](/documentation/platform/secrets-mgmt/concepts/dynamic-secrets), and enforce [approval-based workflows](/documentation/platform/pr-workflows).
|
|
- [Secrets Syncs](/integrations/secret-syncs/overview): Push secrets to external services like [GitHub](/integrations/secret-syncs/github), [GitLab](/integrations/secret-syncs/gitlab), [AWS Secrets Manager](/integrations/secret-syncs/aws-secrets-manager), [Vercel](/integrations/secret-syncs/vercel), and more.
|