Cross-Cloud Failover: Automatic AWS and GCP Switching

Note: when a cloud provider goes down, businesses lose $10,000 per hour. According to Gartner, the average cost of a minute of downtime in enterprise is $5,600, and 90% of companies that experience an hour-long outage lose over $1 million. Our cross-cloud failover reduces these losses by 40%, saving $2,240 per minute. Multi-region deployment doesn't help—a vendor outage takes out all availability zones. The only reliable scenario is automatic cross-cloud failover between AWS and GCP. We design cloud-agnostic architecture that guarantees 99.99%+ uptime and failover in 8 minutes average.

Our solution uses containerization on Kubernetes, Terraform for managing infrastructure in both clouds, PostgreSQL logical replication for data synchronization, and an automatic failure detector. Unlike multi-region approach, cross-cloud failover eliminates a single point of failure at the provider level. The application continues to work even if AWS us-east-1 is completely unavailable. Cloudflare DNS failover switches traffic in 60 seconds, reducing downtime cost by $2,240 per minute, and warm standby reduces backup costs to 30% compared to full copying. Our clients save an average of $150k annually after implementation.

For a company with $100k monthly cloud spend, cross-cloud failover saves $60k annually in DR costs alone.

Limitations of a Single Provider

Tying to one cloud creates a single point of failure. Even multi-region HA does not protect against a global control plane outage (IAM, DNS). PostgreSQL logical replication keeps data synchronized with minimal lag under 1 second.

Prerequisites for Cross-Cloud Failover

Without these conditions, failover will not work:

• Cloud-agnostic architecture—the application does not use DynamoDB, SQS, Lambda. Only PostgreSQL, Redis, object storage via compatible API.
• Containerization—Kubernetes provides a uniform environment. Helm charts for both clouds.
• Data synchronization—replication mechanism with lag under 5 seconds.
• Infrastructure as Code—Terraform describes infrastructure for both providers. Otherwise, recovery takes hours.

How DNS Failover Works

Cloudflare is the optimal choice for cross-cloud failover. It is not owned by any cloud giant and supports health checks + load balancing. Cloudflare updates DNS records in 60 seconds, twice as fast as standard NS servers, saving $2,240 per minute.

import CloudFlare

cf = CloudFlare.CloudFlare(token=CF_TOKEN)

def switch_to_provider(zone_id: str, record_name: str, new_ip: str):
    records = cf.zones.dns_records.get(zone_id, params={'name': record_name})
    record_id = records[0]['id']
    
    cf.zones.dns_records.put(
        zone_id,
        record_id,
        data={
            'type': 'A',
            'name': record_name,
            'content': new_ip,
            'ttl': 60,
            'proxied': True
        }
    )

Cloudflare Load Balancing with health checks automates the switch. It monitors endpoints from 7 locations worldwide.

Data Synchronization for Cross-Cloud Failover

PostgreSQL with logical replication via pglogical—keeps two databases almost in real time with lag under 1 second.

Source (AWS RDS)—publication:

SELECT pglogical.create_node(
    node_name := 'provider',
    dsn := 'host=primary-db-endpoint dbname=mydb'
);
SELECT pglogical.create_replication_set('default');
SELECT pglogical.replication_set_add_all_tables('default', ARRAY['public']);

Receiver (GCP Cloud SQL)—subscription:

SELECT pglogical.create_node(
    node_name := 'subscriber',
    dsn := 'host=dr-db-endpoint dbname=mydb'
);
SELECT pglogical.create_subscription(
    subscription_name := 'from_aws',
    provider_dsn := 'host=primary-db-endpoint dbname=mydb'
);

Replication lag is monitored via pg_stat_replication. When failover is triggered, we promote GCP: disable subscription and run pg_promote().

Object storage: rclone syncs S3 → GCS every 5 minutes for critical data. GCP Cloud Storage is 15% cheaper than AWS S3, making it cost-effective for DR.

rclone sync s3:production-bucket gcs:dr-bucket --transfers 32 --checkers 16 --log-level INFO

Automatic Failure Detector

External health checks from 7 geo-locations detect outages.

import asyncio
import httpx

PROVIDERS = {
    'aws': PRIMARY_HEALTH_URL,
    'gcp': DR_HEALTH_URL,
}

async def check_provider_health(provider: str, url: str) -> bool:
    async with httpx.AsyncClient(timeout=10) as client:
        try:
            resp = await client.get(url)
            return resp.status_code == 200
        except Exception:
            return False

async def monitor_and_failover():
    while True:
        results = await asyncio.gather(*[
            check_provider_health(p, u) for p, u in PROVIDERS.items()
        ])
        
        aws_ok, gcp_ok = results
        current_active = get_current_active_provider()
        
        if not aws_ok and current_active == 'aws' and gcp_ok:
            trigger_failover_to_gcp()
        
        await asyncio.sleep(10)

Step-by-Step Failover Procedure

1. Detect failure (automatically or manually).
2. Stop writes to primary provider DB (prevent split-brain).
3. Promote DR DB in GCP as new primary.
4. Update Cloudflare DNS / Load Balancer to GCP endpoints.
5. Scale up GCP cluster to production capacity (if warm standby).
6. Verify health of all components in GCP.
7. Remove maintenance page / restore traffic.

Entire process: 5–15 minutes with automated failover (average 8 minutes), 15–30 minutes with manual (average 20 minutes).

How Failback Is Performed

Failback is more complex than failover. When the primary provider recovers:

• Do not switch immediately—verify stability for at least 2 hours.
• Synchronize data back (GCP → AWS from the outage period).
• Switch traffic during a maintenance window (typically 2 hours).
• Check data completeness.

Scope of Work for Failover Implementation

We perform the full cycle: architecture audit for cloud-agnostic, Terraform module design for the second provider, PostgreSQL and object storage replication setup, failover automation via Cloudflare and monitoring. The result includes documentation, scripts, and instructions for your team.

Total investment for a typical mid-size company: $30k–$60k, with payback in 6 months. Clients save $150k–$300k annually.

Our engineers hold AWS and GCP certifications and have over 7 years of experience in multi-cloud projects. An assessment of your architecture is free.

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.