Ravi Sir's Cards › AWS
Named backup
This revision card explains Named backup. It starts from the need that risky changes without a snapshot are gambling. On the card, the building blocks include create-backup before migration; list-backups; keep cost watched. The how-to section notes change ticket , then backup name , then verify AVAILABLE , then proceed. An example on the card is lucas Meyer snapshots ledgers before schema weekends.
Read card text
What this card says
Why do we need it?
Risky changes without a snapshot are gambling.
What is it?
create-backup before migration; list-backups; keep cost watched.
on-demand backup
How to do it
Change ticket → backup name → verify AVAILABLE → proceed.
Example
Lucas Meyer snapshots ledgers before schema weekends.