Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Container Registry
  • Getting started
    • All guides
    • Installing and configuring Docker
    • Authentication in Container Registry
    • Scanning Docker images for vulnerabilities
    • Creating a trigger for a registry
      • Assigning a role
      • Viewing assigned roles
      • Revoking a role
  • Yandex Container Solution
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Troubleshooting
  • FAQ
  1. Step-by-step guides
  2. Working with roles
  3. Assigning a role

Assigning a role for a resource

Written by
Yandex Cloud
Updated at August 3, 2026
View in Markdown

To grant access to a resource, assign a role to a subject for the resource itself or for a resource from which access permissions are inherited, such as a folder or cloud. For the current list of resources you can assign roles for, see Resources you can assign a role for.

Management console
CLI
Terraform
API
  1. In the management console, select the folder where you want to assign a role for a resource.
  2. Navigate to Container Registry.
  3. Select a registry or repository in it.
  4. Navigate to the Access bindings tab.
  5. Click Assign roles.
  6. In the window that opens, select a group, user, or service account.
  7. Click Add role and select role from the list.
  8. Click Save.

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:

  • To a user:

    yc container <resource> add-access-binding <resource_name_or_ID> \
      --role <role> \
      --user-account-id <user_ID>
    
  • To a service account:

    yc container <resource> add-access-binding <resource_name_or_ID> \
      --role <role> \
      --service-account-id <service_account_ID>
    
  • To all authenticated users (the All authenticated users public group):

    yc container <resource> add-access-binding <resource_name_or_ID> \
      --role <role> \
      --all-authenticated-users
    

    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.

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 \
  --user-account-id 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 = [
          "userAccount:<user_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: ID of the user, group, or service account getting the role.
    • 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 = [
          "serviceAccount:<service_account_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: ID of the user, group, or service account getting the role.

    For more information about yandex_container_repository_iam_binding, see this provider guide.

    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 whether the role has been assigned 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>
    

Use the updateAccessBindings REST API method for the Registry resource or the RegistryService/UpdateAccessBindings gRPC API call.

Use the updateAccessBindings REST API method for the Repository resource or the RepositoryService/UpdateAccessBindings gRPC API call.

Was the article helpful?

Previous
Creating a trigger for a registry
Next
Viewing assigned roles
© 2026 Direct Cursus Technology L.L.C.