Google-owned and Google-managed encryption key

Related topics

• customer-managed encryption key is an alternative to Google-owned and Google-managed encryption key From the official documentation: “Optional. To use a customer-managed encryption key (CMEK) to encrypt messages, select **Cloud KMS key**. By default, Pub/Sub uses Google default encryption, which doesn't require a CMEK.”
• CMEK is an alternative to Google-owned and Google-managed encryption key From the official documentation: “You can choose whether to use a Google-owned and Google-managed encryption key (GMEK) or Customer-managed encryption key (CMEK) approach to encrypt and decrypt your API data at rest.”
• Dataflow works with Pub/Sub From the official documentation: “Pub/Sub notifies Dataflow about the upload.”
• CMEK secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• CMEK secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• customer-managed encryption key is part of Cloud Key Management Service From the official documentation: “[Create a customer-managed encryption key (CMEK)](/kms/docs/creating-keys) in Cloud Key Management Service.”
• customer-managed encryption key depends on Cloud Key Management Service From the official documentation: “The Cloud Key Management Service key for encrypting your log data”
• Cloud HSM is part of Cloud Key Management Service From the official documentation: “You can import into Multi-tenant Cloud HSM keys, Single-tenant Cloud HSM keys, or software keys in Cloud KMS.”
• Cloud HSM works with customer-managed encryption key From the official documentation: “Cloud HSM provides a layer of abstraction on top of the HSM modules. This abstraction lets you use your keys in CMEK integrations or the Cloud KMS APIs or client libraries without HSM-specific code.”
• Cloud Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• Cloud Key Management Service works with CMEK From the official documentation: “With CMEK, you can use your cryptographic keys, managed within Cloud Key Management Service (Cloud KMS), to protect your RAG corpus data.”
• Cloud KMS works with Pub/Sub From the official documentation: “This page shows you how to use [Pub/Sub](/pubsub) to create notifications on state changes for Cloud KMS resources.”
• Cloud SQL depends on Cloud KMS From the official documentation: “Cloud SQL administrator operations, such as create, clone, or update, might fail due to Cloud KMS errors, and missing roles or permissions.”
• CMEK works with Dataflow From the official documentation: “The region for your CMEK and the [region](/dataflow/docs/resources/locations) for your Dataflow job must be the same.”
• Cloud HSM depends on Cloud Key Management Service From the official documentation: “Because Cloud HSM uses Cloud KMS as its front end, you can leverage all the conveniences and features that Cloud KMS provides.”
• Cloud HSM works with Cloud Key Management Service From the official documentation: “Creates a new key in Cloud KMS backed by Cloud HSM.”
• Cloud HSM works with Cloud KMS From the official documentation: “Creates a new key in Cloud KMS backed by Cloud HSM.”
• Cloud HSM works with CMEK From the official documentation: “How Cloud HSM handles request flows for creating keys, cryptographic operations, and CMEK integrations.”
• Cloud Key Management Service works with customer-managed encryption key From the official documentation: “Several Google Cloud products are integrated with Cloud KMS to support Customer-Managed Encryption Key (CMEK) functionality.”
• Cloud KMS works with CMEK From the official documentation: “To put project IDs in an ALLOW list to ensure that only keys from an instance of Cloud KMS within that project are used for CMEK.”
• Cloud KMS works with Dataflow From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Dataflow.”
• Cloud SQL works with Dataflow From the official documentation: “Use Datastream to replicate changes from your MySQL instance to either BigQuery or Cloud Storage, and then use Dataflow or Managed Service for Apache Spark to bring the data into your Cloud SQL instance.”
• CMEK depends on Cloud Key Management Service From the official documentation: “Modify the CMEK configuration on a parameter by updating the parameter to use the new Cloud KMS key resource names.”
• CMEK works with Pub/Sub From the official documentation: “By using Pub/Sub with CMEK, you are able to meet locality rules about encryption while still maintaining high availability.”
• customer-managed encryption key depends on Cloud KMS From the official documentation: “To encrypt restored disks with a Customer-Managed Encryption Key (CMEK), make sure that the Compute Engine service agent (`service-PROJECT_NUMBER@compute-system.iam.gserviceaccount.com`) has the [Cloud KMS CryptoKey Encrypter/Decrypter…”
• customer-managed encryption key secures Cloud SQL From the official documentation: “To use a configured customer-managed encryption key (CMEK) to secure access to Cloud SQL, enter the **Resource Name of the Encryption key** in the text field.”
• customer-managed encryption key secures Dataflow From the official documentation: “(Optional) To [encrypt the Dataflow pipeline state](/dataflow/docs/guides/customer-managed-encryption-keys) with a customer-managed encryption key, click **Show encryption options** and select **Use a customer-managed encryption key (CMEK)**.”
• customer-managed encryption key secures Pub/Sub From the official documentation: “Your topic is configured to use a [customer-managed encryption key](/pubsub/docs/encryption) from Cloud Key Management Service (Cloud KMS), and Pub/Sub can't encrypt the published message:”