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
          • datasphere_community
          • datasphere_community_iam_binding
          • datasphere_project
          • datasphere_project_iam_binding

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for limits
  • Nested Schema for settings
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Datasphere
  4. Resources
  5. datasphere_project

yandex_datasphere_project (Resource)

Written by
Yandex Cloud
Updated at August 7, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for limits
    • Nested Schema for settings
    • Nested Schema for timeouts
  • Import

Allows management of Yandex Cloud Datasphere Projects.

Example usageExample usage

//
// Create a new Datasphere Project.
//
resource "yandex_datasphere_project" "my-project" {
  name        = "example-datasphere-project"
  description = "Datasphere Project description"

  labels = {
    "foo" : "bar"
  }

  community_id = yandex_datasphere_community.my-community.id

  limits = {
    max_units_per_hour      = 10
    max_units_per_execution = 10
    balance                 = 10
  }

  settings = {
    service_account_id      = yandex_iam_service_account.my-account.id
    subnet_id               = yandex_vpc_subnet.my-subnet.id
    commit_mode             = "AUTO"
    data_proc_cluster_id    = "foo-data-proc-cluster-id"
    security_group_ids      = [yandex_vpc_security_group.my-security-group.id]
    ide                     = "JUPYTER_LAB"
    default_folder_id       = "foo-folder-id"
    stale_exec_timeout_mode = "ONE_HOUR"
  }
}

resource "yandex_datasphere_community" "my-community" {
  name               = "example-datasphere-community"
  description        = "Description of community"
  billing_account_id = "example-organization-id"
  labels = {
    "foo" : "bar"
  }
  organization_id = "example-organization-id"
}

SchemaSchema

RequiredRequired

  • community_id (String) Community ID where project would be created.
  • name (String) The resource name.

OptionalOptional

  • description (String) The resource name.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • limits (Attributes) Datasphere Project limits configuration. (see below for nested schema)
  • settings (Attributes) Datasphere Project settings configuration. (see below for nested schema)
  • timeouts (Attributes) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) The creation timestamp of the resource.
  • created_by (String) Creator account ID of the Datasphere Project.
  • id (String) The resource identifier.

Nested Schema for Nested Schema for limits

Optional:

  • balance (Number) The number of units available to the project.
  • max_units_per_execution (Number) The number of units that can be spent on the one execution.
  • max_units_per_hour (Number) The number of units that can be spent per hour.

Nested Schema for Nested Schema for settings

Optional:

  • data_proc_cluster_id (String) ID of the DataProcessing cluster.
  • default_folder_id (String) Default project folder ID.
  • security_group_ids (Set of String) The list of security groups applied to resource or their components.
  • service_account_id (String) Service account which linked to the resource.
  • stale_exec_timeout_mode (String) The timeout to automatically stop stale executions. The following modes can be used:
  • ONE_HOUR: Setting to automatically stop stale execution after one hour with low consumption.
  • THREE_HOURS: Setting to automatically stop stale execution after three hours with low consumption.
  • NO_TIMEOUT: Setting to never automatically stop stale executions.
  • subnet_id (String) ID of the subnet where the DataProcessing cluster resides. Currently only subnets created in the availability zone ru-central1-a are supported.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

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_datasphere_project.<resource Name> <resource Id>
terraform import yandex_datasphere_project.my-project ...

Was the article helpful?

Previous
datasphere_community_iam_binding
Next
datasphere_project_iam_binding
© 2025 Direct Cursus Technology L.L.C.