This topic provides a list of Google Cloud services that offer integrations with Cloud KMS. These services generally fall under one of the following categories:
A Customer-managed encryption key (CMEK) integration allows you to encrypt that service's data at rest using a Cloud KMS key that you own and manage. Data protected with a CMEK key cannot be decrypted without access to that key.
A CMEK-compliant service either does not store data, or only stores data for a short period of time, such as during batch processing. Such data is encrypted using an ephemeral key that only exists in memory and is never written to disk. When the data is no longer needed, the ephemeral key is flushed from memory, and the data can't ever be accessed again. The output of a CMEK-compliant service might be stored in a service that is integrated with CMEK, such as Cloud Storage.
Your applications can use Cloud KMS in other ways. For example, you can directly encrypt application data before transmitting or storing it.
To learn more about how data in Google Cloud is protected at rest and how customer-managed encryption keys (CMEK) work, see Customer-managed encryption keys (CMEK).
The following table lists services that integrate with Cloud KMS for software and hardware (HSM) keys. For products that integrate with Cloud KMS when using external Cloud EKM keys, see Services that support CMEK with Cloud EKM.
The following table lists services that do not use customer-managed encryption keys (CMEKs) because they do not store data long term. For more information on why these services are considered CMEK compliant, see CMEK compliance.
|Cloud Build||CMEK compliance in Cloud Build|
|Container Registry||Using a storage bucket protected with CMEK|
|Cloud Vision||CMEK compliance in Vision API|
Other integrations with Cloud KMS
These topics discuss other ways to use Cloud KMS with other Google Cloud services.
|Any service||Encrypt application data before transmitting or storing it|
|Cloud Build||Encrypt resources before adding them to a build|