What Is EBS?
Amazon Elastic Block Store (EBS) is a high-performance block storage solution designed to be used with EC2 instances. It works by giving the user access to a multitude of small network-attached blocks, each of which is presented as a simple volume.
This distributed way of providing storage allows for easy expansion of storage capacity when needed; EBS volumes can scale into petabytes of data. EBS also ensures high availability (HA) and durability by replicating all data within the Availability Zone (AZ).
Amazon EBS volumes are very easy to use, whether you need to add them to or remove them from the EC2 instance, modify their size, or change their type. With only a couple of clicks, you can create an EBS snapshot, effectively making a backup of your entire volume. This can later be used to recreate the data if necessary.
This is part of a series of articles about AWS Backup
An Overview of AWS EBS Volume Types
All EBS volumes fall into two categories: SSD-backed EBS volume types and HDD-backed EBS volume types.
Solid State Drives (SSD) Volume Types
1. General Purpose SSD (gp2) Volumes
General Purpose SSD (gp2) volumes are the most common types of EBS volumes. They were designed to be a cost-effective storage option for a wide variety of workloads.
Use cases: gp2 volumes cover system volumes, dev and test environments, and various low-latency apps.
Storage size: They come in sizes between 1GiB and 16GiB and provide very low latency, down to single-digit milliseconds.
Performance: gp2 volumes have a decent IOPS (starting from 100 and going all the way to 16000 IOPS) and a maximum throughput of 250MiB/s. You can combine multiple Amazon EBS volume types in a RAID to achieve even higher performance on a single instance.
The overall performance of gp2 volumes is directly related to their size; users get 3 IOPS per each GiB. This defines baseline performance as well as how quickly you gain the I/O credits which can be used for burst performance when needed.
Cost: gp2 volumes are fairly cheap, especially for the balanced performance they provide. They are priced at $0.1 per GB per month of provisioned storage.
2. Provisioned EBS IOPS SSD (io1) Volumes
Provisioned IOPS SSD (io1) types of EBS volumes are a special type of volume created to fulfill the needs of very intensive I/O workloads that require very high throughput.
Use cases: They are useful for cases which are latency-sensitive, like large database workloads (e.g., MySQL, Cassandra, MongoDB, and Oracle) and critical business applications that need the kind of sustained performance gp2 volumes can’t achieve.
Storage size: Io1 volumes can store between 4GiB and 16TiB, and their IOPS can be as low as 100 or high as 64000 IOPS per volume with up to 1,000 MiB/s of throughput.
Performance: While the performance of gp2 volumes is dictated by volume size, the performance of provisioned IOPS SSD volumes can be set during creation time. It is limited by a maximum IOPS to volume size ratio of 50:1.
Cost: $0.125 per GB per month of provisioned storage and $0.065 per provisioned IOPS per month.
Hard Disk Drives (HDD) Volume Types
3. Throughput Optimized HDD (st1) Volumes
Throughput Optimized HDD (st1) volumes are a type of volume that offers low-cost storage while fulfilling the need for sequential workloads that require more throughput than IOPS.
Use cases: When working with data warehouses, log processing, ETL (extract, transform, load) or AWS EMR, this is a volume type to look into. Keep in mind that this AWS EBS volume type cannot be used as a boot volume.
Storage size: st1 volumes can range in size between 500GiB and 16TiB, and they allow for 500 MiB/s of throughput per volume with 500 IOPS.
Performance: st1, like gp2, relies on burstable performance, and volume size will be the main factor when calculating baseline performance.
Cost: st1 volumes come with a lower price tag: $0.045 per GB per month of provisioned storage.
4. Cold HDD (sc1) Volumes
Cold HDD (sc1) volumes, like st1 volumes, provide low-cost storage for workloads that rely on throughput rather than IOPS.
Use cases: sc1 volumes are primarily used for large amounts of data that is infrequently accessed, or in cases where the cost of storage is the most important factor.
Storage size: sc1 volumes come in sizes between 500GiB and 16TiB
Performance: sc1 volumes provide up to 250 IOPS and 250MiB/s of throughput per volume. sc1, just like st1, cannot be used as a boot volume and relies on burstable performance.
Cost: sc1 volumes are the cheapest option available, costing only $0.025 per GB per month of provisioned storage.
5. EBS GP3 Volumes
SSD (gp3) volumes are the newest version of EBS General Purpose volumes. They provide better performance at a discount compared to gp2 volumes (up to 20% per GB). These volumes are suitable for predictable workloads requiring baseline performance of 3000 IOPS.
Use cases: gp3 volumes are used for medium-sized databases like Oracle and Microsoft SQL Server, virtual desktops, boot volumes, and interactive latency-sensitive applications. They are suitable for development and testing environments.
Storage size: gp3 volumes offer the same capacity as gp2, between 1GiB and 16GiB.
Performance: gp3 volumes support throughput of up to 1000 MiB/second per volume. They support up to 16000 IOPS per volume at 64 KiB per I/O (compared to just 16 KiB per I/O for gp2 volumes).
Cost: gp3 volumes are priced at $0.08 per GB-month of storage, with 3,000 free IOPs and 125 MB/second throughput. Beyond these limits, costs include $0.005 per IOPS-month and $0.04 per MB/second-month throughput.
- Choose gp3 for predictable workloads with IOPS needs: gp3 volumes offer better baseline performance and are cheaper than gp2, making them ideal for workloads that require predictable IOPS without the need for burst performance.
- Select instance types that complement your volume choice: Ensure your EC2 instance type supports the IOPS and throughput of your EBS volume. For example, high IOPS io1 volumes need to be paired with EC2 instances that can handle the required network bandwidth, such as M5 or C5 instances.
- Leverage io1/io2 for latency-sensitive databases: For high-performance databases (like Oracle or MySQL) where low latency is crucial, use io1 or io2 volumes. They offer configurable IOPS independent of volume size, up to 64,000 IOPS, which is critical for transaction-heavy applications.
- Monitor volume performance with CloudWatch: Set up CloudWatch alarms to track key metrics like IOPS, latency, and throughput. This helps identify whether your selected volume type is performing optimally, allowing for timely adjustments.
- Automate backup policies with lifecycle management: Use N2WS or AWS Backup to automate snapshot backups of EBS volumes, especially before resizing or modifying them. Leverage lifecycle policies to move snapshots to cheaper storage tiers (e.g., S3 Glacier).
6. Previous Generation Magnetic Volumes
Previous generation magnetic volumes, also known as Standard volumes, were the original EBS offering before the introduction of SSD and HDD-backed volumes. These volumes were designed to provide a balance of cost and performance for applications with moderate IOPS requirements. However, they are now considered outdated and are typically not recommended for new applications.
Use cases: Standard magnetic volumes provide a storage option for applications that do not require high throughput or IOPS. They are suitable for workloads where data is accessed infrequently and where performance is not a critical factor. These volumes can be used for scenarios such as backups, archival storage, and data that is accessed less frequently.
Storage size: They are available in sizes ranging from 1 GiB to 1 TiB. The performance of these volumes does not scale with size, which limits their effectiveness for larger workloads.
Performance: Standard magnetic volumes offer a maximum throughput of 40–90 MiB/s and can handle up to 200 IOPS per volume.
Cost: Magnetic volumes are one of the more cost-effective options, priced at $0.05 per GB per month of provisioned storage.
AWS EBS Volume Types Summary Table
The table below provides a quick comparison of the AWS EBS pricing and EBS volume types:
| Volume Type | General Purpose SSD (gp2) | Provisioned IOPS SSD (io1) | Throughput Optimized HDD (st1) | Cold HDD (sc1) | General Purpose SSD (gp3) |
| Uses | General purpose SSD volume that balances performance and price; used for low-latency app, dev and test environments | Highest-performance SSD volume, designed for mission-critical, low-latency, or high-throughput applications; used for large databases, and critical business applications | Low-cost HDD volume designed for throughput-intensive workloads; used for log processing, data warehouses, and streaming workloads | Lowest cost HDD volume designed for infrequently accessed data; used as a cheap storage solution | Suitable for predictable workloads requiring baseline performance of 3000 IOPS. |
| Volume Size | 1GiB—16TiB | 4GiB—16TiB | 500GiB—16TiB | 500GiB—16TiB | 1GiB—16TiB |
| Max Throughput per Volume | 250MiB/s | 1000MiB/s | 500MiB/s | 250MiB/s | up to 1000 MiB/s |
| Max IOPS per Volume | 16000 | 64000 | 500 | 250 | 16000 |
| Cost | $0.1 per GB | $0.125 per GB + $0.065 per IOPS | $0.045 per GB | $0.025 per GB | $0.08 per GB* |
What Are Instance Store Volumes?
Instance store volumes are a special block-level storage option that can be used on AWS. Unlike EBS volumes, which are network attached, these are physically attached to the host computer. They are meant to serve as temporary storage solutions only, used for caches, buffers, and other ephemeral data.
The lifetime of the instance store volume depends directly on the instance to which it is attached. If you reboot the instance, the data will persist; but, if you stop the instances, terminate them, or even change the instance type, your data will be lost.
Instance store volumes can actually provide very high performance, delivering high random I/O which can be good for low-latency workloads. They can even outperform EBS volumes in writes and uncached reads.
Instance store volumes come with no individual cost; instead, they are included as part of the instance’s usage cost. Like EBS types, these also come with specific instance types—usually specialized ones with higher price tags.
For example, the i3 family (starting at $0.156 per hour), a storage-optimized instance designed for I/O performance, uses instance store volumes for its workloads.
High-performance, GPU-backed instances like g3 ($1.14 per hour) and memory-optimized instances meant for in-memory applications such as x1 (a very expensive instance with its lowest possible cost at $6.669 per hour) rely on instance store volumes. They all benefit from the great performance that these ephemeral, locally-attached volumes provide.
How to Choose Amazon EBS Volume Types
Here are key considerations for selecting an Amazon EBS volume type.
Durability
All Amazon EBS volumes are designed with high durability in mind, featuring an annual failure rate (AFR) of between 0.1% and 0.2%. This high level of durability is achieved through data replication within the same Availability Zone (AZ). While durability is consistent across different EBS volume types, ensuring that your volumes are within the same AZ as your EC2 instances is crucial to maintaining data integrity and availability.
Volume size
The size of the volume is a critical factor in determining the appropriate EBS type. General Purpose SSD (gp2) and Provisioned IOPS SSD (io1) volumes offer flexibility, supporting sizes from 1 GiB to 16 TiB. Throughput Optimized HDD (st1) and Cold HDD (sc1) volumes cater to larger datasets, starting at 500 GiB and extending up to 16 TiB. The volume size not only affects storage capacity but also performance; for example, gp2 volumes provide better IOPS with larger sizes, making them ideal for scaling applications.
Maximum IOPS per volume
Input/output operations per second (IOPS) is a critical performance metric, especially for transactional and database applications. Provisioned IOPS SSD (io1) volumes offer the highest IOPS, reaching up to 64,000 IOPS per volume. This makes them suitable for high-performance databases and critical business applications.
General Purpose SSD (gp2) volumes offer up to 16,000 IOPS, balancing performance and cost for a wide range of applications. HDD volumes, such as st1 and sc1, are designed for lower IOPS requirements, providing up to 500 and 250 IOPS, respectively, and are more suited for sequential workloads.
Maximum throughput per volume
Throughput, measured in MiB/s, is essential for applications that handle large, sequential data transfers. Provisioned IOPS SSD (io1) volumes provide the highest throughput, up to 1,000 MiB/s, making them ideal for data-intensive applications.
Throughput Optimized HDD (st1) volumes offer up to 500 MiB/s, catering to applications like log processing and big data workloads. General Purpose SSD (gp2) volumes provide up to 250 MiB/s, suitable for a broad range of applications, while Cold HDD (sc1) volumes, designed for infrequent access, also offer up to 250 MiB/s.
Support for Amazon EBS Multi-Attach
Amazon EBS Multi-Attach allows multiple EC2 instances to access an EBS volume simultaneously, enhancing availability and redundancy. This feature is currently supported only by Provisioned IOPS SSD (io1) volumes.
Multi-Attach is particularly beneficial for clustered applications that require shared storage and can improve fault tolerance and reduce latency in distributed systems.
Ability to Run as Boot Volume
Not all EBS volumes can serve as boot volumes. Both General Purpose SSD (gp2) and Provisioned IOPS SSD (io1) volumes can be used as boot volumes, providing the necessary performance and reliability to start and run instances.
Throughput Optimized HDD (st1) and Cold HDD (sc1) volumes cannot be used as boot volumes. When selecting a boot volume, consider the performance requirements of your operating system and startup applications to ensure quick boot times and smooth operation.
Leveraging EBS Volumes for AWS Backup with N2WS
Selecting the right Amazon EBS volume type is just one part of ensuring optimal performance and reliability for your applications. EBS volumes are designed with an annual failure rate (AFR) of between 0.1% and 0.2%. This fact underscores the necessity of having a robust backup and recovery tool. This is where N2WS Backup & Recovery comes into play.
Why Choose N2WS for AWS Backup?
N2WS Backup & Recovery is a leading solution for cloud-native backup and disaster recovery, specifically optimized for AWS. Here are some reasons why integrating N2WS with your EBS volumes can enhance your data protection strategy:
1. Automated, Reliable Backups N2WS provides automated backup policies that ensure your data is regularly and securely backed up without manual intervention. With support for all EBS volume types, you can schedule backups that align with your operational needs and compliance requirements.
2. Fast and Efficient Recovery In the event of data loss or corruption, N2WS enables rapid recovery of your EBS volumes. You can restore entire volumes or individual files with minimal downtime, ensuring business continuity.
3. Cost Optimization N2WS offers features like incremental backups and lifecycle management, which help optimize storage costs. By only backing up changed data and automatically moving older backups to more cost-effective storage tiers, you can save on AWS storage expenses.
4. Enhanced Security and Compliance With N2WS, you can perform DR backups of encrypted volumes into other regions or accounts for added security. It also support AWS GovCloud, making it ideal for government agencies and enterprises with strict regulatory needs.
5. Comprehensive Reporting and Alerts N2WS provides detailed reporting and alerting capabilities, giving you visibility into your backup operations. You can generate reports to demonstrate compliance and receive alerts to stay informed about the status of your backups.
How to Get Started with N2WS
- Install N2WS Backup & Recovery: Available in AWS Marketplace, N2WS can be easily deployed within your AWS environment. Choose the appropriate configuration that fits your needs and budget.
- Configure Backup Policies: Define backup schedules and retention policies that align with your business requirements. N2WS supports flexible backup configurations to suit various workloads and data protection strategies.
- Monitor and Manage Backups: Use the N2WS dashboard to monitor backup activities and ensure everything is running smoothly. Leverage reporting and alerting features to stay on top of your data protection status.
- Test Recovery Processes: Regularly test your recovery procedures to ensure you can quickly restore data when needed. N2WS simplifies recovery testing, making it easy to verify that your backups are reliable.
Protecting your AWS environment is critical to maintaining business continuity and data integrity. With N2WS Backup & Recovery, you can ensure your EBS volumes are backed up securely and that your data is always recoverable. Get started with N2WS Backup & Recovery today by visiting the AWS Marketplace and experience the peace of mind that comes with knowing your data is protected by one of the leading solutions in the industry.
Related content: check out our post on aws backup vs snapshot
