1

I have an application running in N.Virginia Region. I want to configure Regional failover such that if my N.Virgina region or application goes down, same application should come up secondary Region. Initially secondary Region should not have any resources. May be we can only have a CloudFormation template for application or an Lambda function in secondary Region which could bring up all the resources in secondary Region.

For data replication between regions, I will have snapshots of EBS copied periodically to secondary region, and will run a Read replica of RDS in secondary region. But I want, EC2, Loadbalancer, EBS and other resources to spin up on failover.

My primary concern is to achieve Region level high availability without having to spend cost on secondary Region until failover happens.

Abhizer Saifee
  • 303
  • 4
  • 13
  • 1
    You will always have some resource cost in fail over region. All application data must be backed up to the fail over region, always and continuously per your RPO recovery point objective. "Initially secondary Region should not have any resources" is not feasible, if you want region level fail over. – Rodrigo Murillo Jan 16 '18 at 02:37
  • I will have snapshots of EBS copied periodically to secondary region, and will run a Read replica of RDS in secondary region. But I want, EC2, Loadbalancer, EBS and other resources to spin up on failover. – Abhizer Saifee Jan 16 '18 at 07:09

0 Answers0