The root volume is the primary storage volume that contains the operating system of an EC2 instance. It determines boot behavior, persistence of the OS across stop/start cycles, performance characteristics, and whether data survives instance termination.
Every EC2 instance has a root volume that holds the operating system, boot loader, and base configuration derived from the Amazon Machine Image (AMI). The type of root volume — either EBS (Elastic Block Store) or Instance Store — has major implications for data persistence, instance behavior during stop/terminate operations, and overall reliability.
The OS is stored on a network-attached EBS volume
Instance can be stopped and restarted — data persists on the EBS volume
By default, the root EBS volume is deleted when the instance is terminated (DeleteOnTermination = true)
You can change DeleteOnTermination to false to keep the volume after termination
Supports snapshots for backup and AMI creation
Can be encrypted using AWS KMS
Supports volume type changes (gp2, gp3, io1, io2) for performance tuning
Boot time is typically faster and more reliable than instance store
The OS is stored on physically attached NVMe/SSD storage on the host server
Extremely high I/O performance — no network latency
Data is permanently LOST when the instance is stopped, terminated, or the host fails
Cannot be stopped — only rebooted or terminated
Not suitable for production data storage without external replication
Best for temporary scratch space, caches, or buffer data
Always use gp3 (General Purpose SSD v3) for root volumes — it is cheaper and faster than gp2
Enable encryption on root volumes for security compliance (HIPAA, PCI-DSS)
Set DeleteOnTermination to false for critical instances to prevent accidental data loss
Take regular EBS snapshots of root volumes for backup and disaster recovery
Size the root volume appropriately — avoid running out of OS disk space in production
Separate application data and logs onto a dedicated EBS volume, not the root volume