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 ruble 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 ruble 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.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.