Git-Mirrors/constellation
1
0
Fork 0
mirror of https://github.com/edgelesssys/constellation.git synced 2024-09-20 00:06:21 +00:00
Code Issues Packages Projects Releases Wiki Activity
57786db96b
constellation/keyservice
History
Daniel Weiße 5eb73706f5
internal: refactor storage credentials (#1071) 
* Move storage clients to separate packages

* Allow setting of client credentials for AWS S3

* Use managed identity client secret or default credentials for Azure Blob Storage

* Use credentials file to authorize GCS client

---------

Signed-off-by: Daniel Weiße <dw@edgeless.systems>
2023-03-02 15:08:31 +01:00
..
cmd internal: refactor storage credentials (#1071) 2023-03-02 15:08:31 +01:00
internal/server internal: use go-kms-wrapping for KMS backends (#1012) 2023-02-08 12:03:54 +01:00
keyserviceproto kms: rename kms to keyservice 2023-01-16 11:56:34 +01:00
Dockerfile constants: make VersionInfo readonly (#1316) 2023-03-01 11:55:12 +01:00
README.md dev-docs: Go package docs (#958) 2023-01-19 15:57:50 +01:00

README.md

KeyService

The KeyService is one of Constellation's Kubernetes components, responsible for distributing keys and secrets to other services. This includes the JoinService, which contacts the KeyService to derive state disk keys and measurement secrets for newly-joining, and rejoining nodes, and Constellation's CSI drivers, which contact the KeyService for disk encryption keys.

The service is not exposed outside the cluster, and should be kept for internal usage only.

gRPC API

Keys can be requested through simple gRPC API based on an ID and key length.

Backends

The KeyService supports multiple backends to store keys and manage crypto operations. The default option holds a master secret in memory. Keys are derived on demand from this secret, and not stored anywhere. Other backends make use of external Key Management Systems (KMS) for key derivation and securing a master secret. When using an external KMS backend, encrypted keys are stored in cloud buckets.