Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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.
Terraform in Yandex Cloud
  • Getting started
  • Setting up Yandex Cloud Terraform provider authentication
  • Solution library
    • Overview
    • Release notes
          • container_registry
          • container_registry_iam_binding
          • container_registry_ip_permission
          • container_repository
          • container_repository_iam_binding
          • container_repository_lifecycle_policy

In this article:

  • Example usage
  • Arguments & Attributes Reference
  • Import
  1. Terraform reference
  2. Resources
  3. Container Registry
  4. Resources
  5. container_registry_iam_binding

yandex_container_registry_iam_binding (Resource)

Written by
Yandex Cloud
Updated at July 9, 2026
View in Markdown
  • Example usage
  • Arguments & Attributes Reference
  • Import

Allows creation and management of a single binding within IAM policy for an existing registry.

Warning

Warning: This resource is authoritative for the given role on the target registry and manages the complete set of its members. When you change or delete yandex_container_registry_iam_binding, the role may be removed from other subjects on the registry as well — including subjects granted outside of this resource (via the corresponding *_iam_member resource, the management console, CLI or API). Those subjects are not tracked in the Terraform state, so a plain terraform plan does not list them. Be careful.

Example usageExample usage

//
// Create a new Container Registry and new IAM Binding for it.
//
resource "yandex_container_registry" "your-registry" {
  folder_id = "your-folder-id"
  name      = "registry-name"
}

resource "yandex_container_registry_iam_binding" "puller" {
  registry_id = yandex_container_registry.your-registry.id
  role        = "container-registry.images.puller"

  members = [
    "system:allUsers",
  ]
}

Arguments & Attributes ReferenceArguments & Attributes Reference

  • id (String). The ID of this resource.
  • members (Required)(Set Of String). An array of identities that will be granted the privilege in the role. Each entry can have one of the following values:
  • userAccount:{user_id}: A unique user ID that represents a specific Yandex account.
  • serviceAccount:{service_account_id}: A unique service account ID.
  • federatedUser:{federated_user_id}: A unique federated user ID.
  • federatedUser:{federated_user_id}:: A unique SAML federation user account ID.
  • group:{group_id}: A unique group ID.
  • system:group:federation:{federation_id}:users: All users in federation.
  • system:group:organization:{organization_id}:users: All users in organization.
  • system:allAuthenticatedUsers: All authenticated users.
  • system:allUsers: All users, including unauthenticated ones.

Warning

for more information about system groups, see Cloud Documentation.

  • registry_id (Required)(String). The ID of the compute registry to attach the policy to.
  • role (Required)(String). The role that should be assigned. Only one yandex_container_registry_iam_binding can be used per role.
  • sleep_after (Number). For test purposes, to compensate IAM operations delay

ImportImport

The resource can be imported by using their resource ID. For getting it you can use Yandex Cloud Web Console or Yandex Cloud CLI.

# terraform import yandex_container_registry_iam_binding.<binding Name> "<registry_id>,<resource Role>"
terraform import yandex_container_registry_iam_binding.puller "crps9**********k9psn,container-registry.images.puller"

Was the article helpful?

Previous
container_registry
Next
container_registry_ip_permission
© 2026 Direct Cursus Technology L.L.C.