Home / AWS Backup errors

Backup fails when the source resource carries tags

Critical FAILED AWS Backup
What AWS reports
not authorized to perform: backup:tagbackup:tagresource

Matched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.

What is actually happening

If your source resources have tags, or you want tags copied onto recovery points, the AWS Backup IAM role needs backup:TagResource on recovery points. Without it, resources with tags fail while untagged ones succeed — so the failure looks random until you notice the pattern.

How to fix it

  1. Open IAM → Roles and select the role AWS Backup uses.
  2. Add backup:TagResource to the policy.
  3. Scope it to "Resource": "arn:aws:backup:*:*:recovery-point:*" rather than granting it broadly.
  4. Re-run the backup for a tagged resource to confirm.

What AWS documents

AWS states the role needs backup:TagResource applied to arn:aws:backup:*:*:recovery-point:* when source resources contain tags.

Source: AWS Backup Developer Guide — Troubleshoot creating resources

Stop finding this one failure at a time

BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.

Start free trial