Failover to Secondary

When a regional service event affects the Unicorn application in the primary region N. Virginia (us-east-1), we want to bring up the resources in the secondary region N. California (us-west-1).

We assume a regional service event has occurred. In this section, we will manually perform a series of tasks to bring up the application in the secondary region N. California (us-west-1). In a production environment, we would automate these steps using an AWS Cloudformation template or third-party tools.

We will perform the following:

  • Launch an EC2 instance from the AMI (Amazon Machine Image)
  • Restore the RDS database from backup
  • Configure the application

Simulating a Regional Service Event

We will now simulate a regional service event affecting the S3 static website in N. Virginia (us-east-1) serving The Unicorn Shop website.

1.1 Click S3 to navigate to the dashboard.

1.2 Click on the backupandrestore-uibucket-xxxx link.

1.3 Click the Permissions link. In the Block public access (bucket settings) section, click the Edit button.

1.4 Enable the Block all public access checkbox, then click the Save button.

1.5 Type confirm, then click the Confirm button.

1.6 Click the Properties link.

1.7 In the Static website hosting section. Click on the Bucket website endpoint link.

1.8 You should get a 403 Forbidden error.