Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 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
          • cloudregistry_folder
          • cloudregistry_folder_iam_binding
          • cloudregistry_folder_iam_member
          • cloudregistry_lifecycle_policy
          • cloudregistry_registry
          • cloudregistry_registry_iam_binding
          • cloudregistry_registry_iam_member
          • cloudregistry_registry_ip_permission
          • cloudregistry_scan_policy

In this article:

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

yandex_cloudregistry_registry_iam_binding (Resource)

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

Manages the members of a single IAM role on an existing registry.

On creation, the specified members are added to the role without removing existing members. On update, the resource replaces the members of the previously managed role with the configured bindings. On deletion, it removes the managed role from all of its members, including those not listed in this resource. Other roles on the target resource are preserved.

Warning

Warning: Updating or deleting yandex_cloudregistry_registry_iam_binding can revoke access granted outside this resource, including access granted through *_iam_member, the management console, CLI or API. Those subjects are not tracked in this resource's Terraform state and are not shown in its normal plan diff. The provider attempts to list affected subjects in a separate warning during planning when it can read the current access bindings. An absent warning does not guarantee that no other subjects will lose access.

Warning

Only one yandex_cloudregistry_registry_iam_binding resource may manage a given role on a given registry. Do not use *_iam_binding and *_iam_member for the same role on the same target resource: they will conflict over the role's members. They can be used together for different roles. Use *_iam_member to manage an individual member while preserving other members of the role.

Example usageExample usage

//
// Create a new Cloud Registry and new IAM Binding for it.
//
resource "yandex_cloudregistry_registry" "your-registry" {
  name      = "test-registry"
  folder_id = "test_folder_id"

  labels = {
    my-label = "my-label-value"
  }
  kind      = "DOCKER"
  type      = "LOCAL"

  description = "Some desctiption"
}

resource "yandex_cloudregistry_registry_iam_binding" "puller" {
  registry_id = yandex_cloudregistry_registry.your-registry.id
  role        = "cloud-registry.artifacts.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 registry to attach the policy to.
  • role (Required)(String). The role that should be assigned. Only one yandex_cloudregistry_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_cloudregistry_registry_iam_binding.<binding Name> "<registry_id>,<resource Role>"
terraform import yandex_cloudregistry_registry_iam_binding.puller "crps9**********k9psn,cloudregistry-registry.images.puller"

Was the article helpful?

Previous
cloudregistry_registry
Next
cloudregistry_registry_iam_member
© 2026 Direct Cursus Technology L.L.C.