My Amazon EBS snapshots show no progress or receive the error "ConcurrentSnapshotLimitExceeded". How can I resolve this?

2 minute read

Multiple snapshots for my Amazon Elastic Block Store (Amazon EBS) volume are stuck at less than or equal to 100% progress in pending state. When I try to launch a new snapshot, I receive the error: ConcurrentSnapshotLimitExceeded. How can I resolve this issue?

Short description

The ConcurrentSnapshotLimitExceeded error might occur for the following reasons:

  • You have too many snapshots running concurrently. When multiple snapshots are running concurrently, newer snapshots remain in the pending state until the pending snapshot with the oldest "Started" time moves to the completed state. A single gp2, io1, io2, or Magnetic volume can have up to five concurrent pending snapshots. A single st1 or sc1 volume can have one pending snapshot.
  • You deleted an in-progress snapshot. You can delete EBS snapshots while they're in progress. If you then initiate a new snapshot, the displayed progress percentage might be stuck for an extended period of time. The deleted snapshot progress will continue until it's 100% complete.

If you try to initiate more than the allowed concurrently pending snapshots (including any deleted while in progress), you receive the error message ConcurrentSnapshotLimitExceeded.


When you receive this error, you've reached the limit on the number of concurrent snapshots you can create on the specified volume. Wait until the 'pending' requests complete. After all pending requests complete, check that you don't have snapshots that are in an incomplete state, such as 'error'. Snapshots in an incomplete state count against your concurrent snapshot limit.

Note: As a best practice, allow sufficient time for the previous snapshot to complete. It's a best practice to wait 15 seconds between create-snapshot API requests for the same volume. For additional information, see Amazon EBS FAQs.

Related information

Creating an Amazon EBS snapshot


Error codes

AWS OFFICIALUpdated 3 years ago