The Recovery Point Objective is the acceptable amount of data that can be listed in the event of a downtime. For example, the failed RDS database can be restored in another instance, using the last snapshot available; in this case, the 12:00 AM snapshot. This recovery mode will drop eight hours of database transactions; from the business perspective, the risk associated with the loss of the master database node and the volume of transactions is low, and the cost to maintain a standby replica is high:

To lower the RPO and RTO, several methods can be put in place, like continuous snapshots, active replication, and redundancy.

The AWS Disaster Recovery options will be discussed next, ordered from the highest to the lowest recovery objectives.