Object Storage for 1C-Bitrix: SigV4, CORS, CDN

When integrating Yandex Object Storage with 1C-Bitrix, developers often encounter non-obvious problems: SigV4 signature incompatibility, CORS blocking file uploads from the browser, and incorrect CDN caching. A typical Bitrix store stores between 10 and 50 GB of product images in /upload/. Moving to cloud S3 storage reduces server load by 40% and speeds up catalog page loading by 2–3 times. We configure cloud storage turnkey: from creating a service account to connecting CDN. Our experience includes over 50 projects for online stores and corporate portals. We resolve these issues in 2–3 days, guaranteeing compatibility with any Bitrix components. The cost of storing 1 GB in Yandex Object Storage starts from 2 rubles per month, which is several times cheaper than a dedicated disk array. Total economy: up to 2,000 rubles per month on hosting and traffic for a typical store.

Connection Parameters

Yandex Object Storage endpoint: https://storage.yandexcloud.net. Region: ru-central1. Public URL format: https://[bucket].storage.yandexcloud.net/[key] — virtual hosted style.

In /bitrix/admin/main_cloud_storage.php specify:

• Storage type: Amazon S3 (compatible)
• Endpoint: https://storage.yandexcloud.net
• Region: ru-central1
• Access Key: static key ID from Yandex Cloud console
• Secret Key: secret key
• Bucket: bucket name

Creating a service account and keys: in Yandex Cloud console: IAM → Service Accounts → Create → assign storage.editor role on the bucket → Create static access key.

Setting Up S3-Compatible Storage

The main.cloudstorages module uses the AWS SDK PHP. When connecting to Yandex Object Storage, the SDK may default to the wrong signature version. Yandex supports only Signature Version 4 (SigV4), while the SDK for custom endpoints sometimes tries to use SigV2. Without explicitly specifying the signature, authorization fails. The fix is to add the parameter 'signature' => 'v4' to the client configuration:

$s3Client = new \Aws\S3\S3Client([
    'version'     => 'latest',
    'region'      => 'ru-central1',
    'endpoint'    => 'https://storage.yandexcloud.net',
    'signature'   => 'v4',
    'credentials' => [
        'key'    => $accessKey,
        'secret' => $secretKey,
    ],
]);

If the module interface does not allow passing this parameter, we edit the provider class (with a backup) or use inheritance. This approach has been tested on dozens of projects.

How to Fix SigV4 Signature Errors?

Official 1C-Bitrix documentation does not provide a ready-made solution. In practice, a patch to /bitrix/modules/main/lib/cloudstorages/amazon.php helps: add 'signature' => 'v4' in the client constructor. Alternatively, override the getS3Client() method in an inherited class. Source: Yandex Object Storage documentation — SigV4 is mandatory.

Configuring CORS for Uploads

When using presigned URLs for direct upload to Object Storage, browsers block requests without CORS headers. In the Yandex Cloud console, in the "CORS" section, add a rule. Follow these steps:

1. Navigate to the bucket settings in Yandex Cloud Console.
2. Open the "CORS" tab.
3. Add a new rule:

<CORSConfiguration>
  <CORSRule>
    <AllowedOrigin>https://example.com</AllowedOrigin>
    <AllowedMethod>GET</AllowedMethod>
    <AllowedMethod>PUT</AllowedMethod>
    <AllowedHeader>*</AllowedHeader>
    <MaxAgeSeconds>3600</MaxAgeSeconds>
  </CORSRule>
</CORSConfiguration>

4. Save the configuration.

Without this setting, TinyMCE and custom upload forms will throw an error. We include CORS configuration in the standard scope of work.

Lifecycle Policies for Temporary Files

Yandex Object Storage supports automatic deletion of files older than N days. This is useful for folders /upload/tmp/ and /upload/import/, which Bitrix does not clean. Example rule:

{
    "Rules": [{
        "ID": "cleanup-tmp",
        "Status": "Enabled",
        "Filter": { "Prefix": "upload/tmp/" },
        "Expiration": { "Days": 7 }
    }]
}

Configured via console or API. Space savings up to 30% per month on a typical store. For a store with 20 GB of temporary files, this saves about 600 rubles per month when stored in the cloud.

How to Set Up CDN?

Yandex Cloud CDN integrates with Object Storage in minutes: create a CDN resource with the bucket as origin, specify the CDN domain in the cloud_storage_cdn_url option. After that, Bitrix generates public URLs through the CDN, and files are served from the nearest point of presence. Parameter in code:

\Bitrix\Main\Config\Option::set('main', 'cloud_storage_cdn_url', 'https://cdn.example.com');

Writes go directly to the bucket, reads go through the CDN. For image resizes, this gives a 2–3x speedup in catalog page loading. For Russian projects, Yandex CDN offers the best latency compared to CloudFront — delays are 30% lower thanks to data centers in Moscow and St. Petersburg.

What's Included in Turnkey Setup

We perform the full cycle: creating a service account, CORS configuration, signature patch, lifecycle policies, CDN integration. We provide configuration documentation and backup of original files. We guarantee data integrity and compatibility after Bitrix updates.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.