Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • kms_asymmetric_encryption_key
          • kms_asymmetric_encryption_key_iam_binding
          • kms_asymmetric_encryption_key_iam_member
          • kms_asymmetric_signature_key
          • kms_asymmetric_signature_key_iam_binding
          • kms_asymmetric_signature_key_iam_member
          • kms_secret_ciphertext
          • kms_symmetric_key
          • kms_symmetric_key_iam_binding
          • kms_symmetric_key_iam_member

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Import
  1. Terraform reference
  2. Resources
  3. Key Management Service (KMS)
  4. Resources
  5. kms_symmetric_key_iam_binding

yandex_kms_symmetric_key_iam_binding (Resource)

Written by
Yandex Cloud
Updated at September 18, 2025
  • Example usage
  • Schema
    • Required
    • Optional
  • Import

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

Example usageExample usage

//
// Create a new KMS Symmetric Key and new IAM Binding for it.
//
resource "yandex_kms_symmetric_key" "your-key" {
  name = "symmetric-key-name"
}

resource "yandex_kms_symmetric_key_iam_binding" "viewer" {
  symmetric_key_id = yandex_kms_symmetric_key.your-key.id
  role             = "viewer"

  members = [
    "userAccount:foo_user_id",
  ]
}

SchemaSchema

RequiredRequired

  • 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.

Warning

for more information about system groups, see Cloud Documentation.

  • role (String) The role that should be assigned. Only one yandex_kms_symmetric_key_iam_binding can be used per role.
  • symmetric_key_id (String) The ID of the compute symmetric_key to attach the policy to.

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.

# terraform import yandex_kms_symmetric_key_iam_binding.<resource Name> "<resource Id>,<resource Role>"
terraform import yandex_kms_symmetric_key_iam_binding.viewer "abjjf**********p3gp8,viewer"

Was the article helpful?

Previous
kms_symmetric_key
Next
kms_symmetric_key_iam_member
© 2025 Direct Cursus Technology L.L.C.