API keys

Related topics

• API keys is an alternative to service accounts From the official documentation: “You might also be able to use API keys in some situations, but service accounts are generally recommended.”
• API keys is an alternative to Workload Identity Federation From the official documentation: “Use [API keys](/docs/authentication/api-keys) or [Workload Identity Federation](/docs/authentication/set-up-adc-on-premises).”
• API keys works with Cloud Audit Logs From the official documentation: “Cloud Audit Logs for API keys let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• API keys works with Cloud Endpoints From the official documentation: “Cloud Endpoints handles both API keys and authentication schemes, such as Firebase or Auth0.”
• API keys depends on Secrets From the official documentation: “API keys use secrets, which contain one or more secret versions, along with metadata such as labels and replication information.”
• Application restrictions secures API keys From the official documentation: “Application restrictions specify which websites, IP addresses, or apps can use your API key.”
• Identity and Access Management secures API keys From the official documentation: “API Keys uses [Identity and Access Management](/iam) to manage access to the keys.”
• Cloud Audit Logs works with Cloud Key Management Service From the official documentation: “Cloud Audit Logs for Cloud KMS in the Activity stream read like generic logs, and are not easily read by a human.”
• Cloud Audit Logs works with Cloud Storage From the official documentation: “This page provides supplemental information for using [Cloud Audit Logs](/logging/docs/audit) with Cloud Storage.”
• Cloud Endpoints works with GKE From the official documentation: “In addition, Endpoints only supports gRPC services for GKE, Compute Engine, and Cloud Run (Beta).”
• Cloud Endpoints depends on Service Management API From the official documentation: “Cloud Endpoints uses Service Management to manage your API.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run is an alternative to GKE From the official documentation: “For your containerized websites, you can also deploy them to [Cloud Run](/run) in addition to [using GKE](#kubernetes-engine).”
• Cloud Run works with Google Kubernetes Engine From the official documentation: “Connecting Cloud Run services to Cloud Service Mesh lets you securely route traffic to workloads on GKE.”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• 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).”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Cloud Endpoints works with Cloud Run From the official documentation: “In addition, Endpoints only supports gRPC services for GKE, Compute Engine, and Cloud Run (Beta).”
• Cloud Endpoints depends on Identity and Access Management From the official documentation: “Endpoints uses [Identity and Access Management (IAM)](/iam/docs) to control access to your API.”
• Cloud Run works with GKE From the official documentation: “Leverage Google Kubernetes Engine (GKE) and Cloud Run to deploy applications to the Google Cloud, optimizing costs, performance, and management overhead.”
• Cloud Audit Logs works with Cloud Run From the official documentation: “The sample code shows you how to read Cloud Storage events using Cloud Audit Logs in a service deployed to Cloud Run.”
• Cloud Audit Logs works with Google Kubernetes Engine From the official documentation: “For clusters on patch versions 1.21.9 and 1.22.3 or later with Cloud Logging [enabled](/stackdriver/docs/solutions/gke/installing#installing), GKE provides a [Cloud Audit Logs log](/kubernetes-engine/docs/how-to/audit-logging#viewing_your_projects_admin_activity_log) to…”
• Cloud Audit Logs works with Service Management API From the official documentation: “Cloud Audit Logs for Service Management let you track administrative and data-access operations on your resources to help you monitor access and configuration changes.”
• Cloud Endpoints works with Google Kubernetes Engine From the official documentation: “Getting started with Endpoints on GKE”
• Cloud Endpoints works with Service Management API From the official documentation: “To deploy the Endpoints configuration, you use the [gcloud endpoints services deploy](/sdk/gcloud/reference/endpoints/services/deploy) command. This command uses [Service Management](/service-infrastructure/docs/manage-config) to create a managed service.”
• Cloud Key Management Service depends on Identity and Access Management From the official documentation: “Whatever the mechanism, Cloud KMS resolves the provided credential to identify the principal (the entity which is authenticated and is authorizing the request), and calls IAM to see whether the principal is authorized to make the request and whether an audit log is written.”
• Cloud Key Management Service works with Identity and Access Management From the official documentation: “The Cloud KMS platform is integrated with [IAM](/iam/docs/overview) and [Cloud Audit Logs](/logging/docs/audit) so that you can manage permissions on individual keys and audit how they are used.”
• Cloud Key Management Service secures Secrets From the official documentation: “On GKE these Secrets are encrypted at rest and can optionally be encrypted using KMS.”
• Cloud Run is an alternative to Google Kubernetes Engine From the official documentation: “**Agent and tool runtimes**: hosting and executing agents or MCP servers on runtimes such as Agent Runtime on Gemini Enterprise Agent Platform, Cloud Run, or Google Kubernetes Engine (GKE) incurs standard compute and runtime charges for those services.”
• Cloud Run works with Workload Identity Federation From the official documentation: “This tutorial describes how to use Workload Identity Federation to authenticate workloads that run outside of Google Cloud so that they can access microservices hosted by Cloud Run.”
• 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 Google Kubernetes Engine From the official documentation: “Often, media-related data residing in Cloud Storage is processed by applications running in Compute Engine or Google Kubernetes Engine, and the output of this process is written back to Cloud Storage.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• GKE depends on Identity and Access Management From the official documentation: “GKE relies on and can be used with many other Google Cloud services, from IAM for access control to Cloud Billing for managing your costs.”
• Google Kubernetes Engine works with Identity and Access Management From the official documentation: “In GKE, you can also use IAM to manage which users and service accounts can access, and perform operations in, your clusters.”
• Identity and Access Management secures Cloud Audit Logs From the official documentation: “IAM permissions and roles determine your ability to access audit logs data in the [Logging API](/logging/docs/reference/v2/rest), the [Logs Explorer](/logging/docs/view/logs-explorer-interface), and the [Google Cloud CLI](/logging/docs/reference/tools/gcloud-logging).”
• Identity and Access Management secures Cloud Key Management Service From the official documentation: “If you need to prevent a user from using a Cloud KMS resource during the time needed for propagation of an eventually consistent operation, remove the Identity and Access Management (IAM) permission for the resource.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management configures GKE From the official documentation: “First, as you would with most services on Google Cloud, you need to configure [IAM](/iam) roles in order to set up authorization on GKE.”
• Identity and Access Management configures service accounts From the official documentation: “To manage this access, you grant specific Identity and Access Management (IAM) roles to the service accounts that receive events and invoke your target workloads.”
• Identity and Access Management works with Service Management API From the official documentation: “Understand and use Identity and Access Management with the Service Management API.”
• Secrets is part of Google Kubernetes Engine From the official documentation: “If the same metadata injection method is not available, GKE offers [ConfigMaps](/kubernetes-engine/docs/concepts/configmap) and [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/).”
• service accounts is part of Identity and Access Management From the official documentation: “The Organization Policy Service provides constraints that can be used in [organization policies](/organization-policy/overview) to limit the usage of Identity and Access Management (IAM) [service accounts](/iam/docs/service-accounts).”
• Service Management API is part of Cloud Endpoints From the official documentation: “The components that make up Endpoints are: - Extensible Service Proxy (ESP) or Extensible Service Proxy V2 (ESPv2) - for injecting Endpoints functionality. - Service Control - for applying API management rules. - Service Management - for configuring API management rules.”
• Service Management API depends on Identity and Access Management From the official documentation: “The Service Management API uses [Identity and Access Management](/iam) (Cloud IAM) to control access to managed services and their child resources.”
• Workload Identity Federation secures Cloud Storage From the official documentation: “To allow GKE to securely access the Cloud Storage bucket, set up GKE Workload Identity Federation:”
• Workload Identity Federation is part of Identity and Access Management From the official documentation: “[Identity and Access Management (IAM)](/iam/docs/overview) lets you manage fine-grained access to services and resources in Google Cloud. IAM includes features such as the following: - [Privileged Access Manager](/iam/docs/pam-overview), which manages on-demand, temporary…”