Create a GCP KMS provider with the given options.
List all keys, optionally filtered by usage or enabled state.
Optionalfilters: { usage?: string; enabled?: boolean }Retrieve metadata for a specific key by ID.
Create a new key with the given algorithm and usage.
Optionalmetadata: Record<string, string>Enable every disabled version of a key.
Disable every enabled version of a key.
Schedule every version that is not already scheduled or destroyed
for destruction. Cloud KMS applies the key's own
destroyScheduledDuration, set when the key is created, so
pendingWindowDays is not used.
Optional_pendingWindowDays: numberEncrypt plaintext using a managed key.
Optionalcontext: Record<string, string>Decrypt ciphertext using a managed key.
Optionalcontext: Record<string, string>Sign data with the newest enabled version of a signing key. Digest algorithms receive the message's digest, Ed25519 the message itself. The result reports the version's actual algorithm.
Optional_algorithm: stringVerify a signature locally against the public key of every enabled version, so signatures made before a rotation still verify until their version is disabled or destroyed. Cloud KMS has no remote verify for asymmetric keys. A mismatch returns false; transport and lookup errors are thrown.
Optional_algorithm: stringWrap an existing key with the managed key.
Optionalcontext: Record<string, string>Unwrap a wrapped key with the managed key.
Optionalcontext: Record<string, string>
Google Cloud KMS adapter.
Uses the Google Cloud KMS REST API v1 via native
fetchwith zero SDK dependencies.Example