Skip to content

Deployment ​

OpenKCM runs as a set of deployments: central components that every region uses, one CMK deployment per CMK region, Krypton, and the provider's own services in their system regions. This page shows where each component runs and where the data of a tenant lives. For sizing, dependencies, ports and the installation order, see Deployment planning.

Deployments ​

DeploymentRunsHow manyHolds
CentralRegistry, CMK-2-Krypton BridgeOneRegistry: every tenant with its CMK region, every system and the tenant it belongs to. Bridge: its jobs and the keys it manages in Krypton
CMK regionCMK, CMK UI, Envoy Gateway with ExtAuthZ, Session ManagerOne per CMK region, for example emea, usThe tenants of the region: keys, key configurations, groups, approvals, system links, sessions. Regions share nothing
KryptonRoot node, agentsOne root node; agents where workloads need keys close to themKey metadata in PostgreSQL, sealed key material in OpenBao
System regionThe provider's servicesWhere the services run, for example eu10, eu20The systems that use the keys. Each CMK region serves a set of system regions

Topology ​

Central components ​

The Registry knows every tenant and the CMK region that serves it, and every system and the tenant it belongs to. It sends each tenant's jobs to the CMK of that region.

The CMK-2-Krypton Bridge is a central component, like the Registry. It serves the CMKs of all regions: it receives their key and system tasks, offers an API to onboard tenants and manage their Domain (System) keys in Krypton, and registers the tenants and systems it creates keys for in the Registry. It is the only component that calls Krypton on behalf of CMK.

Current state

Today one Bridge instance reads the tasks of one CMK region. See the Bridge's current state.

CMK regions and system regions ​

Two kinds of region make up an OpenKCM deployment:

RegionExampleWhat it is
CMK regionemea, usA regional CMK deployment. It serves the tenants assigned to it, with its own UI, API, gateway, sign-in and databases
System regioneu10, eu20, us10Where the provider's services run. A CMK region sends key and system tasks to each system region it serves

A tenant belongs to exactly one CMK region. Its systems can run in any of the system regions that its CMK region serves.

Krypton ​

Krypton has one root node, which holds the top of every key hierarchy and the key metadata of all tenants. Agents take over the lower levels of a hierarchy for a part of the topology, for example a region, so that workloads get their keys close to where they run. The root node sends each agent the keys of its segment. See Krypton architecture.

Where data lives ​

Data residency follows the CMK region: the databases of a tenant's CMK region keep its key configurations, groups, approvals and settings. Only the central components are shared, and they hold no key material.

DataHeld byWhere
Tenants, their CMK region and identity provider settings; systems and the tenant each belongs to; the IDs of their keysRegistryCentral PostgreSQL database
The Bridge's jobs, and the IDs of the keys it manages in KryptonCMK-2-Krypton BridgeCentral PostgreSQL database
Key configurations, key metadata, groups, approvals, system links, per tenantCMKPostgreSQL database of the CMK region, one schema per tenant
Browser sessionsSession ManagerValkey or Redis of the CMK region
Customer keys (L1)KeystoreA keystore that the provider runs for the tenant (BYOK), or the customer's own keystore (HYOK); AWS KMS today
Key hierarchies below the customer key (L2 to L4)KryptonKey metadata in the PostgreSQL database of the root node and of each agent; key material sealed, in OpenBao

See also ​

EU and German government funding logos

Funded by the European Union – NextGenerationEU.

The views and opinions expressed are solely those of the author(s) and do not necessarily reflect the views of the European Union or the European Commission. Neither the European Union nor the European Commission can be held responsible for them.