predefined roles

Related topics

• 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.”
• basic roles is an alternative to predefined roles From the official documentation: “To keep your project and clusters secure, use [predefined Roles](#predefined) whenever possible.”
• 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).”
• IAM policies configures predefined roles From the official documentation: “Predefined roles, which you grant by using IAM policies, contain permissions that let principals perform specific actions.”
• predefined roles configures IAM permissions From the official documentation: “IAM predefined roles let you manage the permissions available to users.”
• 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.”
• predefined roles is part of Identity and Access Management From the official documentation: “There are three types of roles in IAM: - **Predefined roles** provide granular access for a specific service and are managed by Google Cloud.”
• custom roles is an alternative to predefined role From the official documentation: “Consolidate multiple predefined roles into fewer custom roles to reduce the space consumed.”
• 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 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.”
• basic roles is part of Identity and Access Management From the official documentation: “IAM provides three types of roles: [predefined roles](#predefined-compute-engine-roles), [basic roles](#basic-iam-roles), and [custom roles](/iam/docs/understanding-custom-roles).”
• Bigtable is an alternative to Cloud Storage From the official documentation: “If the joining data is in the gigabyte or terabyte range, use either Bigtable or Cloud Storage to merge the joining data to the driving data, depending on the nature of the data.”
• 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).”
• IAM policies configures principal From the official documentation: “IAM policies grant specific roles to principals, thereby giving them certain permissions.”
• 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.”
• 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.”
• basic roles is an alternative to predefined role From the official documentation: “Instead, grant the most limited predefined roles or custom roles that meet your needs.”
• Bigtable works with Cloud Storage From the official documentation: “For example, if you frequently write data to Bigtable from a Cloud Storage bucket in the `us-central1` (Iowa) region, create your Bigtable cluster in a zone within `us-central1`.”
• 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).”
• IAM permissions is part of custom roles From the official documentation: “A role is a collection of permissions.”
• 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 permissions works with IAM roles From the official documentation: “This page lists the IAM roles and permissions for Apigee Registry.”
• IAM policies configures Bigtable From the official documentation: “Bigtable uses [IAM](/iam) for access control. To control who has access a resource, set IAM policies on the resource.”
• 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 role From the official documentation: “IAM policies grant specific roles to a project member, giving that identity certain permissions.”
• 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 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.”
• IAM roles secures Bigtable From the official documentation: “Access to your Bigtable tables is controlled by your Google Cloud project and the [Identity and Access Management (IAM) roles](/bigtable/docs/access-control#roles) that you assign to users.”
• 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 Bigtable From the official documentation: “Bigtable uses Identity and Access Management (IAM) for authorization.”
• 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 IAM policies From the official documentation: “IAM lets you control **who** (identity) has **what access** (roles) to **which resource** by setting IAM policies.”
• 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).”
• predefined role is part of Identity and Access Management From the official documentation: “To make it easier to give these users the permissions that they need, Identity and Access Management (IAM) offers predefined roles that are designed for specific job functions.”
• principal works with service account From the official documentation: “The previous query searches for audit logs that capture roles being granted to a principal on a service account.”