Cloud Architecture, Migration, Cost and DR Plans
Cloud architectures, migration waves, ranked cost cuts, and RTO/RPO-backed DR plans for AWS, Azure, or GCP, with tradeoffs stated.
Before & after
Same prompt, same agent — the only difference is the skill.
Cloud architecture design involves several key considerations. You'll want to think about availability zones, load balancing, database replication, and cost optimization. There are multiple approaches to achieving high availability and scalability. AWS offers many services that could help—EC2 instances, RDS, S3, CloudFront, and others. You might also consider disaster recovery, data backup strategies, and security groups. I'd be happy to help you explore different options and discuss trade-offs. What's most important to your specific use case? Are you prioritizing cost, performance, or reliability?
WELL-ARCHITECTED REVIEW FOR 10K RPS SAAS PLATFORM REGION STRATEGY → Primary: us-east-1 (largest instance selection) → Secondary: eu-west-1 (lowest latency for EU customers) → Tertiary: ap-southeast-1 (Asia-Pacific coverage) COMPUTE LAYER → EKS auto-scaling cluster (3 zones, 2-16 nodes per zone) → Target: 15-20% headroom at peak load → Pod disruption budgets for zero-downtime deployments DATA LAYER → Aurora Global Database (read replicas in secondary regions, 100ms RPO) → Read-only replica in each region for 99.99% availability → Failover time: under 30 seconds via RTO automation CACHING & EDGE → CloudFront + ElastiCache (Redis) in each region → TTL strategy: 5min static, 30sec dynamic content COST BASELINE → Compute: 8K/month | Storage: 2K/month | Data transfer: 3K/month → Reserved instances on primary region save 35% → Spot instances for non-critical batch jobs: 70% savings DISASTER RECOVERY → RTO: 5 minutes (automated failover) → RPO: 1 minute (continuous replication) → Test quarterly via backup restore drills
About this skill
Your cloud bill doubled and someone wants to switch providers. Or your DR plan has never been tested, or your new architecture is a list of services with no numbers attached. This skill turns cloud decisions into arithmetic: availability math, sizing, ranked savings, and migration payback. Every recommendation names what it costs and when to revisit it.
What it does
- Converts vague requirements into numbers: RPS, data growth, p99 latency, RTO/RPO per tier, budget, and ops headcount. It then shows the availability and sizing math behind the design.
- Triages cloud bills in the right order (waste, rightsizing, scheduling, storage, data transfer, then commitments) and ranks each fix by savings-to-effort.
- Runs a payback calculation before endorsing any cloud-to-cloud move, so "switch to GCP" is weighed against the fixes available on the current provider.
- Plans migrations per workload using the 7 Rs and builds dependency-ordered waves. Databases cut over through CDC with validation and a time-boxed rollback.
- Designs landing zones covering account structure, guardrail policies, centralized logging, SSO, and a non-overlapping IP plan.
- Picks a DR pattern per tier (backup/restore through active-active) and checks it against real restore times, quotas, DNS TTLs, and failover testing.
What you get
A decision-ready plan with the math shown: requirements table, design or migration waves, cost or payback calculations, tradeoffs with revisit triggers, risks, and ordered next steps. Quick questions get short direct answers.
Best for
Engineering leads, platform teams, and startup CTOs who are designing, migrating, or cutting the cost of workloads on AWS, Azure, or GCP and need answers they can defend to leadership.
SKILL.md preview
---
name: cloud-architecture-migration-cost-dr
description: Designs and reviews cloud architectures on AWS, Azure, and GCP using numeric requirements, availability and sizing math, and explicit tradeoffs. Plans per-workload migrations in dependency-ordered waves, ranks cost cuts by savings-to-effort with payback math, and ties DR patterns to RTO/RPO targets. Use when the user says "design the architecture for...", "review our cloud setup", "our AWS bill doubled", "should we move to GCP", "plan our migration off on-prem", "we need a DR plan", "our failover test failed", or "set up a landing zone".
---
# Cloud Architecture, Migration, Cost and DR Plans
… (sign up to view the full skill)More development skills
View all Development skills →Chaos Experiment and Game Day Planner
Plans chaos experiments and game days: hypothesis, blast radius, abort conditions, tool manifests, rollback, and post-run review.
Claude Code Cost and Latency Routing
Configure Claude Code Router with model tiers, explicit fallbacks, compatibility checks, and a cost-aware validation plan.
CI/CD Pipeline Builder with Gated Deploys
Generates CI/CD workflows from your repo's real stack: cached fast-fail checks, pinned actions, and staging-to-prod deploys with gates.
Terraform Modules and Safe Deployments
Get reusable Terraform modules, safe state migrations, explicit provider wiring, and CI gates tied to reviewed plans.