yandex_dns_zone_iam_binding (Resource)

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

Example usageExample usage

//
// Create a new DNS Zone and new IAM Binding for it.
//
resource "yandex_dns_zone" "zone1" {
  name = "my-private-zone"
  zone = "example.com."
}

resource "yandex_dns_zone_iam_binding" "viewer" {
  dns_zone_id = yandex_dns_zone.zone1.id
  role        = "dns.viewer"
  members     = ["userAccount:foo_user_id"]
}

SchemaSchema

RequiredRequired

• dns_zone_id (String) The ID of the compute dns_zone 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_dns_zone_iam_binding can be used per role.

OptionalOptional

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

ImportImport

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

IAM binding imports use space-delimited identifiers; first the resource in question and then the role. These bindings can be imported using the dns_zone_id and role.

# terraform import yandex_dns_zone_iam_binding.<resource Name> "dns_zone_id,dns.viewer"
terraform import yandex_dns_zone_iam_binding.viewer "dns9m**********tducf,dns.viewer"