Assigning a role for a resource

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id.

If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

Run this command to assign a role for a resource:

yc container <resource> add-access-binding <resource_name_or_ID> \
  --role <role> \
  --subject <subject_type>:<subject_ID>

Where:

• <resource>: registry or repository resource type.

• <resource_name_or_ID>: Name or ID of the resource to assign the role for.

• --role: Role you want to assign.

• --subject: Subject getting the role.

  Subject designations

  To indicate a subject, use the --subject parameter in <subject_type>:<ID> format. For some subject types, the Yandex Cloud CLI provides separate parameters instead of --subject, where you only need to specify the subject name or ID without the type. Possible subject designations and matching CLI parameters:

  Subject type	Subject designation	Yandex Cloud CLI parameter
  userAccount	userAccount:<user_ID>	--user-account-id or --user-yandex-login
  serviceAccount	serviceAccount:<service_account_ID>	--service-account-id or --service-account-name
  federatedUser	federatedUser:<user_ID>	--user-account-id
  group	group:<group_ID>	--group-members
  system	system:allAuthenticatedUsers (All authenticated users group)	--all-authenticated-users
  	system:allUsers (All users group)	—
  	system:group:organization:<organization_ID>:users (All users in organization X group)	--organization-users
  	system:group:federation:<federation_ID>:users (All users in federation N group)	--federation-users
  	system:group:userpool:<pool_ID>:users (All users in userpool P group)	—

Example

In the example below, we are assigning the container-registry.admin role for my-first-registry to a user.

yc container registry add-access-binding my-first-registry \
  --role container-registry.admin \
  --subject userAccount:ajeugsk5ubk6********

Result:

done (4s)

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

1. Describe the following in the configuration file:

   • The yandex_container_registry_iam_binding resource parameters to assign the role for the registry:

     resource "yandex_container_registry_iam_binding" "registry_name" {
       registry_id = "<registry_ID>"
       role        = "<role>"
     
       members = [
         "<subject_type>:<subject_ID>",
       ]
     }
     

     Where:

     • registry_id: ID of the registry for which the role is being assigned. To find out the registry ID, get a list of registries in the folder.

     • role: Role you want to assign.

     • members: List of designations of subjects the role is assigned to.

       Subject designations

       To indicate a subject, use a combination of its type and unique ID, i.e., <subject_type>:<ID>. Here is how you can designate a subject:

       Subject type	Subject designation
       userAccount	userAccount:<user_ID>
       serviceAccount	serviceAccount:<service_account_ID>
       federatedUser	federatedUser:<user_ID>
       group	group:<group_ID>
       system	system:allAuthenticatedUsers (All authenticated users group)
       	system:allUsers (All users group)
       	system:group:organization:<organization_ID>:users (All users in organization X group)
       	system:group:federation:<federation_ID>:users (All users in federation N group)
       	system:group:userpool:<pool_ID>:users (All users in userpool P group)

   • The yandex_container_repository_iam_binding resource parameters to assign the role for the repository:

     resource "yandex_container_repository_iam_binding" "repository_name" {
       repository_id = "<repository_ID>"
       role          = "<role>"
     
       members = [
         "<subject_type>:<subject_ID>",
       ]
     }
     

     Where:

     • repository_id: ID of the repository for which you are assigning the role. To find out the repository ID, get a list of repositories in the folder.

     • role: Role you want to assign.

     • members: List of designations of subjects getting the role.

       Subject designations

       To indicate a subject, use a combination of its type and unique ID, i.e., <subject_type>:<ID>. Here is how you can designate a subject:

       Subject type	Subject designation
       userAccount	userAccount:<user_ID>
       serviceAccount	serviceAccount:<service_account_ID>
       federatedUser	federatedUser:<user_ID>
       group	group:<group_ID>
       system	system:allAuthenticatedUsers (All authenticated users group)
       	system:allUsers (All users group)
       	system:group:organization:<organization_ID>:users (All users in organization X group)
       	system:group:federation:<federation_ID>:users (All users in federation N group)
       	system:group:userpool:<pool_ID>:users (All users in userpool P group)

   For more on the properties of the yandex_container_repository_iam_binding resource, see this provider guide.

2. 1. In the terminal, navigate to the configuration file directory.

   2. Make sure the configuration is correct using this command:

      terraform validate
      

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.
      

   3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

   4. Apply the configuration changes:

      terraform apply
      

   5. Type yes and press Enter to confirm the changes.

You can check the role assignment using the management console or this CLI command:

• Registry:

  yc container registry list-access-bindings <registry_name_or_ID>
  

• Repository:

  yc container repository list-access-bindings <repository_name_or_ID>
  

To assign a role for a registry, use the updateAccessBindings REST API method for the Registry resource or the RegistryService/UpdateAccessBindings gRPC API call.

To assign a role for a repository, use the updateAccessBindings REST API method for the Repository resource or the RepositoryService/UpdateAccessBindings gRPC API call.

In the request body, set the action property to ADD and specify subject type and ID in the subject property.