Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Yandex Managed Service for PostgreSQL
  • Getting started
    • All tutorials
    • Creating a PostgreSQL cluster for 1C
    • Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster
    • Exporting a database to Yandex Data Processing
    • Searching for cluster performance issues
    • Performance analysis and tuning
    • Setting up a connection from a Serverless Containers container
    • Delivering data to Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Delivering data to Yandex Managed Service for YDB using Yandex Data Transfer
    • Delivering data to Yandex Managed Service for Apache Kafka® using Debezium
    • PostgreSQL change data capture and delivery to YDS
    • Delivering data from Yandex Managed Service for Apache Kafka® using Yandex Data Transfer
    • Transferring data from Yandex Object Storage using Yandex Data Transfer
    • Configuring a fault-tolerant architecture in Yandex Cloud
    • Status monitoring of geographically distributed devices
    • Writing load balancer logs to PostgreSQL
    • Creating an MLFlow server for logging experiments and artifacts
    • Working with data using Query
    • Federated data queries using Query
    • Fixing string sorting issues after upgrading _glibc_
    • Writing data from a device into a database
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Required paid resources
  • Create a Managed Service for PostgreSQL cluster
  • Connect the database to 1C:Enterprise
  • PostgreSQL extensions for 1C:Enterprise support
  • Delete the resources you created
  1. Tutorials
  2. Creating a PostgreSQL cluster for 1C

Creating a PostgreSQL cluster for 1C:Enterprise

Written by
Yandex Cloud
Updated at May 5, 2025
  • Required paid resources
  • Create a Managed Service for PostgreSQL cluster
  • Connect the database to 1C:Enterprise
    • PostgreSQL extensions for 1C:Enterprise support
  • Delete the resources you created

Managed Service for PostgreSQL allows you to create fault-tolerant PostgreSQL clusters optimized for 1C:Enterprise. To this end, the service supports PostgreSQL versions 13-1c, 14-1c, 15-1c, and 16-1c with all the required extensions installed and the connection pooler configuration modified.

Warning

You can only connect 1C:Enterprise to version 13-1c, 14-1c, 15-1c, and 16-1c clusters.

Select your host class based on the number of users in your 1C:Enterprise installation. The s2.small hosts can accommodate up to 50 users at a time. We recommend using the s2.medium class if 50 or more users are going to access the database. Choose the storage size based on your expected data scope and allow for possible growth in your data volumes.

Required paid resourcesRequired paid resources

The support cost includes:

  • Managed Service for PostgreSQL cluster fee: Using computing resources allocated to hosts and disk space (see Managed Service for PostgreSQL pricing).
  • Fee for using public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).

Create a Managed Service for PostgreSQL clusterCreate a Managed Service for PostgreSQL cluster

Manually
Terraform

Create a Managed Service for PostgreSQL cluster of any suitable configuration with the following settings:

  • Environment: PRODUCTION.
  • Version: PostgreSQL version used for working with 1C:Enterprise. The names of such versions end with -1c.
  • Host class: s2.small or higher.
  • Hosts: Add at least two more hosts in different availability zones. This provides the fault tolerance of the cluster. The database is automatically replicated. To learn more, see Replication in Managed Service for PostgreSQL.
  1. If you do not have Terraform yet, install it.

  2. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

  3. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

  4. Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.

  5. Download the postgresql-1c.tf configuration file to the same working directory.

    This file describes:

    • Network.
    • Subnet.
    • Security group and rule enabling cluster connections.
    • Managed Service for PostgreSQL cluster for 1C:Enterprise with the database and user.
  6. Specify the infrastructure parameters in the postgresql-1c.tf configuration file under locals:

    • cluster_name: Cluster name.
    • pg_version: PostgreSQL version used for working with 1C:Enterprise. The names of such versions end with -1c.
    • db_name: Database name.
    • username and password: Name and user password of the database owner.
  7. Make sure the Terraform configuration files are correct using this command:

    terraform validate
    

    If there are any errors in the configuration files, Terraform will point them out.

  8. Create the required infrastructure:

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Creating a DB cluster may take a few minutes.

Connect the database to 1C:EnterpriseConnect the database to 1C:Enterprise

Add the created database as an information base to 1C:Enterprise. When adding the database, use the following parameters:

  • Secure connection: Disabled.
  • DBMS type: PostgreSQL.
  • Database server: c-<cluster_ID>.rw.mdb.yandexcloud.net port=6432.
  • Database name: Name of the database you specified when creating the cluster.
  • Database user: Username of the database owner.
  • User password: Password of the database owner.
  • Create database if none present: Disabled.

PostgreSQL extensions for 1C:Enterprise supportPostgreSQL extensions for 1C:Enterprise support

List of extensions installed in PostgreSQL 13-1c, 14-1c, 15-1c, and 16-1c clusters:

  • online_analyze

  • plantuner

  • fasttrun

  • fulleq

  • mchar

Delete the resources you createdDelete the resources you created

Delete the resources you no longer need to avoid paying for them:

Manually
Terraform

Delete the Managed Service for PostgreSQL cluster.

  1. In the terminal window, go to the directory containing the infrastructure plan.

    Warning

    Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

  2. Delete resources:

    1. Run this command:

      terraform destroy
      
    2. Confirm deleting the resources and wait for the operation to complete.

    All the resources described in the Terraform manifests will be deleted.

Was the article helpful?

Previous
All tutorials
Next
Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster
Yandex project
© 2025 Yandex.Cloud LLC