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
          • mdb_sharded_postgresql_cluster
          • mdb_sharded_postgresql_database
          • mdb_sharded_postgresql_shard
          • mdb_sharded_postgresql_user

In this article:

  • Example Usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for config
  • Nested Schema for config.sharded_postgresql_config
  • Nested Schema for config.sharded_postgresql_config.coordinator
  • Nested Schema for config.sharded_postgresql_config.coordinator.resources
  • Nested Schema for config.sharded_postgresql_config.infra
  • Nested Schema for config.sharded_postgresql_config.infra.resources
  • Nested Schema for config.sharded_postgresql_config.router
  • Nested Schema for config.sharded_postgresql_config.router.resources
  • Nested Schema for config.access
  • Nested Schema for config.backup_window_start
  • Nested Schema for hosts
  • Nested Schema for maintenance_window
  • Nested Schema for timeouts
  • Import
  1. Terraform reference
  2. Resources
  3. Managed Service for Sharded PostgreSQL
  4. Resources
  5. mdb_sharded_postgresql_cluster

yandex_mdb_sharded_postgresql_cluster (Resource)

Written by
Yandex Cloud
Updated at September 18, 2025
  • Example Usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for config
    • Nested Schema for config.sharded_postgresql_config
    • Nested Schema for config.sharded_postgresql_config.coordinator
    • Nested Schema for config.sharded_postgresql_config.coordinator.resources
    • Nested Schema for config.sharded_postgresql_config.infra
    • Nested Schema for config.sharded_postgresql_config.infra.resources
    • Nested Schema for config.sharded_postgresql_config.router
    • Nested Schema for config.sharded_postgresql_config.router.resources
    • Nested Schema for config.access
    • Nested Schema for config.backup_window_start
    • Nested Schema for hosts
    • Nested Schema for maintenance_window
    • Nested Schema for timeouts
  • Import

Manages a Sharded Postgresql cluster within the Yandex Cloud.

Example UsageExample Usage

//
// Create a new MDB Sharded PostgreSQL Cluster.
//
resource "yandex_mdb_sharded_postgresql_cluster" "default" {
  name        = "test"
  environment = "PRESTABLE"
  network_id  = yandex_vpc_network.foo.id

  config = {
    backup_retain_period_days = 10
    sharded_postgresql_config = {
      common = {
        console_password = "P@ssw0rd"
        log_level = "INFO"
      }
      router = {
        resources = {
          resource_preset_id = "s2.micro"
          disk_type_id       = "network-ssd"
          disk_size          = 32
        }
        config = {
          show_notice_messages = false
          prefer_same_availability_zone = true
        }
      }
      coordinator = {
        resources = {
          resource_preset_id = "s2.micro"
          disk_type_id       = "network-ssd"
          disk_size          = 32
        }
      }
      balancer = {}
    }
  }

  hosts = {
    "router1" = {
      zone      = "ru-central1-a"
      subnet_id = yandex_vpc_subnet.foo.id
      assign_public_ip = false
      type = "ROUTER"
    }
    "router2" = {
      zone      = "ru-central1-d"
      subnet_id = yandex_vpc_subnet.foo.id
      assign_public_ip = false
      type = "ROUTER"
    }
    "coordinator" = {
      zone      = "ru-central1-d"
      subnet_id = yandex_vpc_subnet.foo.id
      assign_public_ip = false
      type = "COORDINATOR"
    }
  }
}

// Auxiliary resources
resource "yandex_vpc_network" "foo" {}

resource "yandex_vpc_subnet" "foo" {
  zone           = "ru-central1-d"
  network_id     = yandex_vpc_network.foo.id
  v4_cidr_blocks = ["10.5.0.0/24"]
}
locals {
  shards = 4
  users = {
    alice: {
      "password": "password",
      "conn_limit": 30
    },
    bob: {
      "password": "mysupercoolpassword",
      "conn_limit": 15

    }
  }
  dbs = {"testdb": "alice", "anotherdb": "bob"}

  user_shard_combinations = flatten([
    for shard in range(local.shards) : [
      for user, cfg in local.users : {
        shard = shard
        name  = user
        settings = cfg
        key   = "${shard}-${user}"
      }
    ]
  ])
  db_shard_combinations = flatten([
    for shard in range(local.shards) : [
      for db, owner in local.dbs : {
        shard = shard
        db  = db
        owner = owner
        key   = "${shard}-${db}"
        owner_key = "${shard}-${owner}"
      }
    ]
  ])
}

/****************** PostgreSQL Shards Management ******************/

