Amazon EFS volumes should be in backup plans
Confirms that each EFS file system is in an AWS Backup plan in the same Region, protecting it from deletion and data loss: EFS automatic backups are on, a plan's resource assignment selects it (no backup has to have run yet), or AWS Backup already holds a recovery point for it. A resource assignment with both a resource list and a tag list must match both here.
- service
- EFS
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Affects another check: A plan assignment leaves EFS.7 failing, which needs EFS automatic backups; turning those on in the file system's General settings passes both checks instead.
In the console
AWS Backup → Backup plans → the plan → Resource assignments → Assign resources
- IAM role
- Default role, or a role allowed to back up EFS file systems
- Define resource selection
- Include specific resource types; Include all resource types needs EFS opted in to AWS Backup
- Select resource types
- EFS, with this file system left selected (by default every EFS file system is)
- Refine selection using tags
- Optional; the file system must match every tag condition you add
With the AWS CLI
aws backup create-backup-selection --backup-plan-id <backup-plan-id> --backup-selection '{"SelectionName":"efs-file-systems","IamRoleArn":"<backup-role-arn>","Resources":["arn:aws:elasticfilesystem:*:*:file-system/*"]}' --region <region>With Terraform
resource "aws_backup_selection" "this" {
name = "efs-file-systems"
plan_id = var.backup_plan_id
iam_role_arn = var.backup_role_arn
resources = ["arn:aws:elasticfilesystem:*:*:file-system/*"]
}
See which of your accounts this check is failing on.
Book a live scan