Cloud architecture for SMB: Yandex Cloud, AWS and hybrid — cost optimization, fault tolerance and backups

Clouds for Small Business: More Than Just Hosting

Small and medium-sized businesses are increasingly moving their IT infrastructure to the cloud. The reasons include avoiding capital expenditures on hardware, the need to scale quickly, and growing reliability requirements. But choosing a specific platform and architectural pattern often becomes a trade-off between budget, service availability, and familiar tools. This article is a practical guide for SMB owners, CTOs, and development leads who want to design a cloud environment that is cost-optimized, stable 24/7, and protected against data loss. We’ll look at two key providers—Yandex Cloud and AWS—show when a hybrid approach is justified, and give concrete recommendations for high availability, backup, and cost management. If you need expertise in building cloud solutions, the ESK Solutions team is ready to help—from auditing your current infrastructure to the full cycle of cloud services development and configuration.

Platform Comparison: Yandex Cloud vs. AWS for Small Projects

Both platforms offer compute, storage, managed databases, serverless, and compliance tools. But differences in pricing models, local presence, and ecosystem make the choice non-trivial.

Yandex Cloud — Advantages for Russian Businesses

• Data centers in Russia: Three availability zones within Russia, which simplifies compliance with Federal Law 152-FZ and reduces latency for users in the CIS.
• Ruble-based pricing: No currency risks, transparent billing, with post-payment and 1–3 year resource reservations available.
• Integrations with the Yandex ecosystem: Ready-made connectors with Yandex Tracker, analytics services, and speech technologies can speed up internal product launches.
• Free tier: Compute Cloud, Managed Service for PostgreSQL, and Object Storage offer limits sufficient for a prototype or staging environment.

AWS — Global Standard with a Vast Service Selection

• Global coverage: 30+ regions worldwide, critical for services with an international audience.
• Ecosystem maturity: Over 200 services, from Lightsail for simple projects to Amazon ECS/EKS and Aurora for enterprise workloads.
• Cost optimization tools: Reserved and Savings Plans offer up to 72% discounts, and Compute Optimizer automatically selects instance types.
• 12-month free tier: Includes t2.micro EC2, 5 GB S3, and 750 hours of RDS, helping you start without upfront investment.

For a small online store or SaaS service with a primarily Russian audience, Yandex Cloud is often 20–30% cheaper due to lower traffic costs and no currency revaluation. But if your product targets Europe or the US, AWS offers more tools for automation and global load balancing. Regardless of your choice, at ESK Solutions we design an architecture tailored to your business context—connect with our web development on cloud stacks or comprehensive enhancement of existing systems.

Hybrid Architecture: When Your Own Server and the Cloud Work Together

Hybrid does not necessarily mean a complex “patchwork” environment. It is often a rational way to keep sensitive data on-premise while offloading peak loads and disaster recovery to the public cloud.

When Hybrid Is Justified

• Legacy systems: Part of the business logic still lives on your own servers or in colocation, and moving everything to the cloud abruptly could block operations.
• Unstable internet connection: A hybrid model lets you handle critical operations locally while using the cloud for backup and burst scenarios.
• Security requirements: Databases with personal data or trade secrets stay in an isolated environment, while the frontend and API are hosted in Yandex Cloud / AWS.
• Already purchased equipment: Smart utilization of existing capacity combined with cloud scale-out reduces total cost of ownership.

Practical Implementation

The setup typically includes VPN/Direct Connect between the on-premises network and the cloud, a unified orchestration layer (Kubernetes clusters on bare-metal plus cloud nodes), and a centralized monitoring system. Yandex Cloud offers Interconnect for direct connection to data centers, while AWS offers Direct Connect. In both cases, we help configure a turnkey hybrid infrastructure as part of our cloud services development service.

Ensuring High Availability (HA) in the Cloud: A Practical Minimum for SMBs

Fault tolerance does not always require expensive distributed clusters. For most SMBs, it's enough to withstand downtime within SLA 99.9% and avoid losing session data.

Multi-Zone Deployment

Place virtual machines or containers in at least two availability zones within a single region. In Yandex Cloud, these are zones ru-central1-a, b, c. This approach protects against the failure of an entire data center zone and does not require geographic replication.

Auto Scaling and Load Balancing

• Application Load Balancer (AWS ALB / Yandex ALB) distributes traffic across healthy instances and performs health checks every 5–10 seconds.
• Auto Scaling Group (ASG) / Instance Group maintains a specified number of machines: if one fails, it replaces it with a new one, and adds capacity when load increases.
• Stateless architecture: sessions are offloaded to Redis (Managed Service for Redis / ElastiCache), files to S3 / Object Storage, which simplifies instance replacement without data loss.

Disaster Recovery for Non-Critical Systems

