EBS Elastic Volumes Evolve: The 6-Hour Wait Time Is Gone, and Up to 4 Modifications Are Now Possible Within 24 Hours
This page has been translated by machine translation. View original
On January 15, 2026, the "Elastic Volumes" feature of Amazon Elastic Block Store (EBS) was enhanced. The 6-hour wait period (cooldown time) that was previously required after modifying a volume has been eliminated, and as long as the previous modification has completed, you can now make up to 4 modifications within a rolling 24-hour window.
I had the opportunity to check the behavior of this update using the AWS CLI, so I'd like to share it.
Verification
I used the following environment for verification.
- Region: Tokyo Region (ap-northeast-1)
- AWS CLI version: 2.32.22
$ aws --version
aws-cli/2.32.22 Python/3.9.25 Linux/6.1.159-181.297.amzn2023.aarch64 source/aarch64.amzn.2023
1: Consecutive capacity changes
First, I checked whether the volume size could be changed consecutively in a short period of time.
- Create a 1GB gp3 volume
aws ec2 create-volume \
--size 1 \
--volume-type gp3 \
--availability-zone ap-northeast-1a \
--tag-specifications 'ResourceType=volume,Tags=[{Key=Name,Value=test-capacity-change}]'
1st time: 1GB → 2GB
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxfe08 --size 2
Check the modification state:
aws ec2 describe-volumes-modifications --volume-ids vol-xxxxxxxxxxfe08
Result:
{
"ModificationState": "completed",
"TargetSize": 2,
"OriginalSize": 1,
"StartTime": "2026-01-16T03:32:04+00:00",
"EndTime": "2026-01-16T03:32:06+00:00"
}
The increase from 1GB to 2GB completed in 2 seconds. After the modification completed, the next modification could be executed immediately.
2nd time: 2GB → 3GB
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxfe08 --size 3
3rd time: 3GB → 4GB
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxfe08 --size 4
All modifications completed within seconds, and I was able to run them consecutively without any wait time.
2: Changing the volume type
Next, I tried changing the volume type.
- Create a gp3 volume
aws ec2 create-volume \
--size 1 \
--volume-type gp3 \
--availability-zone ap-northeast-1a \
--tag-specifications 'ResourceType=volume,Tags=[{Key=Name,Value=test-type-change}]'
- Type changes (repeated)
1st time: gp3 → gp2
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxb285 --volume-type gp2
2nd time: gp2 → gp3
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxb285 --volume-type gp3
3rd time: gp3 → gp2
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxb285 --volume-type gp2
4th time: gp2 → gp3
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxb285 --volume-type gp3
All 4 modifications succeeded.
- Attempting a 5th modification
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxb285 --volume-type gp2
The 5th modification, which exceeded the limit, returned the following error:
An error occurred (VolumeModificationRateExceeded) when calling the ModifyVolume operation:
You've reached the maximum modification rate per volume limit.
Wait until 2026-01-17T03:33:19.145Z before you can issue the next modification request for this volume.
The error message explicitly stated the time on the following day when the next modification would become possible.
3: Combined modifications
I tried modifications combining capacity, type, and performance.
- Create a 1GB gp2 volume
aws ec2 create-volume \
--size 1 \
--volume-type gp2 \
--availability-zone ap-northeast-1a \
--tag-specifications 'ResourceType=volume,Tags=[{Key=Name,Value=test-combined-change}]'
1st time: Expand capacity to 10GB
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxbb75 --size 10
2nd time: Change from gp2 to gp3
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxbb75 --volume-type gp3
3rd time: Increase IOPS from 3000 to 3500
aws ec2 modify-volume --volume-id vol-xxxxxxxxxxbb75 --iops 3500
Modifications combining capacity, type, and performance could be executed consecutively without any cooldown time.
Note that I ran them separately this time for verification purposes, but in actual operations, I recommend executing them together in a single request to conserve your modification quota.
aws ec2 modify-volume \
--volume-id vol-xxxxx \
--size 10 \
--volume-type gp3 \
--iops 3500
4: The need to wait for modification completion (completed)
In this verification, modifications of small-capacity volumes completed in a few seconds, but for large-capacity volumes, the time required to complete a modification can be on the order of hours. I checked whether the next modification could be executed on a volume that is currently being modified (in the optimizing state).
- Create a volume from a snapshot
I created a 30GB volume from a Windows Server AMI snapshot:
aws ec2 create-volume \
--snapshot-id snap-05829ab1b1e33ec69 \
--availability-zone ap-northeast-1a \
--volume-type gp3 \
--tag-specifications 'ResourceType=volume,Tags=[{Key=Name,Value=test-windows-volume}]'
- Execute a capacity change
aws ec2 modify-volume --volume-id vol-xxxxxxxxxx38a1 --size 31
- Attempt another modification during modification
While the modification state is optimizing, I try to change the capacity again:
aws ec2 modify-volume --volume-id vol-xxxxxxxxxx38a1 --size 32
The following error occurred:
An error occurred (IncorrectModificationState) when calling the ModifyVolume operation:
Volume vol-xxxxxxxxxx38a1 cannot be modified in modification state OPTIMIZING
Although the limit on the number of modifications has been relaxed, I confirmed that the next modification cannot be made until the backend optimization process (optimizing) has completed.
Summary
With Amazon EBS Elastic Volumes now allowing up to 4 modifications in 24 hours, operational flexibility has greatly improved, such as responding to sudden load increases and recovering immediately from configuration mistakes.
In this verification the modifications completed within seconds, but for large-capacity volumes the time required to complete a modification can be on the order of hours, and performance may be affected during the modification.
Before making changes in a production environment, we strongly recommend preparing a verification environment that reproduces production using snapshots or AMIs, and conducting a rehearsal in advance to check the time required and the performance impact.
Reference links
