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
| Load | Instance type | RAM | CPU |
|---|---|---|---|
| Start / Development | t3.medium | 4 GB | 2 vCPU |
| Medium traffic | c6i.xlarge | 8 GB | 4 vCPU |
| High traffic | c6i.2xlarge | 16 GB | 8 vCPU |
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
- Requirements analysis — 1 day
- Design scheme — 1–2 days
- IaC setup — 1–2 days
- Deployment and load testing — 1–2 days
- Documentation handover and training — 1 day
| Option | Components | Timeline |
|---|---|---|
| EC2 + RDS Multi-AZ + S3 | Basic production infrastructure | 2–3 days |
| + CloudFront + ElastiCache | CDN, session caching | 1–2 additional days |
| Full HA with Auto Scaling | ALB, ASG, Multi-AZ RDS, complete failover | 5–8 days |
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.