Discuss with expertTry it for free
© 2026 Direct Cursus Technology L.L.C.

Using a Yandex Managed Service for Valkey™ cluster as a cache storage for 1C-Bitrix: Site Management

Written by
View in Markdown

You can use a Yandex Managed Service for Valkey™ cluster as an external cache storage for a website on 1C-Bitrix: Site Management.

To set up caching:

  1. Set up your infrastructure.
  2. Configure 1C-Bitrix: Website Management.
  3. Check the result.

If you no longer need the resources you created, delete them.

Getting started

Sign up for Yandex Cloud and create a billing account:

  1. Navigate to the management console and log in to Yandex Cloud or create a new account.
  2. On the Yandex Cloud Billing page, make sure you have a billing account linked and it has the ACTIVE or TRIAL_ACTIVE status. If you do not have a billing account, create one and link a cloud to it.

If you have an active billing account, you can create or select a folder for your infrastructure on the cloud page.

Learn more about clouds and folders here.

This tutorial uses the trial version of 1C-Bitrix with a 30-day trial period. You can check the cost of the product software versions on the 1C-Bitrix official website.

Set up your infrastructure

  1. Create a network named network-1c with the Create subnets option disabled.

  2. In network-1c, create a subnet with the following settings:

    • Name: subnet-a.
    • Availability zone: ru-central1-a.
    • CIDR: 192.168.0.0/24.

  3. In network-1c, create security groups:

    1. Named bitrix-sg, for the VM in the cloud. Set the following rules for this security group:

      Traffic
      direction      		 Description Port range Protocol Source /
      Destination name      		 IPv4 CIDR
      Outbound ANY All Any Prefix 0.0.0.0/0
      Inbound HTTP 80 TCP Prefix 0.0.0.0/0
      Inbound EXT-HTTPS 443 TCP Prefix 0.0.0.0/0
      Inbound SSH 22 TCP Prefix 0.0.0.0/0

    2. Named valkey-sg, for the Yandex Managed Service for Valkey™ cluster. Set the following rules for this security group:

      Traffic
      direction      		 Description Port range Protocol Source /
      Destination name      		 IPv4 CIDR
      Outbound ANY All Any Prefix 0.0.0.0/0
      Inbound EXT-HTTPS 6379 TCP Prefix 0.0.0.0/0

  4. Create a virtual machine with the following configuration in Compute Cloud:

    • Under Boot disk image, select a 1C-Bitrix image.

    • Under Network settings, set the following settings:

      • Subnet: network-1c and subnet-a.
      • Public IP address: Auto.
      • Security groups: bitrix-sg.
      • Internal IPv4 address: Auto.

  5. Connect to the VM over SSH and install the dependencies:

    sudo yum install php php-mcrypt php-cli php-gd php-curl php-mysql php-ldap php-zip php-fileinfo && \
sudo yum install http://rpms.remirepo.net/enterprise/remi-release-7.rpm && \
sudo yum install yum-utils && \
sudo yum-config-manager --enable remi-php74 && \
sudo yum update && \
php -v

    The last command will show the PHP version installed on the VM. For 1C-Bitrix to run correctly, update the PHP version to 7.4 or higher.

  6. Install 1C-Bitrix: Site Management on the VM. Do it by going to http://<VM_public_IP_address>/ in your browser and following the installer instructions.

  7. Create a test website on 1C-Bitrix.

  8. Create a Yandex Managed Service for Valkey™ cluster with the following configuration:

    • Valkey version: 9.1.
    • Persistence: On replicas.
    • Network settings: network-1c as the network and valkey-sg as the security group.
    • DBMS settings:
      • Password: default.
      • Configure → Maxmemory policy: ALLKEYS LRU. This setting will allow Valkey™ to delete the oldest keys when running out of memory.
    • Access from WebSQL: Enabled.

  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. Instead of manually creating the provider configuration file, you can download it.

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

  5. Download the yc-valkey-as-1c-cache-storage.tf configuration file to the same working directory.

    This file describes:

    • Network.

    • Subnets.

    • Security groups.

    • Yandex Managed Service for Valkey™ cluster.

    • Virtual machine with public internet access and preinstalled 1C-Bitrix: Site Management.

    • Settings for 1C-Bitrix: Site Management.

      Note

      Specific 1C-Bitrix settings may vary depending on your custom implementation. You can find cache configuration examples in the product documentation.

  6. In yc-valkey-as-1c-cache-storage.tf, specify the value for the valkey_password variable, i.e., the Yandex Managed Service for Valkey™ cluster user password.

  7. Validate your Terraform configuration using this command:

    terraform validate

    Terraform will display any configuration errors detected in your files.

  8. Create the required infrastructure:

    1. Run this command to view the intended 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.

After you create the resources, the terminal will display the following connection settings:

  • valkey_endpoint: Endpoint for connection to the Yandex Managed Service for Valkey™ cluster.
  • bitrix_vm_public_ip: Public IP address of the VM running 1C-Bitrix: Site Management.

Configure 1C-Bitrix

  1. Connect to the VM running 1C-Bitrix over SSH.

  2. Navigate to the website folder and open the additional settings file named bitrix/.settings_extra.php.

  3. Specify Valkey™ as the caching option and the Yandex Managed Service for Valkey™ cluster address:

    <?php
return [
    'cache' => [
        'value' => [
            'type' => [
                'class_name' => '\Bitrix\Main\Data\CacheEngineRedis',
            ],
            'redis' => [
                'servers' => [
                    [
                        'host' => 'c-<cluster_ID>.rw.mdb.yandexcloud.net',
                        'port' => 6379,
                    ],
                ],
                'serializer' => \Redis::SERIALIZER_IGATBINARY ?? null,
            ],
        ],
        'readonly' => true,
    ],
];

    You can get the cluster ID with the list of clusters in the folder.

    Note

    Specific 1C-Bitrix settings may vary depending on your custom implementation. You can find cache configuration examples in the product documentation.

1C-Bitrix: Site Management is configured when you create the VM. No additional setup is required.

Check the result

  1. Authenticate to your website and navigate to the control panel.

  2. Open Settings → Productivity settings → Productivity panel.

  3. On the Bitrix tab, make sure that caching is enabled with Valkey™ as storage.

  4. Make sure data actually ends up in the cluster:

    1. In the management console, select the folder containing the cluster.
    2. Navigate to Yandex Managed Service for Valkey™.
    3. Click the name of your cluster and select the Monitoring tab. The page that opens will display performance charts for the cluster.
    4. Make sure that clients have appeared, stored data and traffic are growing, and there is disk write activity on replicas due to enabled persistence.

Delete the resources you created

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

  1. Delete the Yandex Managed Service for Valkey™ cluster.
  2. Delete the VM.
  3. If you reserved public static IP addresses, release and delete them.

  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.

Previous
Distributed locks for 1C:Enterprise in a Yandex Managed Service for Valkey™ cluster
Next
Loading data from Object Storage to Managed Service for YDB with Data Transfer