1С-Битрикс Deployment in Yandex.Cloud

1С-Битрикс Deployment in Yandex.Cloud

After the departure of AWS and Azure, Russian companies are looking for infrastructure within the Russian Federation. Yandex.Cloud is physically located in Russia, complies with Federal Law 152-FZ, offers dollar invoicing, and provides support in Russian. But deploying Bitrix correctly is a nontrivial task. Choosing the wrong disk type, missing caching, or incorrect MySQL settings lead to performance bottlenecks. We have deployed dozens of Bitrix projects on Yandex.Cloud and know how to avoid common pitfalls. For example, one of our clients — an online store with a catalog of 200,000 products — after switching to Managed Redis reduced page generation time from 3 seconds to 0.4 seconds, i.e., 7.5 times faster.

Why Yandex.Cloud instead of foreign clouds?

The main reason is the requirements of Federal Law 152-FZ: customer data must be stored in Russia. Yandex.Cloud guarantees localization, offers dollar invoicing, and provides support in Russian. For companies working with government contracts or processing personal data, this is the only viable option. Moreover, the cost of data storage in Managed MySQL on Yandex.Cloud is 30–40% lower than in comparable AWS services with similar performance.

Which architecture to choose: VM or Managed services?

For Bitrix, there are two main options:

• Virtual machine (Compute Cloud) — closer to a classic VPS. We set up LAMP/LEMP and configure it like an ordinary server. Suitable for most projects, especially when you need full control over the environment.
• Managed services + VM — VM for PHP/nginx, Managed MySQL for the database, Managed Redis for caching, Object Storage (S3-compatible) for files. This is a product-oriented approach: Yandex handles the database and cache, so we don't spend time on backups and DBMS updates. Savings on database administration — up to 50%.

For high-load projects (over 100,000 visitors per day) — a load balancer (Application Load Balancer) + VM group (Instance Group) + Managed MySQL in HA mode. Using a load balancer increases availability by 3 times compared to a single VM.

Managed MySQL in Yandex.Cloud provides automatic backups and replication by default, as described in the official documentation. This reduces administration costs by 30–50%.

Creating the Infrastructure

Network and Security

# Create VPC network yc vpc network create --name bitrix-network # Create subnet yc vpc subnet create \ --name bitrix-subnet \ --network-name bitrix-network \ --zone ru-central1-a \ --range 10.0.1.0/24 # Security group yc vpc security-group create \ --name bitrix-sg \ --network-name bitrix-network \ --rule "direction=ingress,port=80,protocol=tcp,v4-cidrs=[0.0.0.0/0]" \ --rule "direction=ingress,port=443,protocol=tcp,v4-cidrs=[0.0.0.0/0]" \ --rule "direction=ingress,port=22,protocol=tcp,v4-cidrs=[YOUR_OFFICE_IP/32]" 

Virtual Machine

yc compute instance create \ --name bitrix-web \ --zone ru-central1-a \ --cores 4 \ --memory 8 \ --create-boot-disk image-family=ubuntu-2204-lts,size=50,type=network-ssd \ --network-interface subnet-name=bitrix-subnet,nat-ip-version=ipv4,security-group-ids=<SG_ID> \ --ssh-key ~/.ssh/id_rsa.pub 

For production, network-ssd is mandatory. network-hdd is unacceptable for Bitrix due to I/O delays, especially when working with b_iblock_element_prop_s* tables.

Software Stack on VM

Nginx + PHP-FPM + MySQL (Managed) + Redis (Managed):

# /etc/nginx/sites-available/bitrix.conf server { listen 80; server_name example.ru www.example.ru; root /var/www/bitrix; index index.php; include /etc/nginx/snippets/bitrix.conf; location ~ \.php$ { fastcgi_pass unix:/run/php/php8.1-fpm.sock; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; include fastcgi_params; } } 

Connection to Managed MySQL:

// /bitrix/.settings.php 'connections' => [ 'value' => [ 'default' => [ 'className' => '\\Bitrix\\Main\\DB\\MysqlConnection', 'host' => 'rc1a-xxxxx.mdb.yandexcloud.net:3306', 'database' => 'bitrix_db', 'login' => 'bitrix_user', 'password' => 'YOUR_PASSWORD', 'options' => [ 'ssl_ca' => '/etc/ssl/certs/YandexInternalRootCA.crt', ], ], ], ], 

The Yandex certificate is downloaded from https://storage.yandexcloud.net/cloud-certs/CA.pem. Without it, the TLS connection to Managed MySQL will not be established.

Managed Redis for Cache and Sessions

// cache via Redis 'cache' => [ 'value' => [ 'type' => [ 'class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis', 'extension' => 'redis', ], 'sid' => 'bitrix_cache', ], ], // sessions via Redis 'session' => [ 'value' => [ 'mode' => 'session.id', 'handlers' => [ 'general' => [ 'type' => 'redis', 'servers' => [ ['host' => 'c-xxxxxx.rw.mdb.yandexcloud.net', 'port' => 6380, 'tls' => true], ], ], ], ], ], 

Properly configured tagged caching allows handling load even on weak VMs. Managed Redis processes requests 5 times faster than file-based disk caching. This is especially important for product catalogs with millions of items.

How to Set Up HTTPS via Certificate Manager?

Yandex.Cloud provides free Let's Encrypt certificates through Certificate Manager. They integrate with Application Load Balancer and with direct VMs via certbot. To get a certificate, use the command:

yc certificate-manager certificate request \ --name bitrix-cert \ --domains example.ru,www.example.ru 

The certificate renews automatically, eliminating the risk of expiration.

Backup

• Managed MySQL — automatic daily backups, retention for 7 days (configurable up to 60 days).
• VM disk — snapshots via yc compute snapshot create scheduled via Cloud Functions.
• Object Storage — enable object versioning in bucket settings.

For /bitrix/ and /local/ — a separate snapshot or rsync to a dedicated bucket.

Monitoring

Yandex Monitoring collects VM metrics automatically. For PHP and Nginx monitoring, install an agent. Set up alerts for CPU > 80%, RAM > 85%, disk > 90%, HTTP 5xx > 1% of requests. This allows timely response to issues.

What Is Included in the Deployment Service

1. Audit of current infrastructure and requirements.
2. Architecture design (choice between VM and Managed services).
3. Network, security group, and DNS configuration.
4. Creation of virtual machines and managed services (MySQL, Redis, Object Storage).
5. Installation and configuration of 1С-Битрикс, including license keys.
6. Caching setup (Redis, tagged caching).
7. HTTPS via Certificate Manager.
8. Backup and monitoring configuration.
9. Performance and security testing.
10. Handover of documentation and administrator training.

Our team has extensive Bitrix experience with over 50 successful projects, including high‑load catalogs. We guarantee stable infrastructure operation and provide post‑deployment support. For an accurate cost and timeline estimate, contact our engineers — get a consultation today.

Deployment Timelines

Cost is calculated individually based on complexity and scope. If you are planning a migration or new deployment, contact us — we will assess your project and propose the optimal solution.