Proposal: optional external cryptographic backend for KMS #7495
Replies: 1 comment
|
Thanks @lecodev-26 for writing this up so carefully before starting, and for putting failure behaviour and no silent fallback up front. I'd rather not add a Floci specific backend interface or setting for this. AWS already has a mechanism for exactly this split: an external key store, where KMS keeps the key metadata and policies and sends Floci does not support custom key stores yet: |
Uh oh!
There was an error while loading. Please reload this page.
Hi Floci maintainers,
I'd like to explore whether Floci could support an optional external cryptographic backend for selected KMS operations, while preserving its existing KMS implementation as the default.
I'm developing NEXUS-Q (https://github.com/lecodev-26/nexusq-keyprovider), an independent cryptographic service, and I'm evaluating a community integration with Floci. Before implementing anything, I'd like to validate the architectural direction with you.
Motivation
Floci already provides KMS and Secrets Manager functionality, including authenticated encryption and key-management operations.
An optional external backend could allow users to delegate selected cryptographic operations to an independently managed service, without changing Floci's AWS-compatible API surface.
NEXUS-Q would be one possible implementation, but the extension should remain provider-neutral.
Proposed architecture
Introduce a narrow internal abstraction around the cryptographic operations that Floci needs from its KMS implementation.
Conceptually:
NEXUS-Q could then be implemented as a separate integration, without making it a mandatory Floci dependency.
Initial scope
I suggest starting with a deliberately limited scope:
EncryptandDecryptcan be delegated safely.Operations such as
GenerateDataKey, asymmetric cryptography, grants, rotation and imported key material should only be included after their contracts and security implications have been reviewed.Security considerations
The integration should explicitly address:
The integration would not claim to be production-audited or officially supported without the appropriate review.
Questions for maintainers
Before preparing an implementation, I'd appreciate your guidance:
I'm happy to keep the initial contribution narrow and follow Floci's existing architecture and testing conventions.
Thanks for your time!
All reactions