- Newest
- Most votes
- Most comments
Hi,
In addition to Oleksii's answer, I suggest to read https://aws.amazon.com/blogs/mt/establishing-rpo-and-rto-targets-for-cloud-applications/
This blog post details the various aspects of RTO and RPO for cloud applications and the standard AWS recovery models:
- Backup & Resrore
- Pilot Light
- Warm Standby
Best,
Didier
if you store data in EC2, you can regularly create snapshots. RPO would be the time between two snapshots
For example you can use AWS Backup for it
https://aws.amazon.com/getting-started/hands-on/amazon-ec2-backup-and-restore-using-aws-backup/
But actually it's not the best practice to rely on EC2 as data storage. The better way is to keep EC2 as an immutable and easily changeable compute (add and remove EC2 instances as you need during scaling)
RTO would be the time when a particular EC2 instance recovers after the failure, but again, it's better to remove the failed instance and create a new one instead. At least start designing such an approach
thanks for the answer.
Relevant content
asked 2 years ago
asked 2 years ago

Thanks for the answer
Hi Dara, thanks for accepting my answer! Didier