IAM role

Related topics

• IAM role is part of Identity and Access Management From the official documentation: “This page explains the [Identity and Access Management](/iam) roles that are available for the Cloud Billing APIs.”
• IAM permissions is part of IAM role From the official documentation: “Each role contains a list of permissions that let the member interact with the resource.”
• IAM policy configures IAM role From the official documentation: “IAM policies grant specific roles to a project member, giving that identity certain permissions.”
• IAM role secures BigQuery From the official documentation: “You can use predefined and custom IAM roles to give principals the required access to BigQuery resources.”
• IAM role configures dataset From the official documentation: “To grant access to routines you can grant an IAM role with the `bigquery.routines.get` permission on the dataset or on the individual routine.”
• IAM role works with principal From the official documentation: “To give a principal the required permissions, you grant an IAM role to the principal.”
• IAM role configures principal From the official documentation: “When you grant a role to a principal, you grant them all the permissions that the role contains.”
• IAM role configures service account From the official documentation: “5. Use `gcloud storage buckets add-iam-policy-binding` to grant the `storage.objectAdmin` [IAM role](/storage/docs/access-control/iam-roles) to the service account for the bucket.”
• IAM role secures service account From the official documentation: “In order to make API requests as a service account, your currently selected account must have an IAM role that includes the `iam.serviceAccounts.getAccessToken` permission for the service account or accounts.”
• predefined roles is part of IAM role From the official documentation: “You can use the following types of roles in IAM to grant access to BigQuery resources: - [**Predefined roles**](/iam/docs/roles-overview#predefined) are managed by Google Cloud and support common use cases and access control patterns.”
• 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”
• BigQuery works with Cloud SQL From the official documentation: “Add credentials to connect BigQuery to Cloud SQL.”
• Cloud SQL works with Cloud Storage From the official documentation: “Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file.”
• custom roles is an alternative to predefined roles From the official documentation: “Generally, we recommend that you [use predefined roles](/iam/docs/choose-predefined-roles) instead of basic or custom roles.”
• BigQuery works with Dataflow From the official documentation: “Read from BigQuery to Dataflow”
• Cloud Storage works with Dataflow From the official documentation: “Write from Dataflow to Cloud Storage”
• BigQuery is an alternative to Google Cloud Storage From the official documentation: “The training data can be either a CSV file in Cloud Storage or a table in BigQuery.”
• BigQuery works with Google Cloud Storage From the official documentation: “Load Cloud Storage data into BigQuery”
• IAM permissions is part of IAM roles From the official documentation: “IAM roles that apply to Cloud SQL and the permissions contained in each role.”
• 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.”
• 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 Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• custom roles is part of IAM roles From the official documentation: “This requirement applies to both [predefined roles](/iam/docs/roles-permissions) and [custom roles](/iam/docs/roles-overview#custom).”
• custom roles is part of Identity and Access Management From the official documentation: “To support this, IAM offers [custom roles](/iam/docs/creating-custom-roles).”
• Dataflow depends on Cloud Storage From the official documentation: “Begin by creating a Cloud Storage bucket using the Google Cloud console or Google Cloud CLI. The Dataflow pipeline uses this bucket as a temporary storage location.”
• Dataflow works with Google Cloud Storage From the official documentation: “When you run a pipeline using Dataflow, your results are stored in a 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.”
• predefined roles is part of IAM roles From the official documentation: “This requirement applies to both [predefined roles](/iam/docs/roles-permissions) and [custom roles](/iam/docs/roles-overview#custom).”
• principal depends on IAM permissions From the official documentation: “When you grant an IAM *role* to a *principal*, such as a user account, that principal obtains certain *permissions* that allow them to perform actions.”
• 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 SQL depends on Cloud Storage From the official documentation: “When ingesting data from Cloud SQL, data is first staged to a Cloud Storage bucket.”
• Cloud SQL works with Dataflow From the official documentation: “Use Datastream to replicate changes from your MySQL instance to either BigQuery or Cloud Storage, and then use Dataflow or Managed Service for Apache Spark to bring the data into your Cloud SQL instance.”
• Cloud SQL works with Identity and Access Management From the official documentation: “This page describes how Cloud SQL is integrated with IAM .”
• Cloud Storage works with custom roles From the official documentation: “VPC Service Controls supports [custom roles](/iam/docs/creating-custom-roles) for Cloud Storage in ingress and egress rules, but doesn't support the [predefined Cloud Storage roles](/storage/docs/access-control/iam-roles#standard-roles).”
• 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).”
• Dataflow depends on Google Cloud Storage From the official documentation: “- A gcs bucket for staging DataFlow files. Replace `<BUCKET_NAME>`: the name of a valid Google Cloud Storage bucket.”
• Dataflow depends on Identity and Access Management From the official documentation: “Dataflow uses Identity and Access Management (IAM) for authorization.”
• Dataflow works with service account From the official documentation: “If you use query engines such as Managed Service for Apache Spark or Dataflow to read table data, grant this role to the service account that you use to run jobs in that engine.”
• dataset is part of BigQuery From the official documentation: “Create a BigQuery dataset to store your models and sample data:”
• dataset depends on Google Cloud Storage From the official documentation: “Create a dataset using an empty Cloud Storage bucket.”
• IAM permissions is part of custom roles From the official documentation: “A role is a collection of permissions.”
• IAM permissions works with IAM roles From the official documentation: “This page lists the IAM roles and permissions for Apigee Registry.”
• IAM policy configures Cloud Storage From the official documentation: “Access to new buckets is managed using IAM policies instead of<br>[Cloud Storage Access control lists (ACLs)](/storage/docs/access-control/lists).”
• IAM policy configures IAM roles From the official documentation: “When you add a new member to your project, you can use an [Identity and Access Management (IAM)](/iam) policy to give that member one or more IAM roles to control the actions that the member can perform in Migration Center.”
• IAM policy is part of Identity and Access Management From the official documentation: “IAM lets you control **who (users)** has **what access (roles)** to **which resources** by setting IAM policies.”
• IAM policy configures principal From the official documentation: “When you add new principals to your project, you can use an [Identity and Access Management (IAM)](/iam/docs) policy to give that principal one or more IAM roles.”
• 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 configures principal From the official documentation: “To control who can view, create, or update Security Command Center resources, you grant IAM roles to principals, such as users, groups, or service accounts.”
• 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 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 configures Dataflow From the official documentation: “To control access to Dataflow resources for users, groups, and service accounts in a project or organization, use Identity and Access Management (IAM).”
• Identity and Access Management secures dataset From the official documentation: “IAM lets you control who has access to your datasets and data stores.”
• Identity and Access Management configures Google Cloud Storage From the official documentation: “Grant permission for the service account to list and view files in the bucket: ```bash gcloud storage buckets add-iam-policy-binding gs://${PROJECT_ID}-bucket/ \ --member=serviceAccount:sa-test-app-team-x@${PROJECT_ID}.iam.gserviceaccount.com \ --role=roles/storage.objectViewer…”
• Identity and Access Management secures Google Cloud Storage From the official documentation: “These modifications to that file define a second backup repository in a Cloud Storage bucket, accessed through Identity and Access Management (IAM).”
• Identity and Access Management configures IAM permissions From the official documentation: “You can use IAM to manage who can access your project and what they are allowed to do.”
• 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).”