No AWS Backup vault configured

Severity: Medium
Service: Resilience
Check ID: BACKUP_NO_VAULT

What this check finds

No AWS Backup vault exists in this region. Without a Backup vault, centralised backup policies (backup plans) cannot store recovery points, and cross-account or cross-region recovery is unavailable. Critical data may have no resilient recovery path.

Passing looks like: AWS Backup vault configured.

How to fix it

Create a Backup vault.

AWS CLI

aws backup create-backup-vault --backup-vault-name Default --encryption-key-arn <KMS-ARN>

Names in capitals are placeholders for your own resource. Review a command before you run it.

AWS console

AWS Backup → Backup vaults → Create Backup vault.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to No AWS Backup vault configured
Framework	Controls
HIPAA Security Rule	164.308(a)(7) Contingency Plan — Data Backup, Disaster Recovery, Emergency Mode
NIST SP 800-53 Rev5 (Moderate)	CP-9 System Backup
NIST Cybersecurity Framework 2.0	PR.DS-11 Backups of data are created and protected
ISO/IEC 27001:2022 Annex A	A.5.29 Information security during disruption A.5.30 ICT readiness for business continuity A.5.33 Protection of records A.8.13 Information backup

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs