X
Lab complete!
Now that you have completed this lab, make sure to update your Well-Architected review if you have implemented these changes in your workload.
Click here to access the Well-Architected Tool
Module 2: Pilot Light
In this module, you will go through the Pilot Light disaster recovery strategy. To learn more about this disaster recovery strategy, you can review this Disaster Recovery blog.
Pilot Light disaster recovery strategy has Recovery Point Objective(RPO) / Recovery Time Objective (RTO) within tens of minutes. For the pilot light strategy secondary region, the data is live and core infrastructure is provisioned, but the services are either idle or absent.
Our application is currently deployed in our primary region N. Virginia (us-east-1) and we will use N. California (us-west-1) as our secondary region.
Our test application is Unishop. It is a Spring Boot Java application deployed on a single Amazon Elastic Compute Cloud (EC2) instance using a public subnet. Our datastore is an Amazon Aurora MySQL database with a frontend written using bootstrap and hosted in Amazon Simple Storage Service (S3).
This module takes advantage of Amazon Machine Images (AMI) which we will use to launch our Amazon EC2 instance and Amazon Aurora Global Database to replicate our Amazon Aurora MySQL data to our secondary region.
CloudFormation will be used to configure the infrastructure and deploy the application. Provisioning your infrastructure with infrastructure as code (IaC) methodologies is a best practice. CloudFormation is an easy way to speed up cloud provisioning with infrastructure as code.
Prior experience with the AWS Console and Linux command line are helpful but not required.
Because this workload has only one EC2 instance that is deployed in only one Availability Zone, this architecture does not meet the AWS Well Architected Framework best practices for running highly available production applications but suffices for this workshop.
