OAuth 2.0

Related topics

• OpenID Connect depends on OAuth 2.0 From the official documentation: “OpenID Connect is an identity layer on top of the OAuth 2.0 protocol.”
• Apigee works with OAuth 2.0 From the official documentation: “Learn about the main advantages of using OAuth 2.0 with Apigee, including speed, scale, visibility, and so on.”
• Cloud Storage works with OAuth 2.0 From the official documentation: “After you fully migrate, you can use all the features of Cloud Storage, including multiple projects and OAuth 2.0 for authentication.”
• OAuth 2.0 is an alternative to service account From the official documentation: “If you are using the service account authentication instead of OAuth 2.0 authentication, ensure that appropriate permissions are given to the service account.”
• Organization Policy Service depends on OAuth 2.0 From the official documentation: “Organization Policy Service uses [OAuth 2.0](http://tools.ietf.org/html/rfc6749) for API authentication and authorization.”
• 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: “External BigQuery data source backed by Cloud Storage”
• Cloud Storage works with Google SecOps From the official documentation: “Configure a feed in Google SecOps to ingest from Google Cloud Storage”
• 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.”
• Cloud Run works with Cloud Storage From the official documentation: “Route Cloud Storage events to Cloud Run”
• 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 Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Cloud Build works with Cloud Run From the official documentation: “Cloud Build - create container images and deploy to Cloud Run.”
• Cloud Build works with Cloud Storage From the official documentation: “Cloud Build then stores Terraform files and the Terraform State File in a Cloud Storage bucket.”
• 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.”
• Cloud Storage works with customer-managed encryption keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• service account is part of Google SecOps From the official documentation: “Each Google SecOps instance has a unique service account.”
• Apigee works with customer-managed encryption keys From the official documentation: “This page describes using CMEK with Apigee.”
• BigQuery works with Google SecOps From the official documentation: “Google SecOps exports the following categories of data to your BigQuery project:”
• Cloud Storage works with Compute Engine From the official documentation: “You can use a web browser, the Google Cloud CLI, or a programming language to transfer files between Cloud Storage and Compute Engine VMs.”
• Organization Policy Service configures service account From the official documentation: “To limit who can create service accounts, use the [Organization Policy Service](/resource-manager/docs/organization-policy/overview).”
• Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• customer-managed encryption keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
• 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 SecOps depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket.”
• Google SecOps depends on service account From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket. You must grant this service account access to your bucket.”
• Apigee works with BigQuery From the official documentation: “You can use the Apigee API to export all analytics data for an entire day from Apigee to your own data repository, such as Google Cloud Storage or BigQuery.”
• Apigee works with Cloud Run From the official documentation: “Apigee supports using [Google OAuth tokens](https://developers.google.com/identity/protocols/oauth2) or [OpenID Connect tokens](https://developers.google.com/identity/protocols/oauth2/openid-connect) to authenticate with Google services such as [Cloud…”
• Apigee works with Google SecOps From the official documentation: “This document explains how to integrate Apigee with [Google Security Operations](/chronicle/docs/secops/secops-overview) (Google SecOps).”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with Compute Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• BigQuery works with service account From the official documentation: “The service account can be used by services, such as Cloud Run, to read and modify data in the BigQuery dataset.”
• Cloud Build depends on Cloud Storage From the official documentation: “Cloud Build uses Cloud Storage to store build resources.”
• Cloud Build works with Compute Engine From the official documentation: “Automating builds on repository events ensures that Cloud Build immediately validates, builds, and publishes your custom OS images to Compute Engine and Artifact Registry upon code review or merge.”
• Cloud Build is an alternative to Compute Engine From the official documentation: “If Cloud Build is not available, use a small Compute Engine VM with a cron job to pull IOC data and write to GCS.”
• Cloud Build works with OpenID Connect From the official documentation: “Cloud Build provides built-in support for the [OpenID Connect (OIDC)](https://openid.net/connect/) standard for secure authentication and authorization between services.”
• Cloud Build depends on service account From the official documentation: “Cloud Build uses a service account to execute builds on your behalf.”
• Cloud Run depends on Cloud Build From the official documentation: “By default, Cloud Run uses the [default machine type provided by Cloud Build](/build/pricing).”
• Cloud Run works with Compute Engine From the official documentation: “This lets Cloud Run clients use this backend service route to send requests directly to Compute Engine instances.”
• Cloud Run is an alternative to Compute Engine From the official documentation: “The decision of whether to use Cloud Run, GKE, or Compute Engine as your application host involves trade-offs between configuration flexibility and management effort.”
• Cloud Run works with Google SecOps From the official documentation: “This guide explains how to export Cloud Run logs to Google Security Operations using Cloud Storage.”
• Cloud Run works with OpenID Connect From the official documentation: “Makes an authenticated request within a workflow, using OpenID Connect (OIDC) to connect with Cloud Run.”
• Cloud Run works with service account From the official documentation: “Map a custom Service Account to a Cloud Run service”
• Compute Engine works with Google SecOps From the official documentation: “This document explains how to integrate Compute Engine with Google Security Operations.”
• 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 Apigee From the official documentation: “To ensure that customer-managed encryption keys are always used when encrypting your data in Apigee, create the following organization policy constraint:”
• customer-managed encryption keys secures Cloud Run From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Cloud Run.”
• customer-managed encryption keys depends on service account From the official documentation: “To use a CMEK on a project, you must have a service account and you must grant the key access to the service account.”
• Organization Policy Service configures Compute Engine From the official documentation: “You can use organization policies to enforce constraints on how Compute Engine resources, such as virtual machine (VM) instances, disks, and networks, are configured.”
• service account depends on Cloud Storage From the official documentation: “Google SecOps uses a unique service account to read data from your GCS bucket. You must grant this service account access to your bucket.”