Cloud Cost Optimization: Reduce Cloud Bills by 30–50% Without Losing Performance

Your cloud bills are growing faster than your business — that's normal if you don't manage costs. Typical picture: dev environments run 24/7, instances stay oversized "just in case", unused EBS volumes and snapshots date back years. An infrastructure audit typically uncovers 20–40% waste without any performance hit. Cloud cost optimization is our specialty: we audit cloud infrastructure, right-size instances, and apply Reserved Instances and Savings Plans. Over the past years we have completed more than 100 projects, with average savings of 32% — for a mid-sized business that means $2000–$5000 per month.

The Problems We Solve

The main driver of overspend is lack of regular audit and automation. Engineers create resources for peak load, leaving temporary resources behind. Dev environments often mirror production, even though they are needed only 8 hours a day. Storage classes are never changed, even when data is not accessed for months. Each of these issues individually causes 5–15% of overspend; combined they result in 30–50%. Through right-sizing, Reserved Instance purchases, and removing orphaned resources, we can quickly lower your bill.

Compute (EC2 / GCE / VM)

Compute is the largest cost category. Problems we typically find:

• Oversized instances (e.g., c5.2xlarge for a service handling 200 RPS)
• Dev/staging running nights and weekends
• Old generation instances (r4 instead of r6i)

Storage

Storage waste accumulates quietly:

• EBS volumes left after instance termination (orphaned volumes)
• Snapshots older than 90 days (often retained for years)
• S3 objects with no lifecycle policy
• Suboptimal storage class (Standard used for archives instead of Infrequent Access)

Data Transfer

Data transfer out is expensive — especially cross-AZ traffic (EC2 ↔ RDS in different AZs) and egress from the region.

Idle and Unused Resources

Load balancers with no traffic, NAT Gateways, unattached Elastic IPs.

How We Do It: Detailed Technical Approach

Our audit uses both native cloud tools and custom scripts to analyze your environment. We look at CloudWatch (or Stackdriver) metrics over a 2–4 week period to determine real utilization. Below is a typical methodology.

Right-Sizing Instances

import boto3
from datetime import datetime, timedelta

cw = boto3.client('cloudwatch')

def get_cpu_p95(instance_id: str, days: int = 14) -> float:
    response = cw.get_metric_statistics(
        Namespace='AWS/EC2',
        MetricName='CPUUtilization',
        Dimensions=[{'Name': 'InstanceId', 'Value': instance_id}],
        StartTime=datetime.now() - timedelta(days=days),
        EndTime=datetime.now(),
        Period=3600,
        Statistics=['p95']
    )
    values = [dp['p95'] for dp in response['Datapoints']]
    return max(values) if values else 0

We analyze CPU, memory, and network metrics. If CPU at P95 is below 20%, we downsize; if memory is below 30%, we downsize. Network throughput is compared with instance limits.

Case Study: $5,250 Monthly Savings on AWS

One of our clients, a SaaS provider with 50 EC2 instances and a $15,000 monthly AWS bill, was experiencing steady cost growth. We performed a two-week audit and found:

• 20% of resources were idle (dev environments, orphaned volumes, old snapshots)
• 60% of instances were overprovisioned (e.g., c5.4xlarge used at 10% CPU)
• No Savings Plans were applied to stable workloads

Our team implemented quick wins first: terminated idle resources, automated dev shutdown via Instance Scheduler, and applied S3 Intelligent-Tiering. Then we downsized 30 instances, moving from c5.4xlarge to c5.xlarge where appropriate. Finally, we purchased 3-year Compute Savings Plans for the remaining baseline. The result: monthly bill dropped from $15,000 to $9,750 — a 35% reduction ($5,250 saved per month). The client recouped our fee within the first two months.

Quick Wins (Week 1-2)

1. Remove orphaned resources: EBS volumes without attachment, unattached Elastic IPs, old snapshots.

   aws ec2 describe-volumes --filters Name=status,Values=available --query 'Volumes[*].[VolumeId,Size,CreateTime]' --output table
   

2. Enable S3 Intelligent-Tiering for large buckets — AWS automatically moves objects between storage tiers.
3. Schedule dev/staging shutdown using Lambda + CloudWatch Events or Instance Scheduler.
4. Delete old snapshots by implementing lifecycle policies for AMI and EBS snapshots.

Reserved Instances and Savings Plans

After stabilizing the baseline load, we consider purchasing:

• 1-year Compute Savings Plans: 20–30% discount, flexible (covers EC2, Fargate, Lambda)
• 3-year Reserved Instances: 40–60% discount for stable workloads
• Spot Instances: 70–90% discount for interruptible tasks (batch, CI workers)

For details, see AWS Savings Plans documentation.

Data Transfer Optimization

• Place RDS and EC2 in the same Availability Zone for non-HA instances to avoid cross-AZ charges.
• Use RDS Proxy to reduce connection count and optimize placement.
• Use S3 VPC Gateway Endpoint — traffic from S3 to EC2 via VPC endpoint is not charged as egress.

Process and Evaluation

1. Data collection (2–3 days): We gather billing data, resource inventories, and utilization metrics from your cloud console or API.
2. Audit & analysis (2–3 days): We identify orphaned resources, oversized instances, and savings opportunities.
3. Recommendation & planning (1–2 days): We present a detailed report with estimated savings and implementation roadmap.
4. Implementation (1–2 weeks): We execute quick wins, right-sizing, and purchase Savings Plans.
5. Monitoring & reporting: We set up ongoing cost monitoring and provide monthly reports.

Timelines

• Audit and analysis: 2–3 days
• Quick wins: 2–3 days
• Right-sizing plan and execution: 3–5 days
• Reserved/Savings Plans purchase: 1 day (requires 1–2 weeks of observation before purchase)

What’s Included in Our Work

• Full audit of your cloud infrastructure with detailed report
• Identification of overprovisioned and unused resources
• Right-sizing plan and Reserved Instance/Savings Plans recommendations
• Configuration of automatic dev environment shutdown
• Implementation of S3 lifecycle policies and Intelligent-Tiering
• Cost monitoring and regular reports
• Knowledge transfer and documentation for your team

Typical Audit Results

Request a cloud cost audit — we will find optimization opportunities and propose a savings plan. Contact us to get a consultation and examples of completed projects. Managing cloud costs and optimizing EC2 is an ongoing process; let us help you make it continuous and profitable.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.