IAM roles and permissions

Related topics

• Google Cloud console configures IAM roles and permissions From the official documentation: “You can grant and manage IAM roles using the Google Cloud console, the IAM API methods, or the Google Cloud CLI.”
• IAM roles and permissions is part of Cloud Key Management Service From the official documentation: “This page lists the IAM roles and permissions for Cloud Key Management Service.”
• IAM roles and permissions configures service account From the official documentation: “[Create a service account](/iam/docs/service-accounts-create) that has the following Identity and Access Management (IAM) roles and permissions:”
• Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
• Application Default Credentials works with Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• 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.”
• BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials secures Compute Engine From the official documentation: “To authenticate to Compute Engine, 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.”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Key Management Service From the official documentation: “To authenticate to Cloud KMS, 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:”
• 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.”
• service account is part of Identity and Access Management From the official documentation: “Service accounts function as both principals and resources within IAM.”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, 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 works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• 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.”
• 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.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• Secret Manager depends on Application Default Credentials From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• Secret Manager works with service account From the official documentation: “The service account can access the secret data.”
• service account depends on Secret Manager From the official documentation: “Make sure that the service account that AlloyDB Omni uses has the `secretmanager.secretAccessor` permission to read the secret from Secret Manager.”
• Application Default Credentials configures Compute Engine From the official documentation: “To authenticate to Compute Engine, set up Application Default Credentials.”
• Application Default Credentials secures Secret Manager From the official documentation: “To authenticate to Secret Manager, set up Application Default Credentials.”
• 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).”
• 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 Key Management Service depends on Application Default Credentials From the official documentation: “To authenticate to Cloud KMS, set up Application Default Credentials.”
• Cloud Key Management Service works with Google Cloud console From the official documentation: “There is also a web-based interface for [Cloud KMS on the Google Cloud console](https://console.cloud.google.com/security/kms), which allows for key management operations.”
• 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 works with Secret Manager 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 Secret Manager.”
• Cloud Key Management Service is an alternative to Secret Manager From the official documentation: “Secret Manager is the recommended technique for managing sensitive data with Cloud Build. For existing projects, you can continue using Cloud KMS, but for new projects, use Secret Manager.”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
• Google Cloud console configures Compute Engine From the official documentation: “You can use the standard Google Cloud methods to deploy your VMs on Compute Engine: the Google Cloud console, the Google Cloud CLI, Terraform, and the [REST API](/compute/docs/reference/latest).”
• Google Cloud console configures IAM roles From the official documentation: “You can get and set IAM allow policies and IAM roles using the Google Cloud Console.”
• 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.”
• 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 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 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 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).”
• 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 depends on Cloud Key Management Service 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.”