HAQM EBS features

HAQM EBS allows you to create storage volumes and attach them to HAQM EC2 instances. Once attached, you can create a file system on top of these volumes, run a database, or use them in any other way you would use block storage. HAQM EBS volumes are placed in a specific Availability Zone where they are automatically replicated to protect you from the failure of a single component. All EBS volume types offer durable snapshot capabilities and are designed for high availability.

HAQM EBS provides a range of options that allow you to optimize storage performance and cost for your workload. These options are divided into two major categories: SSD-backed storage for transactional workloads, such as databases and boot volumes (performance depends primarily on IOPS), and HDD-backed storage for throughput intensive workloads, such as MapReduce and log processing (performance depends primarily on MB/s).

Our highest performance io2 Block Express volume enables SAN-like performance in the cloud. Block Express is a next-generation storage server architecture that provides the highest block storage performance without the cost or hassle of having to procure, scale, and maintain expensive on-premises SANs. With io2 Block Express, you can achieve sub-millisecond latency and provision a single io2 Block Express volume with up to 256,000 IOPS, 4,000 MB/second throughput, and 64 TB of capacity—a 4x increase in performance, throughput, and capacity than existing io1 volumes. Io2 Block Express volumes are ideal for the largest, most I/O-intensive, mission-critical deployments of Oracle databases, SAP HANA, Microsoft SQL Server, InterSystems database, and SAS Analytics.

SSD-backed volumes include the highest performance Provisioned IOPS SSD (io2 Block Express and io1) for latency-sensitive transactional workloads and General Purpose SSD (gp3 and gp2) that balance price and performance for a wide variety of transactional data. HDD-backed volumes include Throughput Optimized HDD (st1) for frequently accessed, throughput intensive workloads and the lowest cost Cold HDD (sc1) for less frequently accessed data.

Elastic Volumes is a feature of HAQM EBS that allows you to dynamically increase capacity, tune performance, and change the type of live volumes with no downtime or performance impact. This allows you to easily right-size your deployment and adapt to performance changes.

HAQM EBS volumes are designed to be highly available, reliable, and durable. At no additional charge to you, HAQM EBS volume data is replicated across multiple servers in an Availability Zone to prevent the loss of data from the failure of any single component. For more details, see the HAQM EBS Service Level Agreement.

HAQM EBS offers a higher durability volume (io2 Block Express), that is designed to provide 99.999% durability with an annual failure rate (AFR) of 0.001%, where failure refers to a complete or partial loss of the volume. For example, if you have 100,000 EBS io2 Block Express volumes running for 1 year, you should expect only one io2 Block Express volume to experience a failure. This makes io2 Block Express ideal for business-critical applications such as SAP HANA, Oracle, Microsoft SQL Server and IBM DB2 that will benefit from higher uptime. Io2 Block Express volumes are 2000 times more reliable than typical commodity disk drives, which fail with an AFR of around 2%. All other HAQM EBS volumes are designed to provided 99.8%-99.9% durability with an AFR of between 0.1% - 0.2%,

EBS also supports a snapshot feature, which is a good way to take point-in-time backups of your data. To learn more about HAQM EBS Snapshots and how to take point-in time backups of your volumes please visit here.

For an additional low, hourly fee, customers can launch certain HAQM EC2 instance types as EBS-optimized instances. EBS-optimized instances enable EC2 instances to fully use the IOPS provisioned on an EBS volume.

EBS-optimized instances deliver dedicated throughput between HAQM EC2 and HAQM EBS, with options between 500 and 80,000 Megabits per second (Mbps) depending on the instance type used. The dedicated throughput minimizes contention between HAQM EBS I/O and other traffic from your EC2 instance, providing the best performance for your EBS volumes.

EBS-optimized instances are designed for use with all HAQM EBS volume types.

For more information about the instance types that can be launched as EBS-Optimized instances, see HAQM EC2 Instance Types.

Provisioned IOPS SSD (io2 Block Express and io1) volumes