resource "yandex_mdb_postgresql_cluster_v2" "shard" {
  count = local.shards

  name        = "shard${count.index}"
  environment = "PRESTABLE"
  network_id  = yandex_vpc_network.foo.id

  config {
    version = 17
    resources {
      resource_preset_id = "s2.micro"
      disk_type_id       = "network-ssd"
      disk_size          = 16
    }

    postgresql_config = {
      max_connections                = 395
      enable_parallel_hash           = true
      autovacuum_vacuum_scale_factor = 0.34
      default_transaction_isolation  = "TRANSACTION_ISOLATION_READ_COMMITTED"
      shared_preload_libraries       = "SHARED_PRELOAD_LIBRARIES_AUTO_EXPLAIN,SHARED_PRELOAD_LIBRARIES_PG_HINT_PLAN"
      max_wal_senders = 20
      shared_buffers = 2147483648
    }
  }

  hosts = {
    "first" = {
      zone      = "ru-central1-a"
      subnet_id = yandex_vpc_subnet.test-subnet-a.id
    }
    "second" = {
      zone      = "ru-central1-b"
      subnet_id = yandex_vpc_subnet.test-subnet-b.id
    }
    "third" = {
      zone      = "ru-central1-d"
      subnet_id = yandex_vpc_subnet.test-subnet-d.id
    }
  }
}

resource "yandex_mdb_postgresql_user" "shard_user" {
  for_each = { for combo in local.user_shard_combinations : combo.key => combo }

  cluster_id = yandex_mdb_postgresql_cluster_v2.shard[each.value.shard].id
  name       = "${each.value.name}"
  password   = "${each.value.settings.password}"
  conn_limit = "${each.value.settings.conn_limit}"
  settings = {
    default_transaction_isolation = "read committed"
    log_min_duration_statement    = 5000
  }
}

resource "yandex_mdb_postgresql_database" "shard_db" {
  for_each = { for combo in local.db_shard_combinations : combo.key => combo }

  cluster_id = yandex_mdb_postgresql_cluster_v2.shard[each.value.shard].id
  name       = "${each.value.db}"
  owner      = yandex_mdb_postgresql_user.shard_user[each.value.owner_key].name
  lc_collate = "en_US.UTF-8"
  lc_type    = "en_US.UTF-8"
  extension {
    name = "uuid-ossp"
  }
  extension {
    name = "xml2"
  }
}

/****************** Sharded PostgreSQL Cluster Management ******************/

resource "yandex_mdb_sharded_postgresql_cluster" "default" {
  name        = "diphantxm-full"
  environment = "PRODUCTION"
  network_id  = yandex_vpc_network.foo.id

  hosts = {
    "router2" = {
      zone      = "ru-central1-a"
      subnet_id = yandex_vpc_subnet.test-subnet-a.id
      assign_public_ip = false
      type = "ROUTER"
    }
    "router1" = {
      zone      = "ru-central1-b"
      subnet_id = yandex_vpc_subnet.test-subnet-b.id
      assign_public_ip = false
      type = "ROUTER"
    }
    "router3" = {
      zone      = "ru-central1-d"
      subnet_id = yandex_vpc_subnet.test-subnet-d.id
      assign_public_ip = false
      type = "ROUTER"
    }
  }

  config = {
    backup_retain_period_days = 10
    sharded_postgresql_config = {
        common = {
            console_password = "password"
            log_level = "INFO"
        }
        router = {
            resources = {
                resource_preset_id = "s2.micro"
                disk_type_id       = "network-ssd"
                disk_size          = 32
            }
            config = {
              show_notice_messages = false
              prefer_same_availability_zone = true
            }
        }
        balancer = {}
    }
  }
}

resource "yandex_mdb_sharded_postgresql_database" "spqr_db" {
  for_each = local.dbs

  cluster_id = yandex_mdb_sharded_postgresql_cluster.default.id
  name       = "${each.key}"
}

resource "yandex_mdb_sharded_postgresql_user" "spqr_user" {
  for_each = local.users

  cluster_id = yandex_mdb_sharded_postgresql_cluster.default.id
  name       = "${each.key}"
  password   = "${each.value.password}"
  settings = {
    connection_limit = "${each.value.conn_limit}"
    connection_retries = 5
  }
}

resource "yandex_mdb_sharded_postgresql_shard" "shard" {
  count = local.shards

	cluster_id = yandex_mdb_sharded_postgresql_cluster.default.id
	name       = "shard${count.index}"
	shard_spec = {
		mdb_postgresql = yandex_mdb_postgresql_cluster_v2.shard[count.index].id
	}
}

// Auxiliary resources
resource "yandex_vpc_network" "foo" {}

resource "yandex_vpc_subnet" "test-subnet-a" {
  zone           = "ru-central1-a"
  network_id     = yandex_vpc_network.foo.id
  v4_cidr_blocks = ["10.1.0.0/24"]
}
resource "yandex_vpc_subnet" "test-subnet-b" {
  zone           = "ru-central1-b"
  network_id     = yandex_vpc_network.foo.id
  v4_cidr_blocks = ["10.2.0.0/24"]
}
resource "yandex_vpc_subnet" "test-subnet-d" {
  zone           = "ru-central1-d"
  network_id     = yandex_vpc_network.foo.id
  v4_cidr_blocks = ["10.3.0.0/24"]
}

SchemaSchema

RequiredRequired

  • config (Attributes) Configuration of the Sharded PostgreSQL cluster. (see below for nested schema)
  • environment (String) Deployment environment of the PostgreSQL cluster.
  • hosts (Attributes Map) A host configuration of the PostgreSQL cluster. (see below for nested schema)
  • name (String) Name of the Sharded PostgreSQL cluster. Provided by the client when the cluster is created.
  • network_id (String) The VPC Network ID of subnets which resource attached to.

