service accounts

Related topics

• IAM roles configures service accounts From the official documentation: “You can grant IAM roles to users, groups, and service accounts. These roles define what they can do with your resources.”
• Cloud Run functions depends on service accounts From the official documentation: “Your Cloud Run function runs as an automatically created service account.”
• 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.”
• service accounts secures Cloud Run functions From the official documentation: “You can use dedicated service accounts for authentication to invoke Cloud Run functions from the ABAP SDK.”
• 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).”
• 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”
• Cloud Run functions works with Pub/Sub From the official documentation: “Use Cloud Run functions to publish messages on Pub/Sub.”
• BigQuery works with Cloud Run functions From the official documentation: “Learn how to write an HTTP Cloud Run function that submits a query to BigQuery.”
• BigQuery works with Spanner From the official documentation: “Federated analytics seamlessly combine data from Spanner and other sources in BigQuery.”
• Cloud Run functions works with Cloud Scheduler From the official documentation: “For more advanced scenarios, Cloud Scheduler with<br>Cloud Run functions for automation.”
• Cloud Scheduler works with Pub/Sub From the official documentation: “Create a Pub/Sub topic to set up as your Cloud Scheduler job target.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• 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.”
• Cloud Run functions works with Cloud Storage From the official documentation: “(GCF translates GCS notifications to HTTP requests internally)”
• Cloud Run functions depends on Pub/Sub From the official documentation: “The Pub/Sub message triggers Cloud Run functions.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• 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.”
• Cloud Run functions works with Spanner From the official documentation: “Using Spanner with Cloud Run functions (1st gen)”
• Cloud Scheduler depends on service account From the official documentation: “To sync a replicated taxonomy across locations with Cloud Scheduler, you need a service account.”
• IAM roles is part of Identity and Access Management From the official documentation: “IAM roles give the principals permissions to perform tasks on your App Topology resources.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Spanner From the official documentation: “Identity and Access Management (IAM) lets you control user and group access to Spanner resources at the project, Spanner instance, and Spanner database levels.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Run functions 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 service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• IAM roles configures service account From the official documentation: “2. [Grant the necessary Identity and Access Management roles](#grant-iam-roles) to your service account.”
• Pub/Sub works with service account From the official documentation: “5. Creates a service account to represent the Pub/Sub subscription identity.”
• 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 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 Run functions depends on Cloud Storage From the official documentation: “Cloud Run functions uses the config in Cloud Storage to determine what actions to take for each stateful MIG.”
• Cloud Scheduler depends on Identity and Access Management From the official documentation: “Cloud Scheduler uses Identity and Access Management (IAM) for authorization.”
• Cloud Scheduler depends on Pub/Sub From the official documentation: “Cloud Pub/Sub (required for Cloud Scheduler to invoke functions)”
• 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 Spanner From the official documentation: “Move Spanner databases to and from Avro or CSV files stored in Cloud Storage.”
• IAM roles secures Cloud Storage From the official documentation: “**Fine-grained access control**: Control agent access to Cloud Storage precisely using [IAM roles](/storage/docs/access-control/iam-roles).”
• IAM roles works with service account From the official documentation: “In this section, you designate the service account for the gateway proxies and assign them the correct IAM roles.”
• IAM roles secures Spanner From the official documentation: “To control access to the entire database, use [IAM roles](/spanner/docs/iam).”
• Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
• Identity and Access Management secures Cloud Run functions From the official documentation: “For Cloud Run functions backend services, [Identity and Access Management (IAM)](https://cloud.google.com/iam/docs) is used to control the ability to view, create, update and delete functions.”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management configures service account From the official documentation: “Learn more about using Identity and Access Management to [create a service account](/iam/docs/creating-managing-service-accounts) and [manage the access granted to a service account](/iam/docs/granting-changing-revoking-access).”
• Pub/Sub depends on Cloud Run functions From the official documentation: “After you have set up Cloud Run functions to process model output and generate events, you can set up event notification with Pub/Sub.”
• service account depends on BigQuery From the official documentation: “Each feature view uses a service account to access the source data in BigQuery during sync.”
• service account works with Spanner From the official documentation: “The service account has access to the Spanner instance.”