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
          • serverless_workflow
          • serverless_workflow_iam_binding
  1. Terraform reference
  2. Resources
  3. Serverless Workflows
  4. Resources
  5. serverless_workflow_iam_binding

yandex_serverless_workflow_iam_binding (Resource)

Written by
Yandex Cloud
Updated at July 9, 2026
View in Markdown

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

Warning

Warning: This resource is authoritative for the given role on the target workflow and manages the complete set of its members. When you change or delete yandex_serverless_workflow_iam_binding, the role may be removed from other subjects on the workflow 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.

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.

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

Was the article helpful?

Previous
serverless_workflow
Next
smartcaptcha_captcha
© 2026 Direct Cursus Technology L.L.C.