KMS protects your data from being read. AWS Backup protects it from being lost. It is one place to schedule, run and keep backups for many AWS services, instead of setting up each service on its own.

What AWS Backup does

  • It gives you a central place to manage backups across services such as EBS, RDS, DynamoDB, EFS and S3.
  • You describe what you want in a backup plan, and AWS Backup runs it on a schedule.
  • Backups are stored in a backup vault, which can be encrypted with a KMS key.
  • Every backup job is tracked, so you can see what ran and what failed.

Key concepts

Piece What it is
Backup plan The rules: schedule, lifecycle and which vault to use
Backup rule One schedule inside a plan, such as daily at 05:00 UTC
Resource assignment Which resources the plan covers, by ID or by tag
Backup vault The container that stores recovery points
Recovery point One saved backup that you can restore from
Lifecycle When a backup moves to cold storage or expires

Good to know

  • Assign resources by tag, for example Backup = daily, so new resources are picked up automatically.
  • Set a retention period so old backups do not pile up and cost money.
  • A restore creates a new resource from the recovery point. It does not overwrite the old one.
  • Vault Lock can stop backups from being deleted too early.
  • Cross-Region and cross-account copies help with disaster recovery.

Hands-on: try it in your own account

  1. Open AWS Backup in the console and choose Create backup plan.
  2. Pick Build a new plan and name it demo-daily.
  3. Add a rule: Daily, with retention of 7 days (keep it short to limit cost).
  4. Use the Default backup vault.
  5. Create the plan, then choose Assign resources.
  6. Select Include specific resource types, pick one small resource such as an EBS volume, or assign by tag Backup = daily.
  7. Choose On-demand backup for the same resource to test it now, and wait for the job to finish under Jobs.
  8. Open the recovery point and look at the Restore option.
  9. Clean up: delete the recovery point, the resource assignment and the backup plan.

Common mistakes

  • Making a backup plan but forgetting to assign resources, so nothing is backed up.
  • Never testing a restore. A backup you cannot restore is not a backup.
  • Keeping backups forever and paying for storage you do not need.
  • Keeping backups only in one Region and one account.
  • Forgetting that a backup vault key in KMS must stay available.

Key takeaways

  • AWS Backup gives one place to schedule and track backups across services.
  • A plan holds the rules, a vault holds the recovery points.
  • Assign resources by tag so new ones are covered.
  • Test a restore, and set retention to control cost.

Tomorrow I'll recap the AWS security and operations topics from this series.

Part of #120DaysOfAWS.