From 9def09fdcb8bde0ac057d4208da8cea1577f428a Mon Sep 17 00:00:00 2001 From: Ludovico Magnocavallo Date: Wed, 10 Jun 2020 18:46:16 +0200 Subject: [PATCH] Update README.md --- data-solutions/cmek-via-centralized-kms/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data-solutions/cmek-via-centralized-kms/README.md b/data-solutions/cmek-via-centralized-kms/README.md index 1faaf6dd..c37f8012 100644 --- a/data-solutions/cmek-via-centralized-kms/README.md +++ b/data-solutions/cmek-via-centralized-kms/README.md @@ -2,7 +2,7 @@ This example creates a sample centralized [Cloud KMS](https://cloud.google.com/kms?hl=it) configuration, and uses it to implement CMEK for [Cloud Storage](https://cloud.google.com/storage/docs/encryption/using-customer-managed-keys) and [Compute Engine](https://cloud.google.com/compute/docs/disks/customer-managed-encryption) in a separate project. -The example is designed to match real-world use cases with a minimum amount of resources, and be used as a starting point for scenarios where application projects implement CMEK using keys managed by a central team. It also includes the IAM wiring needd to make such scenarios work. +The example is designed to match real-world use cases with a minimum amount of resources, and be used as a starting point for scenarios where application projects implement CMEK using keys managed by a central team. It also includes the IAM wiring needed to make such scenarios work. This is the high level diagram: