service agent

Related topics

• BigQuery Data Transfer Service depends on service agent From the official documentation: “The BigQuery Data Transfer Service uses a [service agent](/iam/docs/service-account-types#service-agents) to access and manage your resources.”
• Security Command Center depends on service agent From the official documentation: “Granting the roles to each service agent is required for Security Command Center to function.”
• BigQuery Data Transfer Service configures service agent From the official documentation: “When you enable the BigQuery Data Transfer Service API, a [service agent](/bigquery/docs/enable-transfer-service#service_agent) is created for your project.”
• Customer-Managed Encryption Keys depends on service agent From the official documentation: “You need to create a [service agent](/iam/docs/service-agents) identity for each project that requires customer-managed encryption keys.”
• service agent depends on Cloud Key Management Service From the official documentation: “The [`gcloud beta services identity create`](/sdk/gcloud/reference/beta/services/identity/create) command creates or gets the [service agent](/iam/docs/service-account-types#service-agents) that AlloyDB can use to access the Cloud KMS key on your behalf.”
• service agent depends on Cloud KMS CryptoKey Encrypter/Decrypter From the official documentation: “As long as the service agent has the **CryptoKey Encrypter/Decrypter** role, the service can encrypt and decrypt its data.”
• service agent depends on Pub/Sub From the official documentation: “Your service agent must have [publishing access](/pubsub/docs/access-control#console) on the Pub/Sub topic.”
• service agent depends on service account From the official documentation: “The BigQuery Data Transfer Service uses a [*service agent*](/iam/docs/service-account-types#service-agents) to get the access token for the user-provided service account (transfer owner).”
• service agent depends on Service Account Token Creator From the official documentation: “To enable the service agent to generate an [access token](/docs/authentication/token-types#access-tokens) from the user-managed service account, grant the service agent access to the user-managed service account, and assign the **Service Account Token Creator** role…”
• service agent is an alternative to user-managed service account From the official documentation: “Grant the permissions listed in [Service agent permissions](/storage-transfer/docs/iam-cloud#manually_assigning_roles) to the user-managed service account, instead of to the service agent.”
• 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”
• Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• 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 Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Cloud Run depends on Pub/Sub From the official documentation: “Cloud Run function triggered by Pub/Sub to fetch HYPR MFA logs and write to GCS.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• 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.”
• 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.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• BigQuery works with BigQuery Data Transfer Service From the official documentation: “The BigQuery Data Transfer Service uses load jobs to load Amazon S3 data into BigQuery.”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using 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.”
• Service Account Token Creator configures service account From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Security Command Center depends on Application Default Credentials From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• 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 Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• 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.”
• 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.”
• Pub/Sub works with Secret Manager From the official documentation: “Receive notifications via Pub/Sub when Secret Manager resources change.”
• Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials works with Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• 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 Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• 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.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• Application Default Credentials works with Cloud Key Management Service From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Run From the official documentation: “To authenticate to Cloud Run, set up Application Default Credentials.”
• 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:”
• BigQuery 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.”
• BigQuery Data Transfer Service works with Cloud Storage From the official documentation: “- [Cloud Storage](/bigquery/docs/cloud-storage-transfer)”
• Cloud Logging works with Security Command Center From the official documentation: “Viewing findings in Cloud Logging is only available if you activate the Premium or Enterprise tier of Security Command Center.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run works with Secret Manager From the official documentation: “The secret is configured to be accessible by Cloud Run and Cloud Build.”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, 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 works with Security Command Center From the official documentation: “To authenticate to Security Command Center, set up Application Default Credentials.”
• Application Default Credentials works with service account From the official documentation: “You can authenticate the service account using Application Default Credentials (ADC) or a service account key.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with Security Command Center From the official documentation: “Security Command Center supports discovery and inventory of BigQuery datasets.”
• BigQuery Data Transfer Service works with Cloud Logging From the official documentation: “The BigQuery Data Transfer Service exports logs and metrics to Cloud Monitoring and Cloud Logging that provide observability into your transfers.”
• BigQuery Data Transfer Service works with Pub/Sub From the official documentation: “If you intend to set up transfer run notifications for Pub/Sub, you must have `pubsub.topics.setIamPolicy` permissions.”
• BigQuery Data Transfer Service works with service account From the official documentation: “BigQuery Data Transfer Service lets you authenticate data transfers for supported data sources by using a [service account](/iam/docs/service-account-overview) instead of individual user credentials.”
• Cloud Key Management Service works with service account From the official documentation: “When your Database Migration Service migration jobs have CMEK enabled, you need to use a service account to request key access from Cloud Key Management Service.”
• Cloud Logging depends on Application Default Credentials From the official documentation: “To authenticate to Logging, set up Application Default Credentials.”