Provisioned IOPS SSD volumes are designed to deliver a maximum of 256,000 IOPS, 4,000 MB/s of throughput, and 64 TiB in size per volume. Io2 Block Express is the latest generation of the Provisioned IOPS SSD volumes that delivers 4x higher throughput, IOPS, and capacity than io1 volumes, along with sub-millisecond latency. Io2 Block Express provides the highest block storage performance for the largest, most I/O-intensive, mission-critical deployments of Oracle, Microsoft SQL Server, SAP HANA, and SAS Analytics.

When attached to Nitro System-based EC2 instances, io2 Block Express provides sub-millisecond latency, while io1 is designed to achieve single-digit millisecond latencies. Both io1 and io2 Block Express deliver the provisioned performance 99.9% of the time with a durability of 99.999%. This makes io2 Block Express ideal for performance-intensive, business-critical applications that will benefit from higher uptime. Io2 Block Express volumes support Multi-Attach with I/O fencing, which allows customers to attach an io2 Block Express volume to up to sixteen Nitro-based EC2 instances within the same Availability Zone. In addition, Fast Snapshot Restore and Elastic Volumes are also supported in all Provisioned IOPS SSD volumes. For more details on pricing, please visit the pricing page. For more information about instance types that can be launched as EBS-optimized instances, see HAQM EC2 Instance Types. For more information about HAQM EBS performance guidelines, see Increasing EBS Performance. Learn more »

General purpose SSD (gp3 and gp2) volumes

General-purpose volumes are backed by solid-state drives (SSDs) and are suitable for a broad range of transactional workloads, virtual desktops, medium sized single instance databases, latency sensitive interactive applications, dev/test environments, and boot volumes. HAQM gp3 volumes are the latest generation of general-purpose SSD-based EBS volumes that enable customers to provision performance independent of storage capacity, while providing up to 20% lower pricing per GB than existing gp2 volumes. The new gp3 volumes deliver a baseline performance of 3,000 IOPS and 125 MB/s at any volume size. Customers looking for higher performance can scale up to 16,000 IOPS and 1,000 MB/s for an additional fee. Both gp3 and gp2 volumes are designed to offer single-digit millisecond latency and deliver the provisioned performance 99% of the time. We advise using io2 Block Express volumes if you require more IOPS than gp3 can offer, have a workload where low latency is essential, or require improved performance consistency or durability.

To maximize the performance of gp3, we recommend using EBS-optimized EC2 instances.

Throughput optimized HDD (st1) volumes

ST1 is backed by hard disk drives (HDDs) and is ideal for frequently accessed, throughput intensive workloads with large datasets and large I/O sizes, such as MapReduce, Kafka, log processing, data warehouse, and ETL workloads. These volumes deliver performance in terms of throughput, measured in MB/s, and include the ability to burst up to 250 MB/s per TB, with a baseline throughput of 40 MB/s per TB and a maximum throughput of 500 MB/s per volume. ST1 is designed to deliver the expected throughput performance 99% of the time and has enough I/O credits to support a full-volume scan at the burst rate. To maximize the performance of st1, we recommend using EBS-optimized EC2 instances.

Cold HDD (sc1) volumes

SC1 is backed by hard disk drives (HDDs) and provides the lowest cost per GB of all EBS volume types. It is ideal for less frequently accessed workloads with large, cold datasets. Similar to st1, sc1 provides a burst model: these volumes can burst up to 80 MB/s per TB, with a baseline throughput of 12 MB/s per TB and a maximum throughput of 250 MB/s per volume. For infrequently accessed data, sc1 provides extremely inexpensive storage. SC1 is designed to deliver the expected throughput performance 99% of the time and has enough I/O credits to support a full-volume scan at the burst rate. To maximize the performance of sc1, we recommend using EBS-optimized EC2 instances.

HAQM EBS provides the ability to save point-in-time snapshots of your volumes to HAQM S3. HAQM EBS Snapshots are stored incrementally: only the blocks that have changed after your last snapshot are saved, and you are billed only for the changed blocks. If you have a device with 100 GB of data but only 5 GB has changed after your last snapshot, a subsequent snapshot consumes only 5 additional GB and you are billed only for the additional 5 GB of snapshot storage, even though both the earlier and later snapshots appear complete.

When you delete a snapshot, you remove only the data not needed by any other snapshot. All active snapshots contain all the information needed to restore the volume to the instant at which that snapshot was taken. The time to restore changed data to the working volume is the same for all snapshots.

