Throttling / too many concurrent backups
What AWS reports
request limit exceededthrottlingexceptiontoo many requestsrate exceededMatched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.
What is actually happening
Firing a very large number of jobs in the same minute can hit AWS API rate limits. Note this is distinct from a per-resource concurrency limit such as EFS allowing only one backup at a time — that has its own entry.
How to fix it
- Stagger backup schedules across the window instead of one simultaneous burst.
- Reduce backup frequency for low-change resources.
- Request a service quota increase if you legitimately need more concurrency.
What AWS documents
AWS notes some resources such as EFS allow only one concurrent backup to be queued at a time.
Source: AWS Backup Developer Guide — Troubleshooting
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