- Home
- Skills
- DevOps & Cloud
- Multi Region Failover Simulator
Works with the AI Agents you already use
Multi Region Failover Simulator
Design and simulate active-active or active-passive cloud failover architectures with database replication.
$15
Multi Region Failover Simulator
Example session with this skill installed
Design an active-passive multi-region failover for a Next.js app on AWS using Aurora. I need a 15-minute RTO and 5-minute RPO. Primary is us-east-1, secondary is us-west-2.
- Read your context and instructions
- Compiled the multi region failover
I have designed a multi-region failover architecture for your Aurora-backed application, focusing on meeting your 15-minute RTO and 5-minute RPO targets.
Multi-Region Failover Architecture: us-east-1 to us-west-2
| Component | Primary (us-east-1) | Secondary (us-west-2) | Configuration |
|---|---|---|---|
| Database | Aurora MySQL (Writer) | Aurora Global (Read Replica) | Asynchronous replication with <1 min lag |
| Compute | ECS Fargate Service | ECS Fargate (Scaled to 0) | Auto-scaling group triggers on failover |
| Traffic | Route 53 Primary | Route 53 Secondary | Failover routing policy with health checks |
| Storage | S3 Standard | S3 Cross-Region Replication | Versioning enabled for RPO integrity |
Failover Execution Runbook
Detection Phase: Route 53 Health Checks monitor the /health endpoint. If 3 consecutive checks fail (30s interval), the primary DNS record is marked unhealthy.
2.
Database Promotion: Invoke aws rds promote-read-replica-db-cluster for the us-west-2 cluster. This converts the global secondary to a standalone regional cluster.
3. Compute Scaling: Update the ECS Service desired count in us-west-2 from 0 to the production baseline.
4.
DNS Propagation: Route 53 shifts traffic to the us-west-2 Alias record once the health check fails and the TTL (set to 60s) expires.
5.
Split-Brain Prevention: Revoke IAM permissions for the us-east-1 database writer immediately to prevent stale writes if the region partially recovers.
Next steps
- Review the
references/technical-guide.mdfor specific Aurora Global Database promotion CLI syntax. - Add the health check endpoint to your application code to support Route 53 monitoring.
- Define the
terraformorcloudformationtemplates for the us-west-2 cold standby compute resources.
Connects securely to your tools. The creator never sees your data.
About this skill
Single-region deployments are a ticking clock for an outage. When a regional cloud failure occurs, developers often find their disaster recovery plans are either non-existent or lack the necessary detail to handle database replication lag and DNS propagation delays. This skill forces architectural rigor into your high-availability planning.
What it does
- Architect Multi-Region Flows designs active-active or active-passive topologies tailored to specific availability needs.
- Data Replication Strategy defines cross-region sync for AWS Aurora, DynamoDB Global Tables, or GCP Spanner.
- DNS Routing Policy maps out Route 53 or Cloudflare health checks and latency-based routing logic.
- Failover Runbook Generation creates step-by-step execution guides for manual or automated recovery.
- Split-Brain Prevention implements mechanisms to ensure data integrity during regional partition events.
How it works
- Define Objectives by analyzing your current topology and establishing target RTO and RPO metrics.
- Select Replication Mode based on whether the application requires synchronous or asynchronous cross-region data sync.
- Configure Routing Logic to determine how traffic shifts during a regional health check failure.
- Generate Runbooks that provide the exact commands and checks needed to promote a secondary region.
Frameworks & tools
Specific patterns for AWS (Aurora, Route 53, DynamoDB), GCP (Spanner, Cloud Load Balancing), and Cloudflare.
Why this beats prompting it yourself
Generic prompts often ignore the nuance of database replication lag and the "split-brain" risks inherent in automated failover. This skill uses a deterministic workflow to ensure every DR plan addresses traffic routing and data consistency simultaneously.
Use cases
- Designing a 99.99% available API across AWS us-east-1 and us-west-2.
- Creating a recovery runbook for an Aurora Global Database promotion.
- Simulating a regional DNS failover to test latency-based routing.
- Auditing existing infrastructure for single-points-of-failure in the networking layer.
Known limitations
Architectural synthesis and runbook authoring only. It does not perform active infrastructure modifications or execute CLI commands against live cloud providers.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Architectural synthesis and runbook authoring only. Does not modify live infrastructure or execute cloud CLI commands. Restricted to workspace file analysis.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
- Software
- Zero global installationorelevated privileges required.
File System Read/Write (strictly scoped to current project workspace `./`).
Permissions
Target Use Cases: - Design a multi-region disaster recovery plan for our web application. - Architect active-passive database failover with Route 53. - Create an SRE runbook for cross-region cloud failover.