We need to keep the product running even if human errors happen, or natural disasters or data corruption. In this section, we will look at ways Amazon helps us to lower our time to remedy some common disruptions. Good practices for incident management and post-mortems help us to stay within our error budgets while strengthening our services. In our metrics-driven engineering practice, we recommend exercising these processes regularly in order to fine tune your existing SLOs and identify any missing ones.
Just as we use S3 to replicate our objects, CodeCommit to protect our source, and ECR for the durability of our container images (in the next chapter), we can use disk snapshots to help us to safeguard our instance-attached storage:
resource "aws_ebs_volume" "example" {
availability_zone = "us-west-2a"
size = 40
tags {
Name = "HelloWorld"
}
}
resource "aws_ebs_snapshot" "example_snapshot" {
volume_id = "${aws_ebs_volume.example.id}"
tags {
...