yandex_mdb_mongodb_database (Resource)
Written by
Updated at September 11, 2025
Manages a MongoDB Database within the Yandex Cloud. For more information, see the official documentation.
Example Usage
//
// Create a new MDB MongoDB Database.
//
resource "yandex_mdb_mongodb_database" "my_db" {
cluster_id = yandex_mdb_mongodb_cluster.my_cluster.id
name = "testdb"
}
resource "yandex_mdb_mongodb_cluster" "my_cluster" {
name = "test"
environment = "PRESTABLE"
network_id = yandex_vpc_network.foo.id
cluster_config {
version = "6.0"
}
host {
zone_id = "ru-central1-d"
subnet_id = yandex_vpc_subnet.foo.id
}
resources_mongod {
resource_preset_id = "s2.micro"
disk_type_id = "network-ssd"
disk_size = 16
}
}
// 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"]
}
Schema
Required
cluster_id(String) The ID of MongoDB Cluster.name(String) The name of the database.
Optional
timeouts(Attributes) (see below for nested schema)
Read-Only
id(String) The resource identifier.
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.
Import
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_mongodb_database.<resource Name> <cluster_id>:<database_name>
terraform import yandex_mdb_mongodb_database.my_db ...:my_db