gcloud alpha compute backend-services add-iam-policy-binding - add an IAM policy binding to a Compute Engine backend service
gcloud alpha compute backend-services add-iam-policy-binding BACKEND_SERVICE_NAME --member=PRINCIPAL --role=ROLE [--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Add an IAM policy binding to a Compute Engine backend service.
To add an IAM policy binding for the role of 'compute.loadBalancerServiceUser' for the user 'test-user@gmail.com' with backend service 'my-backend-service' and region 'REGION', run:
$ gcloud alpha compute backend-services add-iam-policy-binding \ my-backend-service --region=REGION \ --member='user:test-user@gmail.com' \ --role='roles/compute.loadBalancerServiceUser'
$ gcloud alpha compute backend-services add-iam-policy-binding \ my-backend-service --global \ --member='user:test-user@gmail.com' \ --role='roles/compute.loadBalancerServiceUser'
See https://cloud.google.com/iam/docs/managing-policies for details of policy role and member types.
- BACKEND_SERVICE_NAME
Name of the backend service to operate on.
- --member=PRINCIPAL
The principal to add the binding for. Should be of the form user|group|serviceAccount:email or domain:domain.
Examples: user:test-user@gmail.com, group:admins@example.com, serviceAccount:test123@example.domain.com, or domain:example.domain.com.
Some resources also accept the following special values:
- —
allUsers - Special identifier that represents anyone who is on the internet, with or without a Google account.
- —
allAuthenticatedUsers - Special identifier that represents anyone who is authenticated with a Google account or a service account.
- --role=ROLE
Role name to assign to the principal. The role name is the complete path of a predefined role, such as roles/logging.viewer, or the role ID for a custom role, such as organizations/{ORGANIZATION_ID}/roles/logging.viewer.
- At most one of these can be specified:
- --global
If set, the backend service is global.
- --region=REGION
Region of the backend service to operate on. Overrides the default compute/region property value for this command invocation.
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:
$ gcloud compute backend-services add-iam-policy-binding
$ gcloud beta compute backend-services add-iam-policy-binding