machine image

Related topics

• machine image is part of Compute Engine From the official documentation: “Read and manage Compute Engine machine image resources.”
• Cloud Key Management Service secures machine image From the official documentation: “You can protect a machine image by using either [Cloud Key Management Service (Cloud KMS)](/kms/docs) or a customer-supplied encryption key (CSEK) ([Deprecated](/compute/docs/deprecations)).”
• custom images is an alternative to machine image From the official documentation: “For instances that don't support the creation of machine images, you can instead create an OS image from the boot disk of the instance, as described in [Create custom images](/compute/docs/images/create-custom).”
• customer-managed encryption keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• 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 works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• customer-managed encryption keys is part of Cloud Key Management Service From the official documentation: “The Cloud KMS keys that you create are customer-managed keys.”
• Google Cloud CLI configures Application Default Credentials From the official documentation: “To configure ADC with a user account, you use the Google Cloud CLI:”
• Application Default Credentials works with Cloud Key Management Service From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Backup and DR works with Compute Engine From the official documentation: “This page details how to use Backup and DR to back up the disks of a Compute Engine instance.”
• Compute Engine works with Google Cloud CLI From the official documentation: “Some applications might use commands from the gcloud CLI, which is included by default in most Compute Engine images.”
• Application Default Credentials works with Cloud SQL From the official documentation: “Application Default Credentials are part of the client libraries you can use to access Cloud SQL.”
• Application Default Credentials works with Google Cloud CLI From the official documentation: “To do so, provide your user credentials to ADC by using the Google Cloud CLI.”
• Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• Backup and DR works with Cloud Key Management Service From the official documentation: “Backup and DR supports customer-managed encryption keys (CMEK) that are managed in Cloud Key Management Service.”
• Cloud Key Management Service works with Cloud SQL From the official documentation: “Cloud KMS integrates with Cloud SQL.”
• Cloud Key Management Service works with Google Cloud CLI From the official documentation: “To use Cloud KMS on the command line, first [Install or upgrade to the latest version of Google Cloud CLI](/sdk/install).”
• Cloud Key Management Service works with service account From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• customer-managed encryption keys secures Compute Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
• Google Cloud CLI depends on Application Default Credentials From the official documentation: “To authenticate with the gcloud CLI, generate a local Application Default Credentials (ADC) file by running this command.”
• Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials is an alternative to Google Cloud CLI From the official documentation: “You can authenticate to [the Vision API](/vision/docs/reference/rest) by using your [gcloud CLI credentials](/sdk/docs/authenticate) or by using [Application Default Credentials](/docs/authentication/application-default-credentials).”
• Application Default Credentials depends on service account From the official documentation: “If your `BidiProcessOrder` client runs in a secure environment that can be configured with service account credentials (such as Compute Engine, Google Kubernetes Engine, or your on-premise servers), it can use [Application Default Credentials…”
• Application Default Credentials is an alternative to service account From the official documentation: “There are two ways to obtain credentials for the agent to use: - Let the agent use a service account with private-key authentication - Let the agent use application default credentials (ADC).”
• Backup and DR works with Cloud SQL From the official documentation: “Enhanced backups allow you to use Backup and DR Service with your Cloud SQL instances to manage your backups.”
• Backup and DR secures Compute Engine From the official documentation: “Backup and DR ensures that the chosen Compute Engine instances get backed up per the frequency set in the backup policy.”
• Backup and DR works with customer-managed encryption keys From the official documentation: “This guide explains how to enhance backup security by using Customer-Managed Encryption Keys (CMEK) with Backup and DR.”
• Cloud Key Management Service depends on Application Default Credentials From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Cloud Key Management Service 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 Key Management Service depends on Google Cloud CLI From the official documentation: “To use Cloud KMS on the command line, first [Install or upgrade to the latest version of Google Cloud CLI](/sdk/install).”
• Cloud SQL depends on Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
• customer-managed encryption keys secures Backup and DR From the official documentation: “With CMEK, you can protect your Backup and DR data using a cryptographic key that you control through Cloud Key Management Service.”
• customer-managed encryption keys is part of Cloud SQL From the official documentation: “Cloud SQL also lets you add another layer of encryption to data using [customer-managed encryption keys (CMEK)](/sql/docs/postgres/cmek).”
• Google Cloud CLI configures Compute Engine From the official documentation: “To replace a BYOL license with a PAYG license, use the Google Cloud CLI or the Compute Engine API.”
• service account depends on Cloud Key Management Service From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• service account secures Cloud SQL From the official documentation: “Cloud SQL uses service accounts for authentication between Cloud SQL and other Google Cloud products.”