One of the most common mistakes when deploying an application on AWS is leaving the instance’s disk at its default. The storage type decides how many read and write operations your application can handle without bottlenecks. Here I explain the EC2 volume types, which one I use, and which options to check before launching the instance.
Note: the video is in Spanish (Spanish audio only).
EBS: your instances’ disks
AWS’s block storage service is called EBS (Elastic Block Store). When you launch an instance in EC2, the Storage section already has a volume attached: 8 GB of type gp3. You can change the size easily; in the video I raise it to 80 GB.
What gp3 means
gp stands for general purpose, and 3 is the version. There’s also gp2, and gp1 no longer shows up because it’s discontinued.
My recommendation: use gp3. It’s faster and cheaper than gp2.
IOPS: what actually matters
IOPS are the input and output operations the disk can handle per second. Here’s how they compare:
- gp3 comes with a baseline of 3,000 IOPS, and you can provision more: up to 500 per GB of volume. Note that the extra IOPS you provision cost money.
- gp2 starts at 100 IOPS and grows linearly with size after about 33.33 GB. A 35.33 GB disk only reaches 106 IOPS.
(A gp2 volume under 1 TiB can burst up to 3,000 IOPS for a while, but not sustained.)
That’s the big difference. I’d only use gp2 if the application requires it; for everything else, gp3.
When you need much more: io1 and io2
io (input/output) volumes handle far more operations:
| Type | Max IOPS | IOPS per GB |
|---|---|---|
| io1 | 64,000 | 50 |
| io2 | 256,000 | 1,000 |
io2 reaches four times what io1 does.
Update: in the video I say gp3 tops out at 16,000 IOPS. In September 2025 AWS raised that maximum to 80,000 IOPS and the largest gp3 volume to 64 TiB, so gp3 now matches io1 on IOPS. io2 is still the one that goes furthest.
The advanced options you need to check
- Delete on termination: decides what happens to the disk when you delete the instance. If it’s off, the volume is kept, and a kept volume still costs money even when it isn’t attached to any instance. If it’s on, the volume is deleted with the instance. Check it carefully.
- Encryption at rest: off by default. I recommend turning it on whenever you can: nobody can read the disk’s contents without the encryption key. Every AWS account has a default key, and you can also create your own with KMS.
You can also attach more than one volume to the same instance and, if you run short on space, resize it.
Summary
- The volume type depends on how many input and output operations your application needs.
- For most applications, a general purpose volume (gp3) is enough.
- If you need more performance, go to io1 or io2.
- Newer versions tend to be more efficient and cheaper.
AWS limits and prices change over time: confirm the numbers in the documentation before deciding. With this ready, in this quick guide I launch my own instance.
Found it useful? Watch the full video on YouTube (in Spanish) and subscribe to @Andrevops for more videos like this one.




