Skip to main content
Product Description Cloud Databases
Last update:

Product Description Cloud Databases

Cloud Databases is a service for deploying and managing high-performance and fault-tolerant clusters of supported databases in the cloud.

You can work with cloud databases in dashboard, via API and Terraform.

The product supports user types and roles.

Supported cloud databases


An open source database. Focused on speed and extensibility — you can connect any external data sources, create new data types and functions

PostgreSQL for 1C

PostgreSQL version with necessary extensions for efficient work with 1C:Enterprise

PostgreSQL TimescaleDB

PostgreSQL version with TimescaleDB extension, which can be used for storing time series

MySQL semi-sync

Open-source relational database management system, easily managed and scalable. Suitable for most data manipulation tasks

MySQL sync

An open source MySQL solution. Powered by Percona Server for MySQL with XtraDB storage subsystem


NoSQL class in-memory database management system. Can work as a database and queuing system


An open source distributed system for message delivery, storage and processing. Can work as a data bus for Cloud Native applications

How cloud databases work

Managed databases are deployed in a cluster. A cluster is one or more database servers (nodes) between which replication is configured. The cluster nodes run on Selectel's cloud platform computing resources.

Cloud databases support monitoring, backup, and scaling-up of the cluster. You can increase the fault-tolerance of the cluster and configure replication between nodes.

Database-settings when creating a cluster are selected by default and depend on the cluster configuration and database version. You can change them if necessary.

Configuring the networks of a cloud database depends on the specifics of the infrastructure in which the cloud database is embedded.


In cloud databases, you can monitor the status of the cluster in the dashboard:

  • View information about cluster node utilization and database load in the form of graphs in the control panel;
  • watch the status of the cluster;
  • receive notifications when the disk is full.

Cluster and database node metrics can also be exported in Prometheus format.

More information about monitoring in instructions for PostgreSQL, PostgreSQL for 1C, PostgreSQL TimescaleDB, MySQL sync, MySQL semi-sync, Redis and Kafka.


In cloud databases, the cluster is backed up automatically using WAL-G. All databases except Redis are Point-in-Time Recovery. The frequency of backups depends on the selected database.

Backups are stored in Selectel Object Storage isolated from other users' backups. Backups cannot be unloaded. Automatic backups cannot be disabled.

More information about backups in the instructions for PostgreSQL, PostgreSQL for 1C, PostgreSQL TimescaleDB, MySQL sync, MySQL semi-sync, Redis.


A cloud database cluster can be scaled — for example, increase vCPU and RAM to improve cluster performance. You can also change a fixed node configuration to an arbitrary configuration or an arbitrary configuration to a fixed configuration, but only with more disk space.

The process of changing the configuration depends on the availability of replicas. The configuration change time depends on the amount of data in the cluster.

More information about scaling in instructions for PostgreSQL, PostgreSQL for 1C, PostgreSQL TimescaleDB, MySQL sync, MySQL semi-sync, Redis, and Kafka.

Fault tolerance and replication

By default, a cluster consists of a single master node, the master node. When connected to a master node, all operations are available: read (SELECT) and write (INSERT, UPDATE, DELETE, and others). To provide cluster fault tolerance, add replicas — full copies of the master node. They are only available for reading data (SELECT). If the master node is unavailable, the replicas will take over its role and the cluster will operate normally. They can also be used to reduce the load on the master node during active reading.

Read more about fault tolerance in the instructions for PostgreSQL, PostgreSQL for 1C, PostgreSQL TimescaleDB, MySQL sync, MySQL semi-sync, Redis.

Cloud database settings

Database settings affect the performance of the database cluster. When you create a database cluster, the values for all settings are set automatically. The values are chosen to ensure high cluster performance and vary depending on the cluster configuration and database version.

If the automatic values are not suitable for your tasks, for all cloud databases except Redis, you can set your values when creating a cluster or change the settings in an already created cluster.

More information about cloud database settings in the instructions for PostgreSQL, PostgreSQL for 1C, PostgreSQL TimescaleDB, MySQL sync, MySQL semi-sync and Kafka.


When creating a cloud database cluster, it is necessary to consider the specifics of the infrastructure in which the cloud database is embedded — whether the cluster nodes need to be accessed from the Internet and whether network connectivity with other Selectel services is required.

The cluster can be connected:

  • to a private subnet — a subnet with no access from the Internet;
  • public subnet — all addresses on the public subnet are accessible from the Internet.

Once a cluster is created, the subnet cannot be changed.

For more information about creating network connectivity between a Selectel dedicated server and a cloud database cluster, see the instructions for PostgreSQL, [PostgreSQL for 1C](/cloud/managed-databases/postgresql-for-1c/create-network-to-dedicated-server. mdx), PostgreSQL TimescaleDB, PostgreSQL TimescaleDB, MySQL sync, MySQL semi-sync, Redis, and Kafka.

Areas of responsibility

Selectel provides

  • hardware selection for high DBMS performance;
  • installing an operating system;
  • installation and optimal configuration of the DBMS;
  • updating and maintenance of the operating system and service software;
  • Cluster reliability and fault tolerance — when you build a fault-tolerant cluster, we provide failover in the event of a failure;
  • Configuring and maintaining the service network for cluster replicas;
  • Backup — automatic creation and storage of copies;
  • cluster status monitoring system in the control panel;
  • secure data storage and protection against theft and leakage;
  • compliance with the requirements of 152-FZ;
  • Availability of resources to scale the cluster if you initiate scaling;
  • technical support.

The user provides

  • correct connection to the database;
  • optimality of writing database queries;
  • the schema and structure of the data in the database;
  • initiating cluster scaling.

If you need help with database administration, order admin services.