Google Cloud APIs

Related topics

• Cloud Client Libraries works with Google Cloud APIs From the official documentation: “Client libraries make it easier to access Google Cloud APIs from a supported language.”
• Cloud Service Mesh works with Google Cloud APIs From the official documentation: “**Note:** This guide only supports Cloud Service Mesh with Google Cloud APIs and does not support Istio APIs.”
• Application Default Credentials secures Google Cloud APIs From the official documentation: “To authenticate calls to Google Cloud APIs, client libraries support [Application Default Credentials (ADC)](/docs/authentication/application-default-credentials); the libraries look for credentials in a set of defined locations and use those credentials to authenticate…”
• Chrome Enterprise Premium secures Google Cloud APIs From the official documentation: “securing the Google Cloud console and the Google Cloud APIs with Chrome Enterprise Premium.”
• client libraries works with Google Cloud APIs From the official documentation: “Client libraries make it easier to access Google Cloud APIs from a supported language.”
• Cloud Client Libraries is part of Google Cloud APIs From the official documentation: “If your Cloud Run job interfaces with Google Cloud APIs, such as Cloud Client Libraries, see the [service identity configuration guide](/run/docs/configuring/jobs/service-identity).”
• Context-Aware Access secures Google Cloud APIs From the official documentation: “This guide describes how you can set up Context-Aware Access to help secure service account access to Google Cloud APIs, based on access levels that you define.”
• Google Cloud APIs works with Google Cloud CLI From the official documentation: “The `gcloud` CLI manages authentication, local configuration, developer workflow, and interactions with the Google Cloud APIs.”
• Google Cloud APIs depends on Transport Layer Security From the official documentation: “The Google Cloud APIs use the TLS protocol to verify the identity of a device by decrypting the message encrypted by the private key using the public key of the certificate during the mTLS handshake.”
• Workload Identity Federation for GKE secures Google Cloud APIs From the official documentation: “Agent Substrate on GKE uses Workload Identity Federation for GKE to authenticate to Google Cloud APIs, such as Cloud Storage for saving agent snapshots.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Client Libraries From the official documentation: “The authentication libraries make those credentials available to [Cloud Client Libraries and Google API Client Libraries](/apis/docs/client-libraries-explained).”
• 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.”
• Cloud Service Mesh works with GKE From the official documentation: “# Set up a proxyless gRPC service mesh on GKE”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• Application Default Credentials works with Spanner From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud Service Mesh depends on GKE From the official documentation: “Provision managed Cloud Service Mesh on a GKE cluster.”
• Google Cloud CLI configures Application Default Credentials From the official documentation: “To configure ADC with a user account, you use the Google Cloud CLI:”
• Spanner depends on Application Default Credentials From the official documentation: “To authenticate to Spanner, set up Application Default Credentials.”
• Cloud Client Libraries depends on Application Default Credentials From the official documentation: “When you use client libraries, you use Application Default Credentials to authenticate.”
• Cloud Service Mesh works with Identity-Aware Proxy From the official documentation: “Integrate Identity-Aware Proxy with Cloud Service Mesh”
• GKE works with Identity-Aware Proxy From the official documentation: “If you are running GKE version 1.24 or later, you can configure IAP and GKE by using the Kubernetes Gateway API.”
• GKE works with Workload Identity Federation for GKE From the official documentation: “Workload Identity Federation for GKE (for workloads running on Google Kubernetes Engine only)”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• GKE works with Workload Identity Federation From the official documentation: “To allow GitHub Actions authenticate Google Cloud and deploy to GKE, use [workload identity federation](/iam/docs/workload-identity-federation).”
• Workload Identity Federation for GKE is part of GKE From the official documentation: “Enable Workload Identity Federation for GKE:”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• 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.”
• Cloud Service Mesh works with Workload Identity Federation for GKE From the official documentation: “When Envoy (`envoy-proxy`) connects to Cloud Service Mesh to fetch the xDS configuration, it uses Workload Identity Federation for GKE and the Compute Engine VM default service account (unless the bootstrap was changed).”
• gcloud CLI configures Application Default Credentials From the official documentation: “**gcloud CLI**: Manage cloud resources, configure projects, and set up local Application Default Credentials (ADC).”
• gcloud CLI works with Workload Identity Federation From the official documentation: “Support for Workload Identity Federation in gcloud CLI is available in [version 363.0.0 and later versions of the gcloud CLI](/sdk/docs/components#updating_components).”
• 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 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.”
• Google Cloud CLI works with Spanner From the official documentation: “You have already set up [gcloud CLI](/sdk/docs) for use with Spanner.”
• Workload Identity Federation for GKE secures Cloud Storage From the official documentation: “This command is required to grant the GKE service account permission to access the Cloud Storage bucket using Workload Identity Federation for GKE.”
• Workload Identity Federation for GKE depends on GKE From the official documentation: “Workload Identity Federation for GKE provides a highly secure and automated authentication mechanism, simplifying key management. This method is specific to GKE clusters.”
• Application Default Credentials is part of client libraries 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 client libraries From the official documentation: “Client libraries can use [Application Default Credentials](/docs/authentication/application-default-credentials) to easily authenticate with Google APIs and send requests to those APIs.”
• Application Default Credentials configures client libraries From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• Application Default Credentials works with GKE From the official documentation: “To authenticate to GKE, 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 works with Workload Identity Federation From the official documentation: “The preferred method to set up authentication from outside of Google Cloud is to use workload identity federation. For more information, see [Set up ADC for on-premises or another cloud provider](/docs/authentication/set-up-adc-on-premises) in the authentication documentation.”
• Chrome Enterprise Premium depends on Identity-Aware Proxy From the official documentation: “IAP is the base of Chrome Enterprise Premium, letting you grant access to your HTTPS apps and resources.”
• client libraries works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• client libraries is an alternative to gcloud CLI From the official documentation: “The Google Cloud console cannot be used to change encryption keys on a per-object basis. Use the gcloud CLI or the client libraries instead.”
• client libraries is part of Spanner From the official documentation: “Spanner provides a set of [Client libraries](/spanner/docs/reference/libraries) for various languages, and the ability to read and write data using Spanner-specific API calls, as well as by using [SQL queries](/spanner/docs/query-syntax) and [Data Modification Language…”
• Cloud Client Libraries works with Cloud Storage From the official documentation: “Store and retrieve data in Cloud Storage using Cloud Client Libraries in the standard environment.”
• Cloud Client Libraries is an alternative to gcloud CLI From the official documentation: “You can use the [APIs Explorer](/managed-spark/docs/quickstarts/create-cluster-template), the [Google Cloud console](/managed-spark/docs/quickstarts/update-cluster-console#create_a_cluster), the gcloud CLI…”
• Cloud Client Libraries works with Workload Identity Federation From the official documentation: “Use a client library or tool that supports Workload Identity Federation and can [find credentials automatically](/docs/authentication/client-libraries):”
• Cloud Service Mesh depends on Workload Identity Federation From the official documentation: “This error is shown if the GKE cluster does not have [Workload Identity Federation](/kubernetes-engine/docs/how-to/workload-identity) enabled on all node pools of that cluster, since this is a prerequisites for the installation of Cloud Service Mesh.”
• Cloud Service Mesh depends on Workload Identity Federation for GKE From the official documentation: “Cloud Service Mesh requires Workload Identity Federation for GKE and is the recommended way to access Google APIs from GKE workloads.”
• Cloud Storage works with GKE From the official documentation: “This example configures GKE to store Pod snapshots in the `FOLDER_PATH/` path inside the Cloud Storage bucket `BUCKET_NAME`:”
• Cloud Storage works with Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
• Context-Aware Access is part of Chrome Enterprise Premium From the official documentation: “Defend against real-time phishing and malware, prevent data exfiltration with granular Data Loss Prevention (DLP) policies, and enforce Context-Aware Access to any app (SaaS, cloud, or on-prem) from any device, directly in Chrome.”
• Context-Aware Access depends on Identity-Aware Proxy From the official documentation: “**Caution:** To enable context-aware access control for workstations, you must first enable [IAP](/workstations/docs/enable-iap) on your workstation cluster.”
• Context-Aware Access works with Identity-Aware Proxy From the official documentation: “To help secure agents accessing the Agent Gateway, Context-Aware Access and IAP enforce that agents use [mTLS](#mtls) by verifying certificate-based token binding.”
• gcloud CLI is part of Google Cloud CLI From the official documentation: “If you plan to send Cloud Translation requests through the command line (such as through curl commands), install and initialize the [gcloud CLI](/sdk/gcloud) , which is included in the Google Cloud CLI.”
• gcloud CLI works with Google Cloud CLI From the official documentation: “To use the gcloud CLI, you can [install and initialize](/sdk/docs/install-sdk) the Google Cloud CLI, or you can use [Cloud Shell](/shell/docs/using-cloud-shell).”
• gcloud CLI configures Identity-Aware Proxy From the official documentation: “After you enable IAP, you can use the gcloud CLI to modify the IAP access policy using the IAM role `roles/iap.httpsResourceAccessor`.”