yandex_serverless_container_iam_binding (Resource)

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

Example usageExample usage

//
// Create a new Serverless Container IAM Binding.
//
resource "yandex_serverless_container_iam_binding" "container-iam" {
  container_id = "your-container-id"
  role         = "serverless.containers.invoker"

  members = [
    "system:allUsers",
  ]
}

SchemaSchema

RequiredRequired

• container_id (String) The ID of the compute container 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_serverless_container_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.

# terraform import yandex_serverless_container_iam_binding.<resource Name> "<resource Id>,<resource Role>"
terraform import yandex_serverless_container_iam_binding.container-iam "...,serverless.containers.invoker"