# Amazon EBS volume limits

AWS limits and quotas · Updated 17 November 2026

**Short answer:** A gp3 volume can be 1 GiB to 64 TiB with up to 80,000 IOPS and 2,000 MiB/s; gp2 tops out at 16 TiB and 16,000 IOPS; io2 Block Express reaches 64 TiB and 256,000 IOPS; st1 and sc1 range from 125 GiB to 16 TiB. You can modify a volume up to four times in a rolling 24-hour period, once each change has completed. Each Region also has adjustable quotas on total provisioned storage per volume type (for example 50 TiB of gp3 in most large Regions) and 100,000 snapshots.

## Per-volume limits by type

| Type | Size | Max IOPS | Max throughput |
|---|---|---|---|
| gp3 | 1 GiB to 64 TiB | 80,000 | 2,000 MiB/s |
| gp2 | 1 GiB to 16 TiB | 16,000 | 250 MiB/s |
| io2 Block Express | 4 GiB to 64 TiB | 256,000 | 4,000 MiB/s |
| io1 | 4 GiB to 16 TiB | 64,000 | 1,000 MiB/s |
| st1 (throughput HDD) | 125 GiB to 16 TiB | 500 | 500 MiB/s |
| sc1 (cold HDD) | 125 GiB to 16 TiB | 250 | 250 MiB/s |

st1 and sc1 cannot be boot volumes. The instance also caps what a volume can deliver: every instance type has a maximum EBS bandwidth and IOPS, so a 2,000 MiB/s gp3 volume on a small instance will be limited by the instance, not the volume. gp3's higher figures arrived recently; older references still list 16 TiB and 16,000 IOPS for gp3.

## Account and Region quotas

| Quota | Default | Adjustable |
|---|---|---|
| Storage for gp3 volumes, in TiB | 50 in most large Regions (300 in several newer ones) | Yes |
| Storage for gp2 volumes, in TiB | 50 in the original large Regions, 300 elsewhere | Yes |
| Storage for io2 volumes, in TiB | 20 | Yes |
| IOPS for io1 volumes | 300,000 | Yes |
| Snapshots per Region | 100,000 | Yes |
| Fast snapshot restore, snapshots enabled | 5 | Yes |
| Archived snapshots per volume | 25 | Yes |
| Concurrent snapshots per sc1 volume | 1 | No |

The storage quotas are totals across all volumes of that type in the Region, so a fleet of 500 GiB gp3 volumes reaches 50 TiB at 100 volumes. When you exceed one, `CreateVolume` or `RunInstances` fails with a message saying the request would exceed your maximum storage limit for that type.

```
aws service-quotas list-service-quotas --service-code ebs \
  --query "Quotas[?contains(QuotaName,'Storage for')].[QuotaName,QuotaCode,Value]" --output table

# Total provisioned gp3 GiB in this Region
aws ec2 describe-volumes --filters Name=volume-type,Values=gp3 --query 'sum(Volumes[].Size)'
```

## Modification limits (Elastic Volumes)

- You can change size, type, IOPS or throughput up to **four times in a rolling 24-hour period**, and only after the previous change has finished (state `completed`). Exceeding this returns an error telling you when the next modification is allowed. Older guidance said one change per six hours; the documentation now describes four per 24 hours.
- A size increase is usable once the modification reaches `optimizing`, usually within seconds; you then extend the partition and file system inside the OS. See [increase an EBS volume](https://cloudconsole.dev/how-to/increase-ebs-volume-size).
- Volumes can grow but never shrink. To get a smaller volume, create one and copy the data.
- Optimisation can take hours (up to about six for a 1 TiB volume, and not proportional to size); performance stays between old and new values meanwhile.

```
aws ec2 modify-volume --volume-id vol-0123456789abcdef0 --size 500 --iops 6000 --throughput 500
aws ec2 describe-volumes-modifications --volume-ids vol-0123456789abcdef0 \
  --query 'VolumesModifications[].{state:ModificationState,progress:Progress}'
```

## Volumes per instance

How many volumes you can attach depends on the instance type: on many Nitro instances EBS volumes share attachment slots with network interfaces and NVMe instance store, while some newer types have a dedicated EBS volume limit. Check the instance type's documented volume limit before designing around many small volumes; one larger gp3 volume with provisioned IOPS is often simpler.

## Questions

### What is the maximum size of an EBS volume?

64 TiB for gp3 and io2 Block Express, and 16 TiB for gp2, io1, st1 and sc1.

### How often can I modify an EBS volume?

Up to four times within a rolling 24-hour period, waiting for each modification to complete before starting the next.

### Can I decrease the size of an EBS volume?

No. Elastic Volumes only increases size. Create a smaller volume and copy the data across instead.

## When this happens away from your desk

A full disk rarely waits for working hours. CloudConsole, a phone app for AWS, is being built to show disk and status alarms on your phone so you can see a volume filling up before the instance stops responding.

[About the CloudConsole app](https://cloudconsole.dev/aws-console-app) · [Download on the App Store](https://apps.apple.com/app/cloudconsole-for-aws/id6835419710)

## Sources

- [Amazon EBS volume types](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-volume-types.html)
- [Amazon EBS endpoints and quotas](https://docs.aws.amazon.com/general/latest/gr/ebs-service.html)
- [Modify a volume using Amazon EBS Elastic Volumes](https://docs.aws.amazon.com/ebs/latest/userguide/ebs-modify-volume.html)

## Related

- [How to increase EBS volume size](https://cloudconsole.dev/how-to/increase-ebs-volume-size)
- [aws ec2 describe-volumes](https://cloudconsole.dev/cli/ec2-describe-volumes)
- [aws ec2 create-snapshot](https://cloudconsole.dev/cli/ec2-create-snapshot)
- [CloudWatch alarm for EBS VolumeStalledIOCheck](https://cloudconsole.dev/alarms/ebs-volumestallediocheck)
- [EC2 vCPU limits (On-Demand and Spot instance quotas)](https://cloudconsole.dev/limits/ec2-vcpu-limit)
- [How to request an AWS service quota increase](https://cloudconsole.dev/limits/service-quotas-increase)

---

Source: https://cloudconsole.dev/limits/ebs-volume-limits

CloudConsole is an independent iPhone and Android app for Amazon Web Services by Cloudconcur Ltd. It is not affiliated with Amazon Web Services.
