Google Cloud CLI

Related topics

• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• 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.”
• 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 KMS 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).”
• Dataflow works with Google Cloud CLI From the official documentation: “Dataflow integrates with the Google Cloud CLI.”
• GKE works with Google Cloud CLI From the official documentation: “GKE manages end-user authentication for you through the Google Cloud CLI.”
• Google Cloud CLI works with Spanner From the official documentation: “You have already set up [gcloud CLI](/sdk/docs) for use with Spanner.”
• Bigtable works with Google Cloud CLI From the official documentation: “When you use the [gcloud CLI](/sdk/gcloud/reference/bigtable) to access Bigtable, you authenticate to Google Cloud as a principal, which provides the credentials used by the gcloud CLI commands.”
• bq command-line tool is an alternative to Google Cloud CLI From the official documentation: “You can also submit a batch translation job by using a translation configuration file with the Google Cloud CLI (`gcloud bq migration-workflows`) or with the bq command-line tool command-line tool.”
• Cloud Composer works with Google Cloud CLI From the official documentation: “Your Google Account must have [permissions](/composer/docs/composer-1/access-control#cli) to use Google Cloud CLI with Managed Airflow and run Airflow CLI commands.”
• 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 KMS 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 Logging is an alternative to Google Cloud CLI From the official documentation: “This section shows you how to verify the encryption key that was used during cluster creation. You can perform this verification using Cloud Logging or by using the Google Cloud CLI.”
• Google Cloud CLI configures Cloud Logging From the official documentation: “You can update your cluster's [Cloud Logging](/kubernetes-engine/multi-cloud/docs/aws/how-to/cloud-logging) configuration settings with the Google Cloud CLI.”
• 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.”
• Google Cloud CLI works with Managed Service for Apache Spark From the official documentation: “When you use the [gcloud CLI](/sdk/gcloud/reference/dataproc) to access Managed Service for Apache Spark, you authenticate to Google Cloud as a principal, which provides the credentials used by the gcloud CLI commands.”
• Google Cloud CLI configures Managed Service for Apache Spark From the official documentation: “You can specify one or more labels to be applied to a Managed Service for Apache Spark cluster or job at creation or submit time using the Google Cloud CLI.”
• 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 Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• customer-managed encryption keys depends on Cloud Key Management Service From the official documentation: “These keys are created and managed using Cloud KMS.”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• 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.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• 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 Cloud Monitoring From the official documentation: “You can use Monitoring to export your metrics to BigQuery.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• Dataflow works with Spanner From the official documentation: “Use Dataflow to load data into Spanner.”
• VPC Service Controls secures BigQuery From the official documentation: “BigQuery data is protected with VPC Service Controls”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• customer-managed encryption keys secures Cloud SQL From the official documentation: “Enable CMEK for Cloud SQL Databases”
• BigQuery works with Bigtable From the official documentation: “BigQuery lets you query your Bigtable data from BigQuery.”
• BigQuery works with Spanner From the official documentation: “Federated analytics seamlessly combine data from Spanner and other sources in BigQuery.”
• Cloud SQL works with Compute Engine From the official documentation: “Cloud SQL uses Compute Engine virtual machines (VMs) with persistent storage disks.”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• customer-managed encryption keys depends on Cloud KMS From the official documentation: “You must have a symmetric encryption key in Cloud KMS to use for CMEK.”
• Cloud KMS works with customer-managed encryption keys From the official documentation: “With customer-managed encryption keys (CMEK), volume keys are wrapped using your keys stored in Cloud KMS.”
• Cloud SQL works with GKE From the official documentation: “The app uses Cloud SQL, Vertex AI, and either Google Kubernetes Engine (GKE) or Cloud Run.”
• Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• 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.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Cloud SQL From the official documentation: “Database Migration Service and Cloud SQL use Cloud Logging.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• Cloud Storage works with Managed Service for Apache Spark From the official documentation: “Managed Service for Apache Spark accesses these files on Cloud Storage.”
• 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.”
• BigQuery works with Cloud Key Management Service From the official documentation: “A Cloud KMS key is considered available and accessible by BigQuery under the following conditions:”
• Bigtable works with Dataflow From the official documentation: “The Dataflow job then writes the transformed data to your Bigtable table.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Cloud Monitoring works with Spanner From the official documentation: “Monitor Spanner metrics using Cloud Monitoring.”
• Compute Engine works with Managed Service for Apache Spark From the official documentation: “Google Compute Engine provides a runtime environment for all features provided by Managed Service for Apache Spark and Gemini Enterprise Agent Platform.”
• customer-managed encryption keys secures Bigtable From the official documentation: “In a CMEK-protected instance, Bigtable uses your CMEK key to protect your data at rest.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Spanner From the official documentation: “Identity and Access Management (IAM) lets you control user and group access to Spanner resources at the project, Spanner instance, and Spanner database levels.”
• Managed Service for Apache Spark depends on Cloud Storage From the official documentation: “Managed Service for Apache Spark uses Cloud Storage as its default distributed file system.”
• VPC Service Controls secures Cloud Storage From the official documentation: “Storage Transfer Service supports transfers to Cloud Storage buckets protected by VPC Service Controls.”
• BigQuery works with Cloud KMS From the official documentation: “BigQuery stores the name of the key used to encrypt the table content and uses that key when a table protected by Cloud KMS is queried.”