π Keys under customer control
Bring your own key material (BYOK), or hold your own key (HYOK) in your own keystore. Disable a key, and every system that uses it is informed.
About CMK
Cloud customers stay in control of their data: they bring their own key or keep it in their own keystore, decide who may manage it, and withdraw it from every service and region at once. Krypton, the key engine, creates the key hierarchies that protect the data and delivers keys to workloads.
| You are⦠| Start here | Then |
|---|---|---|
| Evaluating OpenKCM for your platform | Overview | Core concepts, Trust model |
| A customer who manages keys in CMK: tenant administrator, key administrator or auditor | Manage your keys | Keys, Approvals |
| Building a cloud service that encrypts data with customer keys | Connect a regional system | CMK API, Krypton |
| Operating the platform that runs CMK | Deployment planning | Install the Registry, Install a regional deployment, Connect a regional tenant, Operations |
| Contributing to OpenKCM | Contributing | Releases, Roadmap |
| Looking for help, or reporting a problem or a vulnerability | Community and support | Releases |
New to the terms? The glossary explains them all.