See how your platform is backed up, in one page

Your repository now has a docs/backups.md page. It gives a clear overview of how your platform is backed up: what is backed up, by which system, how often, and for how long. It complements the general backup documentation with the details that are specific to your platform.

What is on the page

• A summary table of every backed-up resource, with the backup system (Velero, RDS automated backups, AWS Backup, managed-database backups, and so on), the schedule, and the retention.
• A section per component with the same detail and the exact infrastructure-as-code files that configure it.
• A logging section: the control-plane log retention and the application-log retention.
• A “Not backed up” section that lists what has no backup, for example object-storage buckets, container images, or caches. This makes your coverage explicit, so nothing is a surprise.

What you gain

• One place to see your backup coverage and retention, instead of reading it out of the code.
• A clear view of any gaps, so you can decide what to change.
• Honest scope: we state what we do not back up, not only what we do.

What you need to do

• Nothing right now. The page is already in your repository.
• Read it, and tell us through a GitHub issue if a retention or a coverage does not match what you need. What is backed up, for how long, and how often, is defined per customer, so we set it to your requirements.

Keeping it current

We update docs/backups.md in the same pull request whenever we change a backup-related resource, so the page stays accurate over time.