Cold standby is sufficient: periodic copying of machine images and databases to a remote region (second Yandex Cloud region or AWS cross-region snapshot copy). Recovery Time Objective (RTO) of about 1–4 hours is acceptable for most internal services, and costs are tens of times lower than hot standby.

Data Backup and Recovery: Strategies Without Unnecessary Complexity

Backups are an essential part of security. But for SMBs, it's critical to find a balance between frequency, retention depth, and cost.

Three-Tier Backup Model

• Daily snapshots of databases and file stores: Built-in mechanisms (RDS Automated Backups, Yandex Managed Service for PostgreSQL backup) with 7–14 day retention.
• Weekly full copies to cold storage: Export to S3 Glacier Deep Archive / Yandex Object Storage cold class. Storage cost is minimal, recovery is slower, but acceptable for disaster scenarios.
• Off-site replication: Cross-cloud copying of critical data from Yandex Cloud to AWS S3 or vice versa to protect against a single account compromise.

Script-Free Tools

AWS Backup and Yandex Cloud Backup automate the creation of snapshots of volumes, instances, and managed services on a schedule. For multi-cloud scenarios, you can use cloud functions (Lambda / Cloud Functions) that, on a cron schedule, dump the database and upload it to another provider's object storage. When building SaaS solutions, it's also important to back up metadata and user settings; we implement such policies as part of our SaaS application development service.

Optimizing Cloud Infrastructure Costs: 7 Proactive Tips

Without control, your cloud bill grows faster than revenue. Apply these measures to keep costs within budget without degrading performance.

1. Switch to Reserved and Spot Instances

For workloads with intermittent characteristics (development, testing, predictable batch jobs), use Preemptible VMs in Yandex Cloud or Spot Instances in AWS. Savings can reach 60–80%. It is important to wrap them in a fault-tolerant Auto Scaling Group so that when capacity is revoked, a replacement is instantly spun up.

2. Choose the Right Virtual Machine Family

Don't overpay for vCPUs if your task is memory-bound, and vice versa. AWS offers general-purpose (M), compute-optimized (C), and memory-optimized (R) families, while Yandex Cloud offers similar Intel and AMD lines. Periodic usage analysis via CloudWatch / Yandex Monitoring identifies idle resources and suggests where to downsize configurations.

3. Use Savings Plans / Committed Use

Commit to a consumption volume for 1–3 years in exchange for a discount of up to 50% (AWS Compute Savings Plan) or 30% (Yandex Cloud Reserved Instances). Even a small SMB can reserve one or two instances for a database and a stable application.

4. Eliminating Zombie Resources

Make sure you are not paying for forgotten Elastic IPs, unnecessary snapshots, old AMIs/images, and unused load balancers. Implement a monthly cleanup procedure using CLI scripts or Infrastructure as Code.

5. Data Storage Optimization

Set up lifecycle policies for S3 / Object Storage: transition from Standard to Infrequent Access after 30 days, to Glacier/Cold after 90. For databases, use low IOPS storage types where performance is not critical (e.g., gp2 instead of io1).

6. Traffic Control

Outbound internet traffic is one of the major hidden cost items. Connect a CDN (CloudFront / Yandex CDN) to cache static content, compress API responses, and use VPC endpoints within the cloud to eliminate inter-AZ traffic charges where possible.

7. Financial Transparency via Tags

Tag all resources with 'Project', 'Environment', 'Owner'. Set up AWS Budget Alerts / Yandex Cloud budgets that send notifications when approaching the limit. This turns cloud costs from a black box into a manageable KPI.

We implement these practices during audits and cloud environment builds. If your business is growing and it's time to move infrastructure onto a managed foundation, contact ESK Solutions specialists — we ensure migration with no downtime and subsequent 24/7 support. We also provide ready-made solutions for internal automation, such as CRM system development and corporate portal development, deployed in your cloud.

Frequently Asked Questions

Can I completely abandon my own servers and move entirely to Yandex Cloud?
Yes, this is feasible for most SMBs. It's important to plan the migration of legacy services, set up a VPN to the office, and conduct load testing. Our team assists with end-to-end migration as part of the cloud services development service.

What is the minimum cloud budget for an online store with 5,000 visitors per day?
Approximately from 8,000 to 15,000 RUB per month on Yandex Cloud (2 virtual machines, managed PostgreSQL, Object Storage) with proper utilization of reserved instances. AWS would cost $100–200 depending on region and database query intensity.

What should I do if data needs to be stored only within the territory of the Russian Federation?
Choose Yandex Cloud with resources in the ru-central1 zones. For hybrid scenarios — place databases in the Russian cloud, while frontend and static content can be kept in AWS, provided personal data does not leave the perimeter.

Are the built-in backups of managed services sufficient, or are additional solutions needed?
Built-in backups are usually sufficient for recovery from logical errors. For protection against accidental account deletion or compromise, we recommend a minimal offsite solution — daily export of a dump to an external object storage of another provider.