HumDay

Encrypts data, so that it can only be recovered by a call to Decrypt in Google Cloud Key Management (KMS)

A documented Google Cloud Key Management (KMS) operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Encrypts data, so that it can only be recovered by a call to Decrypt.

  • POSTChanges data · projectscloudkms.googleapis.com/v1/{name}:encrypt

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Google Cloud Key Management (KMS) operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Google Cloud Key Management (KMS) operations

All 29 Google Cloud Key Management (KMS) operations

Questions

Can HumDay encrypts data, so that it can only be recovered by a call to decrypt in Google Cloud Key Management (KMS)?
Yes. This operation is published in Google Cloud Key Management (KMS)'s own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Will this change my Google Cloud Key Management (KMS) data?
Yes — this is a POST operation, so it changes something in Google Cloud Key Management (KMS). HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Google Cloud Key Management (KMS) account.

Where this came from

Read from a published API description for Google Cloud Key Management (KMS) at cloudkms.googleapis.com/$discovery/rest?version=v1. The description above is the provider’s own wording, not ours. Last published 2023-04-21.