Snapshots can be used to instantiate multiple new volumes, expand the size of a volume, or move volumes across Availability Zones. When a new volume is created, you may choose to create it based on an existing HAQM EBS Snapshot. In that scenario, the new volume begins as an exact replica of the snapshot.

The following are key features of HAQM EBS Snapshots:

• Direct read access of EBS Snapshots - Customers can use EBS direct APIs for Snapshots to read data off snapshots and identify differences between two EBS Snapshots without needing to create EBS volumes and EC2 instances. EBS direct APIs for Snapshots enable backup partners to track incremental changes on EBS volumes more efficiently, providing faster backup times and more granular recovery point objectives (RPOs) to customers at a lower cost. For more information, see the EBS direct APIs for Snapshots technical documentation and pricing page.
• Creating EBS Snapshots from any block storage - Using EBS direct APIs, you can create EBS Snapshots directly from any block storage data, regardless of where it resides, including data on-premises, and quickly recover into EBS volumes. This allows you to meet your disaster recovery objectives in AWS at lower costs. For more information, see the EBS direct APIs for Snapshots technical documentation and pricing page.
• Immediate access to HAQM EBS volume data - After a volume is created from a snapshot, there is no need to wait for all of the data to transfer from HAQM S3 to your HAQM EBS volume before your attached instance can start accessing the volume. HAQM EBS Snapshots implement lazy loading, so that you can begin using them right away.
• Instant full performance on EBS volumes restored from snapshots - For an additional hourly charge, you can enable Fast Snapshot Restore (FSR) capability for low latency access to data restored from snapshots. EBS volumes restored from FSR-enabled snapshots instantly receive their full performance. For more information, see the FSR technical documentation and pricing page.
• Automating creation of application-consistent snapshots - With HAQM Data Lifecycle Manager support for pre-script and post-script automation, you can automate the creation of application-consistent EBS Snapshots of your self-managed databases and VSS Backups. The capability will integrate with AWS Systems Manager Agent (SSM Agent) and SSM documents to automate actions before and after snapshots are initialized. To create application-consistent snapshots and find out the workloads supported, see the technical documentation. 
• Resizing HAQM EBS volumes - There are two methods that can be used to resize an HAQM EBS volume. If you create a new volume based on a snapshot, you can specify a larger size for the new volume. With the Elastic Volumes feature you can dynamically grow live volumes without the use of snapshots. Make certain that your file system and application supports resizing a device.
• Sharing HAQM EBS Snapshots - HAQM EBS Snapshots’ shareability makes it easy for you to share data with your co-workers or others in the AWS community. Authorized users can create their own HAQM EBS volumes based on your HAQM EBS shared snapshots; your original snapshot remains intact. You can also restrict public access to snapshots in an account by enabling Block Public Access for EBS Snapshots. If you choose, you can also make your data available publicly to all AWS users. For more information about how to share snapshots, see Modifying Snapshot Permissions.
• Locking HAQM EBS Snapshots - You can lock your HAQM EBS Snapshots to protect them against accidental or malicious deletions, or store them in WORM (write-once-read-many) format for a specific duration to comply with regulatory requirements. While a snapshot is locked, it can't be deleted by any users, regardless of their IAM permissions. For more information, see Locking Snapshots.
• Copying HAQM EBS Snapshots across AWS Regions - HAQM EBS’s ability to copy snapshots across AWS Regions makes it easier to leverage multiple AWS Regions for geographical expansion, data center migration and disaster recovery. You can copy any snapshot accessible to you: snapshots you created; snapshots shared with you; and snapshots from the AWS Marketplace, VM Import/Export, and AWS Storage Gateway. For more information, see Copying an HAQM EBS Snapshot.
• EBS Snapshots Archive - EBS Snapshots Archive is a lower storage cost tier which stores a full copy of your point-in-time EBS Snapshots. Unlike an EBS Snapshot of a volume which is incremental, a snapshot archive is “full” since it contains all the blocks written into the volume at the moment the snapshot was taken. To recreate a volume from EBS Snapshots Archive, you restore the EBS Snapshot to the standard tier, and then create an EBS volume from the restored snapshot.
• Instant full performance on EBS volumes restored from snapshots - For an additional hourly charge, you can enable Fast Snapshot Restore (FSR) capability for low latency access to data restored from snapshots. You can enable FSR on snapshots you own or those shared with you. EBS volumes restored from FSR-enabled snapshots instantly receive their full performance. For more information, see the FSR technical documentation and pricing page.

