EBS

Learn Amazon EBS block storage for EC2, including volume types, snapshots, encryption, performance, and availability boundaries.

Last reviewed: June 2026

·AWS CloudAWS CLI v2AWS SDKsAWS Well-Architected Framework
✅
Quick Understanding: EBS helps teams design, build, secure, operate, and troubleshoot AWS workloads. In enterprise projects, the important questions are ownership, blast radius, automation, observability, compliance, and cost.

🔍 What Is It?

Amazon Elastic Block Store provides block volumes for EC2 instances.

EBS behaves like a disk attached to an instance. It is used for operating systems, application data, databases on EC2, and workloads that need low-latency block storage.

🎯 Why Do We Need It?

EC2 instances need persistent disks. Instance store can be temporary, but EBS volumes persist independently of instance stop/start behavior.

EBS also supports snapshots, encryption, resizing, and multiple performance classes.

Common developer mistakes:

  • →Choosing defaults without checking security, cost, or failure behavior
  • →Treating AWS services as isolated tools instead of part of an architecture
  • →Skipping tags, alarms, IAM review, backups, and runbooks until production incidents happen
  • →Building manually in the console and then struggling to reproduce environments

🏗️ What Happens in Real Projects?

A self-managed Elasticsearch node may use encrypted EBS volumes sized for throughput and IOPS. Snapshots are scheduled, CloudWatch monitors queue length and burst balance, and replacement automation reattaches or recreates volumes as needed.

For many databases, teams choose managed RDS instead of self-managing on EBS.

⚙️ How It Works

An EBS volume is created in one AZ and attached to an EC2 instance in that same AZ.

The OS formats and mounts the volume. Snapshots store point-in-time backups in S3-managed storage. Volume type, size, provisioned IOPS, and throughput determine performance behavior.

💻 Example

EBS production checklist — Operational checks for an EC2 workload using EBS.

text
Volume type: gp3 or io2 based on workload
Encryption: enabled with managed or customer key
AZ: same as attached EC2 instance
Snapshots: scheduled and retention managed
Monitoring: latency, queue depth, throughput, IOPS
Recovery: snapshot restore tested
Cost: unattached volumes detected and cleaned

🤔 Common Confusions

❓ Can one EBS volume attach across AZs?

No. EBS is zonal. The instance and volume must be in the same AZ.

❓ Is EBS the same as S3?

No. EBS is block storage for EC2. S3 is object storage accessed through APIs.

❓ Do snapshots equal instant recovery?

Snapshots help recovery, but restore time, data consistency, and runbooks must be tested.

🚨 Common Production Issues

**Unattached volumes** continue billing after instances are deleted.

**No snapshots** makes volume loss or corruption difficult to recover from.

**Under-provisioned IOPS** causes application latency.

**AZ dependency** blocks recovery if architecture assumes cross-AZ attach.

✅ Best Practices

Encrypt EBS volumes by default

Use gp3 for general workloads and provision performance explicitly when needed

Schedule snapshots and test restoration

Monitor IOPS, throughput, latency, and queue length

Clean up unattached volumes

Prefer managed databases when database operations are not a differentiator

🏛️ Architect's Note

Senior Architect's Perspective

EBS is reliable block storage, but it is still a zonal dependency. High availability comes from application, database, or platform replication around EBS, not from pretending a single volume is multi-AZ.

💬 Frequently Asked Questions

Interview: How would you explain EBS in a real AWS project?

EBS should be explained through the business workload it supports, the AWS responsibility boundary, the failure modes, the security controls, and how it is monitored and automated.

Interview: What production mistake do developers commonly make with EBS?

The common mistake is using the service successfully in a lab but not designing for least privilege, multi-AZ resilience, alarms, cost visibility, and repeatable infrastructure.

Can I resize EBS volumes?

Yes. Volumes can be expanded, and the filesystem usually must be expanded inside the OS.

What is gp3?

gp3 is a general purpose SSD volume type where size, IOPS, and throughput can be configured more independently than older gp2 behavior.

🎯 Key Takeaways

1EBS is block storage for EC2
2EBS volumes are zonal
3Snapshots and encryption are essential production controls
4Performance must be sized and monitored

🎯 Practice this topic in interviews

↗ Where this topic fits

Sources

Sources / References

Use these AWS references to verify the concept in official docs and continue into the most relevant SplashRide pages.