This is a demo: the account, the resources and the restore history below are synthetic. The layout, the verdicts and the PDF are exactly what a real scan produces.
Demo data — not a real AWS account
Your oldest verified restore is 412 days old — and 10 of 14 resources have never been restored.
Account Acme SaaS (demo) 1111••••3333 · regions eu-west-1 · scanned 2026-10-27 10:41 UTC
Protected resources
12/14
Never restored
10
Restore age > 180 days
2
Oldest verified restore
412d
Download the one-page PDFscan 00000000-0000-4000-8000-000000000000
| Resource | Type | Retention | Last backup | Restore age | Verdict |
|---|---|---|---|---|---|
acme-backup-target S3 · eu-west-1 · inventory on versioning enabled · replicated · in an AWS Backup plan · 2 lifecycle rule(s) | S3 | versioning | — | never | never No completed restore in AWS Backup restore history |
acme-csv-exports S3 · eu-west-1 no versioning, no replication | S3 | versioning | — | never | never No completed restore in AWS Backup restore history |
acme-logs-archive S3 · eu-central-1 versioning suspended · 4 lifecycle rule(s) | S3 | versioning | — | never | never No completed restore in AWS Backup restore history |
acme-static-site S3 · eu-west-1 no versioning, no replication | S3 | versioning | — | never | never No completed restore in AWS Backup restore history |
acme-user-uploads S3 · eu-west-1 versioning enabled · 1 lifecycle rule(s) | S3 | versioning | — | never | never No completed restore in AWS Backup restore history |
aurora-core Aurora aurora-postgresql 16.4 · 2 member(s) automated backups 7d · 3 manual snapshot(s) · in an AWS Backup plan | Aurora | 7 days | 2026-10-27 | never | never No completed restore in AWS Backup restore history |
aurora-reporting Aurora aurora-mysql 3.08.0 · 1 member(s) automated backups 5d | Aurora | 5 days | 2026-10-27 | never | never No completed restore in AWS Backup restore history |
legacy-crm RDS postgres 13.16 · db.t4g.large 1 manual snapshot(s) | RDS | — | 2026-04-30 | never | never No completed restore in AWS Backup restore history |
prod-orders RDS mysql 8.0.39 · db.r6g.large · Multi-AZ automated backups 7d · 1 manual snapshot(s) · in an AWS Backup plan | RDS | 7 days | 2026-10-27 | never | never No completed restore in AWS Backup restore history |
staging-orders RDS mysql 8.0.39 · db.t4g.medium automated backups 1d | RDS | 1 days | 2026-10-26 | never | never No completed restore in AWS Backup restore history |
analytics-warehouse RDS postgres 16.4 · db.m6g.2xlarge automated backups 3d · 2 manual snapshot(s) | RDS | 3 days | 2026-10-27 | 247 days | >180 days AWS Backup restore job · 247d ago · validation SUCCESSFUL |
prod-identity RDS postgres 15.8 · db.r6g.xlarge · Multi-AZ automated backups 14d · in an AWS Backup plan | RDS | 14 days | 2026-10-27 | 412 days | >180 days AWS Backup restore job · 412d ago · validation SUCCESSFUL |
acme-invoices S3 · eu-west-1 · inventory on versioning enabled · replicated · 3 lifecycle rule(s) | S3 | versioning | — | 96 days | 31–180 days AWS Backup restore testing · 96d ago · validation SUCCESSFUL |
prod-billing RDS postgres 16.4 · db.r6g.large · Multi-AZ automated backups 7d · 4 manual snapshot(s) · in an AWS Backup plan | RDS | 7 days | 2026-10-27 | 12 days | ok AWS Backup restore job · 12d ago · validation SUCCESSFUL |
Scan notes
- Demo dataset: synthetic resources, not a real AWS account.
What this report is — and is not
- Metadata only: this scan used AWS describe/list APIs. No S3 object, database row or backup content was read, and no credentials were stored.
- Restores performed outside AWS Backup (for example rds:RestoreDBInstanceFromDBSnapshot or a manual copy) are not observable through the read-only API. History can therefore be under-reported, never over-reported.
- A restore age of 'unknown' means this scan could not read the API that would prove or disprove it. Missing evidence is not reported as evidence of failure.
- Not a compliance certification. We report facts with dates; an auditor or your insurer decides what they accept.