1C-Bitrix on AWS: Turnkey Deployment and Optimization

We deploy 1C-Bitrix on AWS for international projects, ensuring high performance and fault tolerance. If your users are distributed worldwide and data is not subject to localization requirements, the eu-central-1 or eu-west-1 region gives ~50 ms latency from Europe and ~150 ms from Russia. The main headache is payment. We solve it through trusted resellers, taking payment administration off your hands.

Recently we deployed Bitrix24 for a company with 500 employees using CRM and portal. After migration to AWS, page load time decreased from 3 seconds to 800 ms — thanks to CloudFront (4x faster than a standard server) and Redis. Server load halved due to Auto Scaling and caching. Clients typically save 30% on infrastructure costs (avg. $2,000/month) compared to on-premise. Estimate how many resources your team will save — contact us for a free audit.

With 10+ years of AWS experience and 50+ Bitrix deployments, we deliver proven results. We'll assess your project in 1 day.

Why AWS is suitable for 1C-Bitrix?

AWS provides managed services that reduce administration and improve fault tolerance. According to 1C-Bitrix documentation, recommended stack is PHP 8.1+, MySQL 8.0, and Redis caching. CloudFront CDN speeds up page loading for users worldwide, and Auto Scaling automatically adds resources during spikes. For Russian companies with international presence, AWS is cost-effective: no reliance on local providers, and you pay only for used resources.

How does the deploying 1C-Bitrix AWS architecture look?

Recommended production scheme:

Route 53 → CloudFront → ALB → EC2 (Auto Scaling Group) → RDS MySQL (Multi-AZ)
                                 ↓
                         ElastiCache Redis, S3 (uploads)

For smaller projects, EC2 + RDS Multi-AZ + S3 + CloudFront is sufficient. Let's examine each component.

EC2 for Bitrix: instance type selection

The c6i (compute-optimized) type is preferable to t3 for PHP — no CPU credits, stable performance. Disk type: gp3 instead of gp2 — cheaper and 3000 IOPS by default.

RDS MySQL Bitrix

Create Multi-AZ RDS MySQL 8.0 for automatic failover. Connection in bitrix/.settings.php:

'connections' => [
    'value' => [
        'default' => [
            'className' => '\\Bitrix\\Main\\DB\\MysqlConnection',
            'host'      => 'bitrix-db.xxxx.eu-central-1.rds.amazonaws.com',
            'database'  => 'bitrix',
            'login'     => 'bitrix_admin',
            'password'  => 'STRONG_PASSWORD',
            'options'   => 2,
        ],
    ],
],

S3 for uploads

Create a bucket and configure an IAM policy S3 with minimal permissions (use IAM role for EC2, not access keys):

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["s3:GetObject", "s3:PutObject", "s3:DeleteObject"],
      "Resource": "arn:aws:s3:::my-bitrix-uploads/*"
    },
    {
      "Effect": "Allow",
      "Action": "s3:ListBucket",
      "Resource": "arn:aws:s3:::my-bitrix-uploads"
    }
  ]
}

CloudFront CDN Bitrix

Set up a distribution with two origins: EC2 (PHP dynamic) and S3 (for /upload/). Enable compression and HTTPS. Cache static content, not dynamic.

ElastiCache Redis Bitrix

Redis cluster for sessions and data cache. Bitrix connects via the memcached module.

AWS ACM SSL

AWS Certificate Manager provides free certificates for ALB and CloudFront.

VPC security group

All components reside in a VPC with private subnets for RDS and Redis. Security Groups restrict access: only EC2 can reach RDS (port 3306) and Redis (port 6379). EC2 only exposes ports 80/443 from ALB.

All components are configured via IaC (Terraform/CloudFormation) — reproducibility guaranteed.

How to ensure fault tolerance for Bitrix AWS infrastructure?

For high availability, use Auto Scaling Bitrix with at least two EC2 instances in different AZs, Multi-AZ RDS, and ElastiCache with a replica. ALB distributes traffic. CloudFront serves as an additional buffer during spikes. This architecture withstands the failure of an entire availability zone without losing service. SLA guarantee: 99.99%.

Optimizing 1C-Bitrix AWS deployments

We fine-tune each component for maximum performance and cost efficiency. Our process includes load testing and tuning of CloudFront, Redis, and Auto Scaling policies.

Deployment process and timelines

1. Requirements analysis — 1 day
2. Design scheme — 1–2 days
3. IaC setup — 1–2 days
4. Deployment and load testing — 1–2 days
5. Documentation handover and training — 1 day

What's included in turnkey deployment

• Architecture diagram with all components
• EC2 and RDS configuration optimized for Bitrix
• S3 and CloudFront setup with caching rules
• SSL certificates via ACM
• IAM policy with least privilege
• CloudWatch monitoring and alerts setup
• Operations manual
• 30 days of technical support after launch

We'll assess your project in 1 day. Order deployment and get a ready-made infrastructure with documentation.

Additionally, we can integrate CloudWatch monitoring and set up automatic RDS backups with 30-day retention. For critical projects, we offer Disaster Recovery in another region. Get an architecture consultation — contact us.

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.