HAQM Data Lifecycle Manager for EBS Snapshots provides a simple, automated way to back up data stored on EBS volumes by ensuring that EBS Snapshots are created and deleted on a custom schedule. You no longer need to use scripts or other tools to comply with data backup and retention policies specific to your organization or industry. With the support for custom script automation, you can set lifecycle policies to automate pre-scripts and post-scripts before and after the creation of application-consistent EBS Snapshots for self-managed databases running on EC2 instances.

With Data Lifecycle Manager, you can be sure that snapshots are cleaned up regularly and keep costs under control. Simply tag your EBS volumes and start creating Lifecycle policies for creation and management of backups. Use CloudWatch Events to monitor your policies and ensure that your backups are being created successfully.

HAQM EBS encryption offers seamless encryption of EBS data volumes, boot volumes and snapshots, eliminating the need to build and manage a secure key management infrastructure. EBS encryption enables data at rest security by encrypting your data volumes, boot volumes and snapshots using HAQM-managed keys or keys you create and manage using the AWS Key Management Service (KMS). In addition, the encryption occurs on the servers that host EC2 instances, providing encryption of data as it moves between EC2 instances and EBS data and boot volumes. For more information, see HAQM EBS encryption in the HAQM EC2 User Guide.

Access to HAQM EBS volumes is integrated with AWS Identity and Access Management (IAM). IAM enables access control to your HAQM EBS volumes. For more information, see AWS Identity and Access Management.

on this page GB = 1024^3 bytes

Elastic Volumes is a feature that allows you to easily adapt your volumes as the needs of your applications change. Elastic Volumes allows you to dynamically increase capacity, tune performance, and change the type of any new or existing current generation volume with no downtime or performance impact. Easily right-size your deployment and adapt to performance changes.

Simply create a volume with the capacity and performance needed today knowing you have the ability to modify your volume configuration in the future, saving hours of planning cycles.

By using HAQM CloudWatch with AWS Lambda, you can automate volume changes to meet the changing needs of your applications.

The Elastic Volumes feature makes it easier to adapt your resources to changing application demands, giving you confidence that you can make modifications in the future as your business needs change.

Customers can enable Multi-Attach on an EBS Provisioned IOPS volume to allow a volume to be concurrently attached to up to sixteen Nitro-based EC2 instances within the same Availability Zone. Multi-Attach makes it easier to achieve higher application availability for applications that manage storage consistency from multiple writers. Each attached instance has full read and write permission to the shared volume. Multi-Attach on a Provisioned IOPS io2 Block Express volume supports NVMe reservations. There is no additional fee to enable Multi-Attach.

To learn more, see Multi-Attach technical documentation.

Torn Write Prevention (TWP) ensures that full 16KiB write operations are persisted to the block storage. With this feature, customers can turn off the double write operation that MySQL and MariaDB databases perform for increased database write throughput. These customers can increase the number of transactions processed per second (TPS) by up to 30% without having to over-provision or scale up their clusters, thereby reducing storage cost. By eliminating the second write operation, TWP decreases the write latency and variability in the number of TPS by up to 50%, enabling customers to improve their Service Level Agreement (SLA) without compromising the resiliency of their workloads.

TWP supports all HAQM EBS volumes attached to EC2 Nitro-based instances. To learn more, see Torn Write Prevention technical documentation.

With Provisioned Rate for Volume Initialization, you can launch hundreds of EC2 instances from EBS-backed HAQM Machine Images or EBS volumes from EBS Snapshots at the same time, knowing that the attached EBS volumes will be fully performant within a predictable amount of time. You can use the feature by setting the volume initialization rate, and the snapshot blocks are downloaded from HAQM S3 and written to the volume at the specified rate after creation.

To learn more, visit the Provisioned Rate for Volume Initialization technical documentation.