[Yandex Cloud documentation](../../index.md) > [Tutorials](../index.md) > Application solutions > 1C > Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster # Creating a cluster of 1C:Enterprise Linux servers with a Managed Service for PostgreSQL cluster In Yandex Cloud, you can create a Yandex Managed Service for PostgreSQL cluster optimized for 1C:Enterprise. Your new 1C:Enterprise infrastructure will consist of a 1C working server, a 1C license server, and a [Managed Service for PostgreSQL cluster](../../managed-postgresql/concepts/index.md). 1C servers will be running [CentOS 7](https://yandex.cloud/en/marketplace/products/yc/centos-7) with no internet access. The cluster will be accessed via an encrypted [OpenVPN server connection](../routing/openvpn.md). To configure a 1C cluster and make sure the created infrastructure works properly, your local computer running Windows (outside Yandex Cloud) must have the 1C: Enterprise client and the 1C administration console installed. The process of creating the 1C:Enterprise infrastructure described in this guide was tested in 1C version `8.3.25`. {% note info %} To use 1C:Enterprise, you need a license. For more information about licenses, their installation, as well as the distributions you may need, see the [1C:Enterprise website](https://its.1c.ru/). {% endnote %} To configure a 1C:Enterprise server cluster: 1. [Get your cloud ready](#before-you-begin). 1. [Set up a VPN to access the cloud infrastructure](#setup-vpn). 1. [Create virtual machines for 1C:Enterprise servers](#create-1c-vms). 1. [Create a Managed Service for PostgreSQL cluster](#create-pg-cluster). 1. [Configure a Samba server on 1C servers](#set-up-samba). 1. [Configure 1C:Enterprise servers](#setup-1c-server). 1. [Configure a 1C server cluster and infobase](#setup-cluster). 1. [Connect to the infobase](#connect-to-infobase). If you no longer need the resources you created, [delete them](#clear-out). ## Get your cloud ready {#before-you-begin} Sign up for Yandex Cloud and create a [billing account](../../billing/concepts/billing-account.md): 1. Navigate to the [management console](https://console.yandex.cloud) and log in to Yandex Cloud or create a new account. 1. On the **[Yandex Cloud Billing](https://center.yandex.cloud/billing/accounts)** page, make sure you have a billing account linked and it has the `ACTIVE` or `TRIAL_ACTIVE` [status](../../billing/concepts/billing-account-statuses.md). If you do not have a billing account, [create one](../../billing/quickstart/index.md) and [link](../../billing/operations/pin-cloud.md) a cloud to it. If you have an active billing account, you can create or select a [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) for your infrastructure on the [cloud page](https://console.yandex.cloud/cloud). [Learn more about clouds and folders here](../../resource-manager/concepts/resources-hierarchy.md). ### Required paid resources {#paid-resources} * VM instance: use of computing resources, storage, public IP address, and OS (see [Compute Cloud pricing](../../compute/pricing.md)). * Managed Service for PostgreSQL cluster: computing resources allocated to hosts, storage and backup size (see [Managed Service for PostgreSQL pricing](../../managed-postgresql/pricing.md)). ## Set up a VPN to access the cloud infrastructure {#setup-vpn} To ensure secure access to the 1C:Enterprise infrastructure you are creating in Yandex Cloud, set up a VPN. To address this task, use [OpenVPN Access Server](https://yandex.cloud/en/marketplace/products/yc/openvpn-access-server) and its Windows client. ### Create a cloud network and subnets {#setup-network} To create a [cloud network](../../vpc/concepts/network.md) with [subnets](../../vpc/concepts/network.md#subnet) in three [availability zones](../../overview/concepts/geo-scope.md): {% list tabs group=instructions %} - Management console {#console} 1. In the [management console](https://console.yandex.cloud), go to the folder where you need to create a cloud network. 1. Navigate to **Virtual Private Cloud**. 1. In the top-right corner, click **Create network**. 1. In the **Name** field, enter `my-1c-network`. 1. Enable **Create subnets**. 1. Click **Create network**. {% endlist %} ### Configure network traffic permissions {#network-settings} [Security groups](../../vpc/concepts/security-groups.md) act as a virtual firewall for incoming and outgoing traffic. Learn more about the default security group [here](../../vpc/concepts/security-groups.md#default-security-group). To ensure proper operation of OpenVPN Access Server and the Managed Service for PostgreSQL cluster, [add](../../vpc/operations/security-group-add-rule.md) additional rules to the default security group of the `my-1c-network` cloud network: Traffic
direction | Description | Port range | Protocol | Source | CIDR blocks --- | --- | --- | --- | --- | --- Inbound | `VPN Server 443` | `443` | `TCP` | `CIDR` | `0.0.0.0/0` Inbound | `VPN Server 1194` | `1194` | `UDP` | `CIDR` | `0.0.0.0/0` Inbound | `Admin Web UI,`
`Client Web UI` | `943` | `TCP` | `CIDR` | `0.0.0.0/0` Inbound | `Managed Service for PostgreSQL` | `6432` | `TCP` | `CIDR` | `0.0.0.0/0` ### Start the VPN server {#create-vpn-server} Create a VM to serve as a gateway for VPN connections: {% list tabs group=instructions %} - Management console {#console} 1. [Reserve](../../vpc/operations/get-static-ip.md) a public IP address for your VPN server. 1. On the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) dashboard in the [management console](https://console.yandex.cloud), click ![plus](../../_assets/console-icons/plus.svg) **Create resource** and select `Virtual machine instance`. 1. Under **Boot disk image**, enter `OpenVPN Access Server` in the **Product search** field and select a public [OpenVPN Access Server](https://yandex.cloud/en/marketplace/products/yc/openvpn-access-server) image. 1. Under **Location**, select an [availability zone](../../overview/concepts/geo-scope.md), e.g., `ru-central1-b`. 1. Under **Disks and file storages**, select the `HDD` [disk type](../../compute/concepts/disk.md#disks_types) and specify its size: `20 GB`. 1. Under **Computing resources**, switch to the `Custom` tab and specify the [platform](../../compute/concepts/vm-platforms.md), number of vCPUs, and amount of RAM: * **Platform**: `Intel Ice Lake`. * **vCPU**: `2`. * **Guaranteed vCPU performance**: `100%`. * **RAM**: `2 GB`. 1. Under **Network settings**: * In the **Subnet** field, select `my-1c-network` and the subnet mapped to the selected VM availability zone. * In the **Public IP address** field, select `List` and the previously reserved public IP address from the list. When configuring a VPN server, use only a static public IP address. Dynamic IP addresses may change after the VM reboots and the connections will no longer work. * Leave the **Security groups** field blank. The [default security group](../../vpc/concepts/security-groups.md#default-security-group) will be assigned to the new VM. 1. Under **Access**, select **SSH key** and specify the VM access credentials: * In the **Login** field, enter a username, e.g., `yc-user`. Do not use `root` or other reserved usernames. To perform operations requiring superuser privileges, use the `sudo` command. * In the **SSH key** field, select the SSH key saved in your [organization user](../../organization/concepts/membership.md) profile. If there are no SSH keys in your profile or you want to add a new key: 1. Click **Add key**. 1. Enter a name for the SSH key. 1. Select one of the following: * `Enter manually`: Paste the contents of the public SSH key. You need to [create](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) an SSH key pair on your own. * `Load from file`: Upload the public part of the SSH key. You need to create an SSH key pair on your own. * `Generate key`: Automatically create an SSH key pair. When adding a new SSH key, an archive containing the key pair will be created and downloaded. In Linux or macOS-based operating systems, unpack the archive to the `/home//.ssh` directory. In Windows, unpack the archive to the `C:\Users\/.ssh` directory. You do not need additionally enter the public key in the management console. 1. Click **Add**. The system will add the SSH key to your organization user profile. If the organization has [disabled](../../organization/operations/os-login-access.md) the ability for users to add SSH keys to their profiles, the added public SSH key will only be saved in the user profile inside the newly created resource. 1. Under **General information**, specify the VM name: `vpn-server`. 1. Click **Create VM**. 1. This will open a window with the licensing model: BYOL (Bring Your Own License). Click **Create**. {% endlist %} ### Get the administrator password {#get-admin-password} The openvpn user with administrator privileges was created on the `OpenVPN` server in advance. The password is generated automatically when you create a [VM](../../compute/concepts/vm.md). Get the password in the [serial port output](../../compute/operations/vm-info/get-serial-port-output.md) or the serial console. The password will display in the following string: ```text To log in, please use the `openvpn` account with the password. ``` Where `` is the `openvpn` user password. Log in to the admin panel using the `openvpn` username and the obtained password. If you do not get the password after [launching the VPN server](#create-vpn-server) for the first time, you need to re-create the VM running [OpenVPN Access Server](https://yandex.cloud/en/marketplace/products/yc/openvpn-access-server). The password will not display when reboot. ### Activate your license {#get-license} {% note info %} If you have up to two VPN connections, use the product for free (no activation required). {% endnote %} To activate the license: 1. Create an account on [openvpn.net](https://myaccount.openvpn.com/signup). 1. Enter the confirmation code sent to your email address. 1. In the **Where would you like to Go?** window, select the **Remember my choice** option and select the **Access serve** product. 1. In the **Tell us more** window, select the purpose: **Business use** or **Personal use**. 1. On the **Subscriptions** tab, select the maximum number of connections in the **How many VPN connections do you need?** field and click **Create**. 1. Your subscription will be displayed on the screen: **Subscription 1**. 1. To copy the activation key, click **Copy Key** under **Subscription Key**. Wait until the VM status changes to `RUNNING` and enter the activation key in the admin panel at `https:///admin/`. You can look up the VM's public IP address in the [management console](https://console.yandex.cloud) by checking the **Public IPv4 address** field under **Network** on the VM page. ### Create an OpenVPN user {#configure-openvpn} OpenVPN Access Server provides two web interfaces: 1. **Client Web UI** at `https:///`. This interface is used by regular users to download client applications and configuration profiles. 1. **Admin Web UI** at `https:///admin/`. This interface is used to configure the server. {% note info %} By default, the server has a self-signed certificate installed. If you need to replace this certificate, follow the steps described [here](https://openvpn.net/vpn-server-resources/installing-a-valid-ssl-web-certificate-in-access-server/). {% endnote %} To create a user, log in to the admin panel: 1. In the browser, open a URL, such as `https:///admin/`. 1. Enter the `openvpn` username and password (to learn how to get the admin password, see [this section](#get-admin-password)). 1. Read the license agreement of click **Agree**. This will open the home screen of the OpenVPN admin panel. 1. Go to the **User management** tab and select **User permissions**. 1. In the user list, enter a username for the new user in the **New Username** field, e.g., `test-user`. 1. Click the pencil icon in the **More Settings** column and enter a password for the new user in the **Password** field. 1. Click **Save settings**. 1. Click **Update running server**. ### Connect to the VPN {#test-vpn} In the admin panel, you can download the [OpenVPN Connect](https://openvpn.net/vpn-client/) client for Windows, Linux, MacOS, Android, and iOS. As this guide covers configuring the 1C:Enterprise client in the Windows environment, download and install the OpenVPN client for Windows on your local computer: 1. Download the installation distribution: * In your browser, open the user panel at `https:///`. * Sign in using the `test-user` username and password. * Download OpenVPN Connect version 2 or 3 by clicking the Windows icon. 1. Install and run OpenVPN Connect. 1. A VPN connection will turn on automatically if auto-login is enabled in the user profile. You can import a new configuration profile into the application by specifying `https:///` or selecting a profile file. ## Create virtual machines for 1C:Enterprise servers {#create-1c-vms} The 1C:Enterprise license must be installed on a separate server for changes to the configurations of other 1C servers to have no effect on the installed license. At this stage, you will create two virtual machines: one will serve as the 1C:Enterprise server and the other, as the licensing server. Create a VM for the 1C:Enterprise server: {% list tabs group=instructions %} - Management console {#console} 1. On the [folder](../../resource-manager/concepts/resources-hierarchy.md#folder) dashboard in the [management console](https://console.yandex.cloud), click ![plus](../../_assets/console-icons/plus.svg) **Create resource** and select `Virtual machine instance`. 1. Under **Boot disk image**, enter `CentOS 7` in the **Product search** field and select a public [CentOS 7](https://yandex.cloud/en/marketplace/products/yc/centos-7) image. 1. Under **Location**, select the [availability zone](../../overview/concepts/geo-scope.md) hosting the VNP server you created earlier. 1. Under **Computing resources**, switch to the `Custom` tab and specify the [platform](../../compute/concepts/vm-platforms.md), number of vCPUs, and amount of RAM: * **Platform**: `Intel Ice Lake`. * **vCPU**: `4`. * **Guaranteed vCPU performance**: `100%`. * **RAM**: `4 GB`. 1. Under **Network settings**: * In the **Subnet** field, select `my-1c-network` and the subnet mapped to the selected VM availability zone. * In the **Public IP address** field, leave the `Auto` value to assign a random external IP address from the Yandex Cloud pool. The virtual machine will need a public IP address for software configuration. Once the software has been configured, unlink the public IP address from the VM. The OpenVPN server will then be used to access the VM. * Leave the **Security groups** field blank. The [default security group](../../vpc/concepts/security-groups.md#default-security-group) will be assigned to the new VM. 1. Under **Access**, select **SSH key** and specify the VM access credentials: * In the **Login** field, enter a username, e.g., `yc-user`. Do not use `root` or other reserved usernames. For operations requiring root privileges, use the `sudo` command. * In the **SSH key** field, select the SSH key saved in your [organization user](../../organization/concepts/membership.md) profile. If there are no SSH keys in your profile or you want to add a new key: 1. Click **Add key**. 1. Enter a name for the SSH key. 1. Select one of the following: * `Enter manually`: Paste the contents of the public SSH key. You need to [create](../../compute/operations/vm-connect/ssh.md#creating-ssh-keys) an SSH key pair on your own. * `Load from file`: Upload the public part of the SSH key. You need to create an SSH key pair on your own. * `Generate key`: Automatically create an SSH key pair. When adding a new SSH key, an archive containing the key pair will be created and downloaded. In Linux or macOS-based operating systems, unpack the archive to the `/home//.ssh` directory. In Windows, unpack the archive to the `C:\Users\/.ssh` directory. You do not need additionally enter the public key in the management console. 1. Click **Add**. The system will add the SSH key to your organization user profile. If the organization has [disabled](../../organization/operations/os-login-access.md) the ability for users to add SSH keys to their profiles, the added public SSH key will only be saved in the user profile inside the newly created resource. 1. Under **General information**, specify the VM name: `server-1c`. 1. Click **Create VM**. {% endlist %} Similarly, create a VM named `licensing-server-1c` for the licensing server using the same parameters. ## Create a Managed Service for PostgreSQL cluster {#create-pg-cluster} Yandex Cloud allows you to create Managed Service for PostgreSQL clusters optimized for 1C:Enterprise. Cluster settings may vary depending on your project requirements. To create a Managed Service for PostgreSQL cluster optimized for 1C: {% list tabs group=instructions %} - Management console {#console} 1. On the folder dashboard in the [management console](https://console.yandex.cloud), click ![plus](../../_assets/console-icons/plus.svg) **Create resource** and select **PostgreSQL cluster**. 1. Under **Basic parameters**: * In the **Cluster name** field, enter the cluster name: `1c-pg`. * From the **Version** list, select `15-1c`. 1. Under **Host class**, select `s3-c2-m8`. This configuration will be enough to health check the solution. If you expect a heavy workload on your new 1C:Enterprise database, select a higher performance class host. 1. Under **Storage size**, select `network-ssd` and set the size to `114 GB`. 1. Under **Database**, specify: * **DB name**: `1c-database`. * **Username**: `user1`. * **Password**: Password you will use to access the DB. * **Locale for sorting (LC_COLLATE)**: `ru_RU.UTF-8`. * **Charset locale (LC_CTYPE)**: `ru_RU.UTF-8`. 1. Under **Network settings**, select `my-1c-network`. Leave the **Security groups** field blank. The [default security group](../../vpc/concepts/security-groups.md#default-security-group) will be assigned to the new cluster. 1. Under **Hosts**, select different availability zones for your hosts to ensure their fault tolerance. 1. Click **Create cluster**. {% endlist %} Creating a DB cluster may take a few minutes. ## Configure a Samba server on 1C servers {#set-up-samba} 1. [Connect](../../compute/operations/vm-connect/ssh.md) to `server-1c` over SSH. 1. Install Samba, the required dependencies, and the `nano` text editor: ```bash sudo yum install nano samba samba-client samba-common ``` 1. Disable IPv6 to avoid server conflicts. * Open the `/etc/sysctl.conf` file: ```bash sudo nano /etc/sysctl.conf ``` Add the following lines to the `/etc/sysctl.conf` file: ```text net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 ``` * Open the `/etc/sysconfig/network` file: ```bash sudo nano /etc/sysconfig/network ``` Add the following lines to the `/etc/sysconfig/network` file: ```text NETWORKING_IPv6=no HOSTNAME=server-1c ``` 1. Set up Samba. To do this, open the `/etc/samba/smb.conf` configuration file: ```bash sudo nano /etc/samba/smb.conf ``` Edit the file as follows: ```text [global] workgroup = WORKGROUP server string = Samba Server%v netbios name = centos security = user map to guest = bad user dns proxy = no passdb backend = tdbsam printing = cups printcap name = cups load printers = yes cups iptions = raw security = user [files] path = /1c-files browsable = yes writable = yes guest ok = yes read only = no ``` 1. Create a shared folder and grant the required access permissions for it: ```bash sudo mkdir /1c-files sudo chmod -R 777 /1c-files ``` 1. Disable SELinux. To do this, open the `/etc/sysconfig/selinux` configuration file: ```bash sudo nano /etc/sysconfig/selinux ``` Change the value of the `SELINUX` parameter: ```text SELINUX=disabled ``` 1. Add the Samba server service to the startup script: ```bash sudo systemctl enable smb.service ``` Result: ```text Created symlink from /etc/systemd/system/multi-user.target.wants/smb.service to /usr/lib/systemd/system/smb.service. ``` 1. Restart the Samba server service: ```bash sudo systemctl restart smb.service ``` Similarly, configure the Samba server on the `licensing-server-1c` VM. ## Configure 1C:Enterprise servers {#setup-1c-server} 1. Copy the 1C:Enterprise server distribution from your local computer to the `server-1c` VM: ```bash scp @:/1c-file. ``` Where: * ``: Name of the binary distribution file. For example: `setup-full-8.3.25.1257-x86_64.run`. * ``: VM username. For example: `yc-user`. * ``: Public IP address of the VM with the 1C server. 1. [Connect](../../compute/operations/vm-connect/ssh.md) to `server-1c` over SSH. 1. Install the 1C:Enterprise server on the VM: ```bash cd /1c-files sudo ./ --mode unattended --enable-components server,ws,server_admin ``` Where `` is the name of the binary distribution file. Here is an example: `setup-full-8.3.25.1257-x86_64.run`. 1. After installation is complete, delete the distribution file by specifying the name of the binary distribution file: ```bash rm ``` 1. Start the 1C server service and add it to the startup script: ```bash sudo ln /opt/1cv8/x86_64/8.3.25.1257/srv1cv8-8.3.25.1257@.service /etc/systemd/system sudo systemctl start srv1cv8-8.3.25.1257@.services.service sudo systemctl enable srv1cv8-8.3.25.1257@.services.service ``` Result: ```text Created symlink from /etc/systemd/system/multi-user.target.wants/srv1cv8-8.3.25.1257@.services.service to /etc/systemd/system/srv1cv8-8.3.25.1257@.service. ``` The path to the 1C:Enterprise server installation files depends on the 1C platform version installed. The example shows commands to start the 1C:Enterprise `8.3.25` server service. 1. Make sure the 1C:Enterprise server service is running: ```bash systemctl status -l srv1cv8-8.3.25.1257@.services ``` Result: ```bash ● srv1cv8-8.3.25.1257@.services.service - 1C:Enterprise Server 8.3 (8.3.25.1257) (.services) Loaded: loaded (/etc/systemd/system/srv1cv8-8.3.25.1257@.service; disabled; vendor preset: disabled) Active: active (running) since Thu 2024-07-18 09:09:12 UTC; 6min ago Main PID: 16656 (ragent) CGroup: /system.slice/system-srv1cv8\x2d8.3.25.1257.slice/srv1cv8-8.3.25.1257@.services.service ├─16656 /opt/1cv8/x86_64/8.3.25.1257/ragent -d /home/usr1cv8/.1cv8/1C/1cv8 -port 1540 -regport 1541 -range 1560:1591 -seclev 0 -pingPeriod 1000 -pingTimeout 5000 ├─16670 /opt/1cv8/x86_64/8.3.25.1257/rmngr -port 1541 -host server-1c.ru-central1.internal -range 1560:1591 -d /home/usr1cv8/.1cv8/1C/1cv8/ -clstid 29361c8c-d4b8-47fd-8b53-43d8349f0e94 └─16769 /opt/1cv8/x86_64/8.3.25.1257/rphost -range 1560:1591 -reghost server-1c.ru-central1.internal -regport 1541 -pid 43049953-184b-453f-985c-604fb96300ae ``` Similarly, configure the 1C server on the `licensing-server-1c` VM. When you are done configuring both 1C servers, [detach the public IP addresses](../../compute/operations/vm-control/vm-detach-public-ip.md) from the `server-1c` and `licensing-server-1c` VMs. For further access to the 1C servers, use the OpenVPN server. ## Configure a 1C server cluster and infobase {#setup-cluster} Before getting started with 1C:Enterprise, configure the server roles and add the infobase to the cluster: 1. Start the 1C administration console on your local Windows computer with the OpenVPN client running. 1. Add the central 1C:Enterprise server to the cluster: 1. Right-click **Central 1C:Enterprise 8.3 servers** and select **Create** → **Central 1C:Enterprise 8.3 server** from the context menu that opens. In the window that opens: 1. In the **Name** field, enter the server's internal FQDN: `server-1c.ru-central1.internal`. You can look up the VM's internal FQDN in the [management console](https://console.yandex.cloud) by checking the **Internal FQDN** field on the VM page. 1. Click **OK**. You will see the local cluster in the tree on the left. 1. Add the 1C licensing server to the server cluster: 1. Expand the **Clusters** tab and select **Local cluster**. 1. Right-click **Working servers** and select **Create** → **Working server** from the context menu that opens. 1. In the **Computer** field of the window that opens, specify `licensing-server-1c.ru-central1.internal` and click **OK**. This server will be used to distribute licenses to other 1C servers. 1. Add functionality assignment requirements to `licensing-server-1c`: 1. Expand the tab of the `licensing-server-1c.ru-central1.internal` server you added, right-click **Functionality assignment requirements**, and select **Create** → **Functionality assignment requirement** from the context menu that opens. In the window that opens: * In the **Requirement object** list, select `Any requirement object`. * In the **Requirement type** list, select `Do not assign`. * Leave all other parameters as they are and click **OK**. 1. Open the **Local cluster** context menu and select **Apply functionality assignment requirements (full)** to apply the new requirement to the cluster. 1. Add another requirement for assigning functionality to the `licensing-server-1c.ru-central1.internal` server with the following parameters: * In the **Requirement object** list, select `Licensing service`. * In the **Requirement type** list, select `Assign`. * Leave all other parameters as they are and click **OK**. 1. Open the **Local cluster** context menu and select **Apply functionality assignment requirements (full)** to apply the new requirement to the cluster. 1. Add functionality assignment requirements to `server-1c`: 1. Expand the `server-1c.ru-central1.internal` server tab, right-click **Functionality assignment requirements**, and select **Create** → **Functionality assignment requirement** from the context menu that opens. In the window that opens: * In the **Requirement object** list, select `Client connection to infobase`. * In the **Requirement type** list, select `Assign`. * Leave all other parameters as they are and click **OK**. 1. Open the **Local cluster** context menu and select **Apply functionality assignment requirements (full)** to apply the new requirement to the cluster. 1. Add another requirement for assigning functionality to the `server-1c.ru-central1.internal` server with the following parameters: * In the **Requirement object** list, select `Licensing service`. * In the **Requirement type** list, select `Do not assign`. * Leave all other parameters as they are and click **OK**. 1. Open the **Local cluster** context menu and select **Apply functionality assignment requirements (full)** to apply the new requirement to the cluster. 1. Right-click **Infobases** inside the **Local cluster** section and select **Create** → **Infobase** from the context menu that opens. In the window that opens, specify the following: * **Name**: `1c-database`. * **Secure connection**: `Continuously`. * **Database server**: Your DB host address and port, e.g., `rc1b-cfazv1db********.mdb.yandexcloud.net port=6432`. To find out the host address: {% list tabs group=instructions %} - Management console {#console} * In the [management console](https://console.yandex.cloud), navigate to the folder page. * Navigate to **Managed Service for PostgreSQL**. * In the window that opens, select the `1c-pg` cluster you created earlier. * Select the **Hosts** tab in the left-hand menu. * In the **Host FQDN** field, hover over the host name (format: `rc1b-cfazv1db********`) and copy the database FQDN by clicking ![copy](../../_assets/copy.svg). The FQDN will be added to the host name, so the **Database server** field should contain a name in `rc1c-cfazv1db********.mdb.yandexcloud.net port=6432` format. {% endlist %} * **DBMS type**: `PostgreSQL`. * **Database**: Database name, `1c-database`. * **Database server user**: `user1`. * **Database user password**: User password you set when creating the cluster. * **Allow license issuing by 1C:Enterprise server**: `Yes`. * **Language (Country)**: `English (United States)`. * **Create a database if none exists**: Disabled. * **Lock execution of scheduled jobs**: Disabled. Click **OK**. ## Connect to the infobase {#connect-to-infobase} 1. Start the 1C: Enterprise client on your local Windows computer with the OpenVPN client running. 1. Click **Add**. 1. Select **Add an existing infobase to the list** and click **Next**. 1. Enter the infobase name, select **On 1C:Enterprise server**, and specify the following settings: * **Server cluster**: `server-1c.ru-central1.internal`. * **Infobase name**: `1c-database`. 1. Click **Next**. 1. Click **Ready**. The infobase should appear on the list of infobases. You can now proceed to configuring and using it. ## Delete the resources you created {#clear-out} To stop paying for the deployed infrastructure: 1. [Delete](../../compute/operations/vm-control/vm-delete.md) the `server-1c`, `licensing-server-1c`, and `vpn-server` VMs. 1. [Delete](../../managed-postgresql/operations/cluster-delete.md) the `1c-pg` cluster. 1. [Delete](../../vpc/operations/address-delete.md) the public static IP address.