Amazon EBS
Amazon EBS Snapshot
You can back up the data on your Amazon EBS volumes to Amazon S3 by taking point-in-time snapshots. Snapshots are incremental backups, which means that only the blocks on the device that have changed after your most recent snapshot are saved. This minimizes the time required to create the snapshot and saves on storage costs by not duplicating data. When you delete a snapshot, only the data unique to that snapshot is removed. Each snapshot contains all of the information that is needed to restore your data (from the moment when the snapshot was taken) to a new EBS volume.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSSnapshots.html
EBS volumes provide durable block-level storage for use with EC2 instances in the AWS cloud. Volumes are automatically replicated within Availability Zones for high availability and durability.
Usage
EBS volumes are network-attached storage that persists independently from the running life of a single EC2 instance. After an EBS volume is attached to an EC2 instance, you can use the EBS volume similar to a physical hard drive -- typically by formatting it with the file system of your choice and using the file I/O interface provided by the instance operating system. Multiple EBS volumes can be attached to a single EC2 instance and it 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. Furthermore EBS provides the ability to save point-in-time snapshots of your volumes. Each separate volume can be configured as EBS General Purpose (SSD), Provisioned IOPS (SSD), Throughput Optimized (HDD), or Cold (HDD) as needed
The volumes types fall into two categories:
- SSD-backed volumes optimized for transactional workloads involving frequent read/write operations with small I/O size, where the dominant performance attribute is IOPS
- HDD-backed volumes optimized for large streaming workloads where throughput (measured in MiB/s) is a better performance measure than IOPS
Amazon EBS volume types - Amazon EBS
Durability & availability
Amazon EBS cloud service is designed to be highly available and reliable. As mentioned earlier EBS volumes data is replicated across multiple servers within availability zones. Taking snapshots of your EBS volumes increases the durability of the data stored on your EBS volumes. Furthermore, EBS volumes are designed for anAnnual Failure Rate (AFR)of between0.1 and 0.2 percent, where failure refers to a complete or partial loss of the volume, depending on the size and performance of the volume.
Security
IAM service enables access to EBS volumes, allowing you to specify who can access which EBS volumes. EBS encryption enables data-at-rest and data-in-motion security. It offers seamless encryption of both EBS boot volumes and data volumes as well as snapshots. Access control plus encryption offers a strong defense-in-depth security strategy for your data.
| Volume type | General Purpose SSD (gp2) | Provisioned IOPS SSD (io1) | Throughput Optimized HDD (st1) | Cold HDD (sc1) |
|---|---|---|---|---|
| Description | General purpose SSD volume that balances price and performance for a wide variety of workloads | Highest-performance SSD volume for mission-critical low-latency or high-throughput workloads | Low-cost HDD volume designed for frequently accessed, throughput-intensive workloads | Lowest cost HDD volume designed for less frequently accessed workloads |
| Use cases | Recommended for most workloads; System boot volumes; Virtual desktops; Low-latency interactive apps; Development and test environments; Critical business applications that require sustained IOPS performance, or more than 16,000 IOPS or 250 MiB/s of throughput per volume; Large database workloads, such as:; MongoDB; Cassandra; Microsoft SQL Server; MySQL; PostgreSQL; Oracle; Streaming workloads requiring consistent, fast throughput at a low price; Big data; Data warehouses; Log processing; Cannot be a boot volume; Throughput-oriented storage for large volumes of data that is infrequently accessed; Scenarios where the lowest storage cost is important; Cannot be a boot volume | |||
| Pricing | $0.114per GB-month of provisioned storage | $0.131per GB-month of provisioned storage AND$0.068per provisioned IOPS-month | $0.051per GB-month of provisioned storage | $0.029per GB-month of provisioned storage |
EBS Pricing - 100 GB - $11.4 per month
S3 Pricing - 100 GB - $2.5 per month
S3 Pricing - First 50 TB / Month - $0.025per GB
S3 Standard - Infrequent Access* - For long lived but infrequently accessed data that needs millisecond access - $0.019per GB
S3 Glacier** - For long-term backups and archives with retrieval option from 1 minute to 12 hours - $0.005per GB
S3 Glacier Deep Archive** - For long-term data archiving that is accessed once or twice in a year and can be restored within 12 hours - $0.002per GB
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html
Multi-Attach is now available on Amazon EBS Provisioned IOPS volume type, io2. Launched in August 2020, io2 is the newest generation of our Provisioned IOPS volume type designed for 99.999% durability (100x io1) and 500:1 IOPS:GiB (10x io1). Multi-Attach lets you share access to an EBS data volume between up to 16 Nitro-based EC2 instances within the same Availability Zone (AZ). Each attached instance has full read and write permission to the shared volume. Multi-Attach is intended to make it easier to achieve higher application availability for customers that want to deploy applications that manage storage consistency from multiple writers in shared storage infrastructure.
gp2 vs gp3
| Volume Type | gp3 | gp2 |
|---|---|---|
| Short Description | Lowest cost SSD volume that balances price performance for a wide variety of transactional workloads | General Purpose SSD volume that balances price performance for a wide variety of transactional workloads |
| Durability | 99.8% - 99.9% durability | 99.8% - 99.9% durability |
| Use Cases | Virtual desktops, medium sized single instance databases such as Microsoft SQL Server and Oracle, latency sensitive interactive applications, boot volumes, and dev/test environments | Virtual desktops, medium sized single instance databases such as Microsoft SQL Server and Oracle, latency sensitive interactive applications, boot volumes, and dev/test environments |
| API Name | gp3 | gp2 |
| Volume Size | 1 GB - 16 TB | 1 GB - 16 TB |
| Max IOPS/Volume | 16,000 | 16,000 |
| Max Throughput*/Volume | 1,000 MB/s | 250 MB/s |
| Max IOPS/Instance | 260,000 | 260,000 |
| Max Throughput/Instance | 12,500 MB/s | 7,500 MB/s |
| Price | $0.08/GB-month; 3,000 IOPS free and; $0.005/provisioned IOPS-month over 3,000;; 125 MB/s free and; $0.04/provisioned MB/s-month over 125 | $0.10/GB-month |
Migrate your Amazon EBS volumes from gp2 to gp3 and save up to 20% on costs | AWS Storage Blog
- It might take up to 24 hours for a new configuration to take effect, and in some cases more, such as when the volume has not been fully initialized. Typically, a fully used 1-TiB volume takes about 6 hours to migrate to a new performance configuration. Transitional volume performance will be no less than the source volume performance. If you are downgrading IOPS, transitional volume performance is no less than the target volume performance.
Changing RDS storage from gp2 to gp3 | AWS re:Post
- There is no downtime associated but always plan to make modifications at the time when clusters is expected to be least busy. There wouldn't be downtime, you may see “Storage Optimization” status.
gp2 to gp3 migration for Amazon RDS | by Rajesh Kantamani | Medium
Underutilized EBS
Neglecting Underutilized EBS Volumes: A Costly Oversight in AWS | by puggy | Medium
Is there a way to programmatically find unused EBS Volume usage? : r/aws
Decreasing Size
Can I reduce an over-sized EBS volume? | AWS re:Post