Cloud External Key Manager

Related topics

• Cloud External Key Manager works with Key Access Justifications From the official documentation: “If you [use a Cloud EKM key](/alloydb/docs/cmek#ekm), then you can use Key Access Justifications to view the reason for each Cloud EKM request.”
• Key Access Justifications is part of Cloud External Key Manager From the official documentation: “You can use Key Access Justifications as part of Cloud EKM.”
• Assured Workloads works with Cloud External Key Manager From the official documentation: “Assured Workloads supports Cloud EKM.”
• Cloud External Key Manager is part of Cloud Key Management Service From the official documentation: “In addition to these features, the Assured Workloads control package you choose will also determine which of the following Cloud KMS key types are available: - [Cloud EKM keys](/kms/docs/ekm#overview)”
• Cloud External Key Manager works with Cloud Key Management Service From the official documentation: “You can use an externally managed key with CMEK using the Cloud External Key Manager service to [make the key available](/kms/docs/ekm) through Cloud KMS.”
• Cloud External Key Manager is an alternative to Cloud Key Management Service From the official documentation: “Unless your control package mandates a certain encryption key strategy, you can use any Google key management service, including Cloud Key Management Service, Cloud External Key Manager, or CMEK.”
• Cloud External Key Manager secures Cloud SQL From the official documentation: “To protect data in Cloud SQL instances, you can use keys that you manage within a supported external key management partner. For more information, see [Cloud External Key Manager](/kms/docs/ekm), including the [Considerations](/kms/docs/ekm#considerations) section.”
• Cloud External Key Manager is an alternative to customer-managed encryption keys From the official documentation: “Unless your control package mandates a certain encryption key strategy, you can use any Google key management service, including Cloud Key Management Service, Cloud External Key Manager, or CMEK.”
• Cloud External Key Manager is an alternative to customer-supplied encryption keys From the official documentation: “Customer-supplied encryption keys (CSEK) are not recommended; scenarios that historically were addressed by CSEK are now better addressed by Cloud External Key Manager (Cloud EKM) because Cloud EKM has support for more services and higher availability.”
• Cloud External Key Manager works with Knowledge Catalog From the official documentation: “In addition, Knowledge Catalog supports Cloud External Key Manager (Cloud EKM), which lets you store your keys in an external key manager outside of Google Cloud.”
• Cloud External Key Manager works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow supports CMEK encryption using [keys stored in External Key Managers](/kms/docs/ekm).”
• Cloud External Key Manager secures Managed Service for Apache Spark From the official documentation: “[Cloud External Key Manager (Cloud EKM)](/kms/docs/ekm) lets you protect Managed Service for Apache Spark data using keys managed by a [supported external key management partner](/kms/docs/ekm#supported_partners).”
• Cloud External Key Manager works with Secret Manager From the official documentation: “In Secret Manager, you can use Cloud External Key Manager (Cloud EKM) keys to encrypt and decrypt secrets.”
• Cloud External Key Manager works with Spanner From the official documentation: “In addition, Spanner supports Cloud External Key Manager (Cloud EKM), which lets you store your keys in an external key manager outside of Google Cloud.”
• Cloud External Key Manager works with Virtual Private Cloud From the official documentation: “This page shows you how to resolve issues with Cloud External Key Manager (Cloud EKM) over virtual private cloud (VPC).”
• customer-managed encryption keys depends on Cloud External Key Manager From the official documentation: “The CMEK keys created for the EU region must be created with external protection level, requiring that you set up an EKM.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• customer-managed encryption keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Cloud Storage From the official documentation: “External BigQuery data source backed by Cloud Storage”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
• Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Knowledge Catalog depends on Application Default Credentials From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials works with Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• BigQuery works with Knowledge Catalog From the official documentation: “Some Knowledge Catalog functionalities trigger job execution using BigQuery.”
• Cloud Logging works with customer-managed encryption keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud SQL works with Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud SQL works with Compute Engine From the official documentation: “Create a Compute Engine VM Instance to host a sample web app that connects to Cloud SQL.”
• Managed Service for Apache Airflow works with Secret Manager From the official documentation: “You can [configure Secret Manager](/composer/docs/composer-3/configure-secret-manager) as your Airflow secrets backend.”
• Cloud Key Management Service works with customer-managed encryption keys From the official documentation: “With CMEK, Cloud Key Management Service wraps your stored volume keys.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• BigQuery works with Spanner From the official documentation: “Reverse ETL (BigQuery to Spanner)”
• Cloud SQL works with Knowledge Catalog From the official documentation: “You can use Knowledge Catalog to organize and enrich the metadata of Cloud SQL resources.”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• customer-managed encryption keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• BigQuery works with Managed Service for Apache Spark From the official documentation: “This means you can quickly read and write BigQuery data to and from Managed Service for Apache Spark.”
• Cloud Logging works with Cloud SQL From the official documentation: “Cloud SQL uses Cloud Logging.”
• Cloud Logging works with Managed Service for Apache Airflow From the official documentation: “You can use [Cloud Monitoring](/monitoring/docs) and [Cloud Logging](/logging/docs) with Managed Service for Apache Airflow.”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Cloud Storage works with Managed Service for Apache Airflow From the official documentation: “Managed Airflow associates a Cloud Storage bucket with your environment.”
• customer-managed encryption keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• Application Default Credentials secures Knowledge Catalog From the official documentation: “To authenticate to Knowledge Catalog, set up Application Default Credentials.”
• BigQuery works with Managed Service for Apache Airflow From the official documentation: “You can use Managed Airflow to orchestrate services in your data pipelines, such as triggering a job in BigQuery or starting a Dataflow pipeline.”
• Cloud SQL works with Secret Manager From the official documentation: “Secret Manager attempts to update the credentials in your Cloud SQL instance.”
• Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• customer-managed encryption keys is an alternative to customer-supplied encryption keys From the official documentation: “CSEK and CMEK are mutually exclusive for the target disk.”
• customer-managed encryption keys secures Secret Manager From the official documentation: “In Secret Manager, you can use a CMEK to protect data at rest.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”