- Newest
- Most votes
- Most comments
Based on the information provided, you're experiencing an issue with multiple AWS Backup restore jobs for EFS that are stuck in PENDING status for over 4 hours with 0% progress.
This appears to be an unusual situation that requires AWS Support intervention. While your verification steps (checking IAM permissions, KMS key policy, service health, and EFS health) are appropriate troubleshooting measures, the persistent PENDING status across multiple restore jobs suggests a potential underlying service issue.
You can try the following additional troubleshooting steps:
-
Check if there are any restore job summaries available using the ListRestoreJobSummaries API, which provides information about restore jobs created or running within the last 30 days.
-
Attempt to create a new restore job with different parameters to see if the issue persists.
-
If possible, try a restore in a different AWS region to determine if the issue is region-specific.
-
Since this appears to be affecting multiple restore jobs and you've already verified the common configuration elements, I recommend opening an AWS Support case with the details you've provided, including all the job IDs and timestamps. Make sure to set the severity as high given the business impact of not being able to restore your EFS backups.
If you have Business or Enterprise Support, you should be able to get assistance relatively quickly for this type of service-impacting issue.
Sources
ListRestoreJobSummaries - AWS Backup
URGENT: Instance Down for 4 Days, No Response from AWS Support (Case IDs: 17nnnnnnnnnnnnn & 17nnnnnnnnnnnnn) | AWS re:Post
Relevant content
- asked 4 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago

There are no logs anywhere, Already tried to create new restore job... thats how I ended up with. 4 ... tried old FS, new FS and what not ... I agree that its likely some issue on AWS side but we dont have technical support plan