yandex_compute_instance_iam_binding (Resource)

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

Example usageExample usage

//
// Create a new Compute Instance and new IAM Binding for it.
//
resource "yandex_compute_instance" "vm1" {
  name        = "test"
  platform_id = "standard-v3"
  zone        = "ru-central1-a"

  resources {
    cores  = 2
    memory = 4
  }

  boot_disk {
    disk_id = yandex_compute_disk.boot-disk.id
  }

  network_interface {
    index     = 1
    subnet_id = yandex_vpc_subnet.foo.id
  }

  metadata = {
    foo      = "bar"
    ssh-keys = "ubuntu:${file("~/.ssh/id_ed25519.pub")}"
  }
}

resource "yandex_compute_instance_iam_binding" "editor" {
  image_id = data.yandex_compute_instance.vm1.id

  role = "editor"

  members = [
    "userAccount:some_user_id",
  ]
}

SchemaSchema

RequiredRequired

• instance_id (String) The ID of the compute instance to attach the policy to.
• members (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.

• role (String) The role that should be assigned. Only one yandex_compute_instance_iam_binding can be used per role.

OptionalOptional

• sleep_after (Number) For test purposes, to compensate IAM operations delay

ImportImport