principal

Related topics

• IAM policies configures principal From the official documentation: “IAM policies grant specific roles to principals, thereby giving them certain permissions.”
• 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.”
• principal works with role From the official documentation: “A binding binds one or more members, or principals, to a single role.”
• 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 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.”
• 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.”
• role configures principal From the official documentation: “You should set the minimum role needed to give the principal the required access.”
• roles configures principal From the official documentation: “IAM roles give the principals permissions to perform tasks on your Agent Registry resources.”
• service accounts is part of principal From the official documentation: “Cloud Run functions supports two different kinds of identities, which are also called **principals**: - Service accounts: These are special accounts that serve as the identity of a non-person, like a function or an application or a VM.”
• Service Account Token Creator configures service account From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• 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.”
• Cloud Storage works with Compute Engine From the official documentation: “For example, you can create a service account that your Compute Engine instances use to access objects stored in Cloud Storage buckets.”
• 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.”
• service account works with Workload Identity Federation From the official documentation: “When an application uses Workload Identity Federation, it impersonates a service account.”
• 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.”
• Cloud Storage works with service account From the official documentation: “The service account can manage objects in the Cloud Storage bucket.”
• IAM permissions is part of roles From the official documentation: “IAM permissions are [grouped into roles](/document-ai/docs/access-control/iam-roles), and you assign roles to users and groups.”
• 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.”
• 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.”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• role is part of Identity and Access Management From the official documentation: “IAM operates on the security principle of least privilege and controls who can access given resources using IAM roles and permissions.”
• 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 is part of project From the official documentation: “All of your Google Cloud resources belong to a project, including Cloud Storage resources like buckets and objects.”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google 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 permissions works with IAM roles From the official documentation: “This page lists the IAM roles and permissions for Apigee Registry.”
• IAM permissions is part of role From the official documentation: “Each role is a collection of one or more *permissions*.”
• IAM permissions depends on roles From the official documentation: “Permissions are not granted directly to users; permissions are instead granted indirectly through roles, which group permissions.”
• IAM policies configures Compute Engine From the official documentation: “You can [grant access to Compute Engine resources](/compute/docs/access/managing-access-to-resources) such as VM instances, images, and disks, by attaching IAM policies directly to those resources.”
• IAM policies configures roles From the official documentation: “IAM policies grant specific roles to a project member, which gives the identity certain permissions.”
• 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 is part of project From the official documentation: “Removes a policy binding to the IAM policy of a project, given a project ID and the binding.”
• IAM policy configures role From the official documentation: “An IAM policy defines and enforces what roles are granted to which principals, and this policy is then attached to a resource.”
• 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 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.”
• 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).”
• 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.”
• role configures 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.”
• roles configures service accounts From the official documentation: “To manage permissions within your project, you grant roles to individuals and service accounts.”
• service account is part of project From the official documentation: “Service accounts are created within a project and have a unique email address that identifies them.”
• service account depends on Service Account Token Creator From the official documentation: “Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the next service account in the list.”
• Service Account Token Creator secures service account From the official documentation: “Each service account in the list must have the `roles/iam.serviceAccountTokenCreator` role on the next service account in the list.”
• Service Account Token Creator configures service accounts From the official documentation: “Grant the **Service Account Token Creator** role to the service account.”
• 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).”
• service accounts is part of project From the official documentation: “Service accounts are owned by projects, and you can create many service accounts for a project.”
• Workload Identity Federation secures Cloud Storage From the official documentation: “To allow GKE to securely access the Cloud Storage bucket, set up GKE Workload Identity Federation:”
• Workload Identity Federation depends on IAM policies From the official documentation: “Workload Identity Federation doesn't require manual configuration or less secure methods like service account key files because it uses IAM policies.”
• Workload Identity Federation is part of Identity and Access Management From the official documentation: “[Identity and Access Management (IAM)](/iam/docs/overview) lets you manage fine-grained access to services and resources in Google Cloud. IAM includes features such as the following: - [Privileged Access Manager](/iam/docs/pam-overview), which manages on-demand, temporary…”