
Even so, you should have at least some idea of how your backup plan is ultimately going to be used. That's something that you will do later on. A backup plan does not define the resources that are to be backed up. The second thing that you will need to do is to determine whether or not you will need to perform application consistent backups.Īs you have seen so far, a backup plan is primarily used to define the backup frequency and the retention requirements. Tagging can be useful if you have complex backup requirements and will be creating multiple plans. First, you will need to apply any required tags to the backup plan. When you finish evaluating the backup rules, there are two more things that you need to do as a part of creating the backup plan. Having multiple backup vaults can be useful in situations in which there are multiple administrators, each of whom are responsible for a subset of your organization's AWS resources.

Amazon provides a default backup vault that is used by default, but you do have the option of creating additional backup vaults.

The rules also determine which backup vault your backups will be saved to. Figure 4: You can review a backup rule by clicking on it.
