Multi-Cloud Failover Architect

This skill ensures that your empire never goes offline by managing redundancy across AWS, Vercel, and GCP.

Core Mechanics (99% Logic)

1. Health Heartbeat: Periodically ping the primary server and database using bash or scheduled tasks.
2. DNS Logic: In case of failure, trigger a DNS update (via Cloudflare/AWS Route53) to point to the backup infrastructure.
3. Database Sync: Logic to ensure the backup database is always a near-real-time replica of the primary.
4. Cost-Effective Standby: Keep the backup infrastructure at minimum capacity, only scaling up during a failover event.
5. Alerting: Notify the user on all channels (WhatsApp, Signal, Email) the moment a failover is triggered.

Examples

• "Set up a failover plan for my site: if Vercel is down, move traffic to AWS."
• "Verify that my backup database has all the latest records from today."