service account key

Related topics

• service account key is an alternative to Workload Identity Federation From the official documentation: “For hosts outside of Google Cloud, you can provide a service account key or configure Workload Identity Federation (WIF).”
• service account key is an alternative to Workload Identity Federation for GKE From the official documentation: “Enabling it lets you use IAM policies to grant Kubernetes workloads in your GKE cluster access to specific Google Cloud APIs without needing manual configuration or less secure methods like service account key files.”
• service account key is part of service account From the official documentation: “A service account can have up to 10 keys.”
• service account impersonation is an alternative to service account key From the official documentation: “If you cannot use a user account or service account impersonation for local development, you can use a service account key.”
• credential configuration file is an alternative to service account key From the official documentation: “This approach uses the credential configuration files in place of the Google service account key files.”
• key rotation secures service account key From the official documentation: “Rotating service account keys can help reduce the risk posed by leaked or stolen keys.”
• service account key secures Pub/Sub From the official documentation: “The Pub/Sub connection is authenticated using a service account key.”
• service account key is part of service accounts From the official documentation: “Managing service identities involves both the service identity (represented by a `ProjectServiceAccount` resource) and its associated credentials (public and private key pairs).”
• service account key is an alternative to short-lived credentials From the official documentation: “Short-lived service account credentials are useful for scenarios where you need to grant limited access to resources for trusted service accounts, and they reduce the risk compared to using long-lived credentials like service account keys.”
• 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 Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Cloud Run depends on service account From the official documentation: “The Cloud Run function needs a service account with permissions to write to GCS bucket and be invoked by Pub/Sub.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, 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.”
• Cloud Run works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to Cloud Run”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• Workload Identity Federation for GKE is part of GKE From the official documentation: “Enable Workload Identity Federation for GKE:”
• Cloud Run depends on Pub/Sub From the official documentation: “Create a Pub/Sub topic that Cloud Scheduler will publish to and the Cloud Run function will subscribe to.”
• 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)”
• service account keys is an alternative to Workload Identity Federation From the official documentation: “Where possible, consider using Workload Identity Federation instead of service account keys.”
• Cloud Run depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Cloud Run is an alternative to 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 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).”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Identity and Access Management works with Workload Identity Federation for GKE From the official documentation: “Instead, your GKE cluster directly authenticates workloads using Google Cloud IAM.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, 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).”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• GKE works with Pub/Sub From the official documentation: “Route Cloud Pub/Sub events to GKE”
• Application Default Credentials works with GKE From the official documentation: “To authenticate to GKE, set up Application Default Credentials.”
• Application Default Credentials works with service account impersonation From the official documentation: “You can use service account impersonation to set up a local Application Default Credentials (ADC) file.”
• Application Default Credentials works with Workload Identity Federation From the official documentation: “ADC also supports [Workload Identity Federation](#workload-identity-federation), enabling applications to access Google Cloud resources from external platforms like Amazon Web Services (AWS), Microsoft Azure, or any identity provider that supports OpenID Connect (OIDC).”
• 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 Run works with Identity and Access Management From the official documentation: “Cloud Run also offers the ability to control access to a service with Identity and Access Management (IAM).”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• service account impersonation configures Application Default Credentials From the official documentation: “You can use service account impersonation to set up a local ADC file.”
• service account keys is part of service account From the official documentation: “You use the Identity and Access Management API to create a new key pair for a service account.”
• 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 configures Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• 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 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).”
• Application Default Credentials is an alternative to service account keys From the official documentation: “When developers are locally iterating on Terraform configuration, they should authenticate by running [`gcloud auth application-default login`](https://cloud.google.com/sdk/gcloud/reference/auth/application-default/login) to generate application default credentials. Don't…”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• 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: “Route Cloud Storage events to GKE”
• Cloud Storage works with Workload Identity Federation for GKE From the official documentation: “For example, consider a Kubernetes workload that uses Workload Identity Federation for GKE to store data in a Cloud Storage bucket.”
• credential configuration file configures service account impersonation From the official documentation: “Use a [credential configuration file](https://google.aip.dev/auth/4117) to configure an external application to impersonate a service account.”
• credential configuration file depends on Workload Identity Federation From the official documentation: “Use a [credential configuration file](https://google.aip.dev/auth/4117) to configure an external application to impersonate a service account. This option is only available for applications that use [Workload Identity Federation](/iam/docs/workload-identity-federation).”
• 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.”
• GKE depends on Workload Identity Federation for GKE From the official documentation: “Your GKE cluster can access the Spanner API through [Workload Identity Federation for GKE](/kubernetes-engine/docs/concepts/workload-identity).”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”