With the cloud’s ever-changing and dynamic characteristics, its environments require newer and easier approaches to cloud backup processes. EC2 servers and instances are commonly rolled into new ones, but the data within them needs to be preserved and stay consistent. Since existing backup mechanisms may still try to backup older resources, backup can become challenging. Ideally, each time an instance is rolled into a new one, a backup solution should automatically recognize the changes and perform backups in a continuous fashion. I’d like to share how this can be done within the AWS cloud, leveraging its resource tagging capability.
In Part 1 of this series about AWS Compute Optimizer, we provided a brief overview of AWS instance types and examined the various EC2 dimensions