Home / AWS Backup errors

AccessDenied / insufficient privileges

Critical FAILED AWS Backup
What AWS reports
backup job failed because of insufficient privilegesyou are not authorized to perform this operationinsufficient privileges to perform this actioninsufficient privilegesnot authorizedaccess denied

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

What is actually happening

AWS Backup assumes an IAM role to perform the backup. Either that role lacks permission for the resource type, or AWS Backup is not a trusted entity allowed to assume it. Each AWS service AWS Backup supports needs different permissions, so a role that works for EBS may still fail for S3 or RDS.

How to fix it

  1. Confirm the role lists AWS Backup as a trusted entity — without that, AWS Backup cannot assume it at all.
  2. Use AWSBackupDefaultServiceRole for backup plans and manual jobs. AWS creates two roles with different purposes; AWSServiceRoleForBackup is not the one to pass here.
  3. Attach AWSBackupServiceRolePolicyForBackup, and AWSBackupServiceRolePolicyForRestores if you restore.
  4. Check the KMS key policy contains Principal arn:aws:iam::<account-id>:root. Without it, IAM policies granting key access have no effect — though IAM policies denying access still do.
  5. For Amazon S3, run the one-time permissions setup. The default role does not include S3 backup and restore permissions.
  6. If your resources carry tags, grant backup:TagResource on arn:aws:backup:*:*:recovery-point:*.

What AWS documents

AWS lists the trust relationship, per-service permissions, and the KMS key policy root principal as the three requirements. It notes IAM allow policies on a key are ineffective without that principal, while deny policies still apply.

Source: AWS re:Post — Why does my AWS Backup job fail?

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