OptionalOptional

  • deletion_protection (Boolean) The true value means that resource is protected from accidental deletion.
  • description (String) Description of the Sharded PostgreSQL cluster.
  • folder_id (String) The folder identifier that resource belongs to. If it is not provided, the default provider folder-id is used.
  • labels (Map of String) A set of key/value label pairs which assigned to resource.
  • maintenance_window (Attributes) Maintenance policy of the PostgreSQL cluster. (see below for nested schema)
  • security_group_ids (Set of String) The list of security groups applied to resource or their components.
  • timeouts (Attributes) (see below for nested schema)

Read-OnlyRead-Only

  • id (String) The resource identifier.

Nested Schema for Nested Schema for config

Required:

  • sharded_postgresql_config (Attributes) Sharded PostgreSQL cluster configuration. (see below for nested schema)

Optional:

  • access (Attributes) Access policy to the Sharded PostgreSQL cluster. (see below for nested schema)
  • backup_retain_period_days (Number) The period in days during which backups are stored.
  • backup_window_start (Attributes) Time to start the daily backup, in the UTC timezone. (see below for nested schema)

Nested Schema for Nested Schema for config.sharded_postgresql_config

Optional:

  • balancer (Map of String) Balancer specific configuration.
  • common (Map of String) General settings for all types of hosts.
  • coordinator (Attributes) Coordinator specific configuration. (see below for nested schema)
  • infra (Attributes) (see below for nested schema)
  • router (Attributes) Router specific configuration. (see below for nested schema)

Nested Schema for Nested Schema for config.sharded_postgresql_config.coordinator

Required:

  • resources (Attributes) Resources allocated to routers of the Sharded PostgreSQL cluster. (see below for nested schema)

Optional:

  • config (Map of String) Coordinator settings.

Nested Schema for Nested Schema for config.sharded_postgresql_config.coordinator.resources

Required:

  • disk_size (Number) Size of the disk in bytes.
  • disk_type_id (String) ID of the disk type that determines the disk performance characteristics.
  • resource_preset_id (String) ID of the resource preset that determines the number of CPU cores and memory size for the host.

Nested Schema for Nested Schema for config.sharded_postgresql_config.infra

Required:

  • resources (Attributes) Resources allocated to routers of the Sharded PostgreSQL cluster. (see below for nested schema)

Optional:

  • coordinator (Map of String) Coordinator settings.
  • router (Map of String) Router settings.

Nested Schema for Nested Schema for config.sharded_postgresql_config.infra.resources

Required:

  • disk_size (Number) Size of the disk in bytes.
  • disk_type_id (String) ID of the disk type that determines the disk performance characteristics.
  • resource_preset_id (String) ID of the resource preset that determines the number of CPU cores and memory size for the host.

Nested Schema for Nested Schema for config.sharded_postgresql_config.router

Required:

  • resources (Attributes) Resources allocated to routers of the Sharded PostgreSQL cluster. (see below for nested schema)

Optional:

  • config (Map of String) Router settings.

Nested Schema for Nested Schema for config.sharded_postgresql_config.router.resources

Required:

  • disk_size (Number) Size of the disk in bytes.
  • disk_type_id (String) ID of the disk type that determines the disk performance characteristics.
  • resource_preset_id (String) ID of the resource preset that determines the number of CPU cores and memory size for the host.

Nested Schema for Nested Schema for config.access

Optional:

  • data_lens (Boolean) Allow access for Yandex DataLens.
  • data_transfer (Boolean) Allow access for DataTransfer
  • serverless (Boolean) Allow access for connection to managed databases from functions
  • web_sql (Boolean) Allow access for SQL queries in the management console

Nested Schema for Nested Schema for config.backup_window_start

Optional:

  • hours (Number) The hour at which backup will be started (UTC).
  • minutes (Number) The minute at which backup will be started (UTC).

Nested Schema for Nested Schema for hosts

Required:

  • type (String)
  • zone (String) The availability zone where the host is located.

Optional:

  • assign_public_ip (Boolean) Assign a public IP address to the host.
  • subnet_id (String) ID of the subnet where the host is located.

Read-Only:

  • fqdn (String) The fully qualified domain name of the host.

Nested Schema for Nested Schema for maintenance_window

Optional:

  • day (String) Day of the week (in DDD format). Allowed values: "MON", "TUE", "WED", "THU", "FRI", "SAT","SUN"
  • hour (Number) Hour of the day in UTC (in HH format). Allowed value is between 1 and 24.
  • type (String) Type of maintenance window. Can be either ANYTIME or WEEKLY. A day and hour of window need to be specified with weekly window.

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_mdb_sharded_postgresql_cluster.<resource Name> <resource Id>
terraform import yandex_mdb_sharded_postgresql_cluster.my_cluster ...

Was the article helpful?

Previous
mdb_sqlserver_cluster
Next
mdb_sharded_postgresql_database
© 2025 Direct Cursus Technology L.L.C.