Backup Region Infrastructure

Workload in the Backup Region

If we’ve decided to fail over to the backup region, the first thing we need to do is deploy the rest of the workload in the backup region.

Download and review scripts and templates

Download the following files:

Review these files and adjust any of the input parameters to suit your needs.

In your working directory, place in a directory called scripts and place the file dr-infra.yaml in a directory called cfn.

Deploy stack

Now create the stack in the backup region:

chmod +x ./scripts/
./scripts/ <template bucket> <template prefix> <stack name> <REGION> <backup bucket name> <ingress prefix> <ingress CIDR> <backup ARN> <source table ARN> <target table name>

Note that we pass in the primary region as the fourth argument. The ingress CIDR argument is the static IP for our example producer, which you can find in the output of the CFN stack used in the primary region. The source table ARN argument can be found in the DynamoDB console, and the target table name argument is processed_tweets. The backup ARN argument is optional in case you want to restore from a specific backup rather than using PITR; you can set it to a placeholder value like arn otherwise.

For example:

./scripts/ backuprestore cfn BackupRestore us-west-2 MyBackupBucket MyPrefix arn:aws:dynamodb:us-west-2:XXX:table/processed_tweets/backup/01628628265604-97d01acc arn:aws:dynamodb:us-west-2:XXX:table/processed_tweets processed_tweets

To update the stack, add the --update flag as the last argument.

Start Analtyics Application

Now, navigate to Kinesis Analytics in the AWS Console in the backup region. Click on the radio button for the application called <stack name>-KinesisAnalyticsApplication and select Run.

Enable DynamoDB point-in-time recovery

Navigate to DynamoDB in the AWS Console. Select the processed_tweets table and go to Backups. Enable PITR and save the changes.

Point-in-time recovery

Point-in-time recovery