![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/EBS.jpg\")
<\/p>\nElastic Block Store (EBS) is a storage service that creates and manages volumes based on four underlying storage types. Volumes are persistent, can be attached and removed from EC2 instances, and are replicated within a single AZ.<\/p>\n
<\/p>\n
<\/p>\n
Volume Types<\/p>\n
To protect against AZ failure, EBS snapshots (to S3) can be used. Data is replicated across AZs in the region and (optionally) internationally.<\/p>\n
<\/p>\n
Legacy non-EBS-optimized instances used a shared networking path for data and storage communications.<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/EBSnon-optimized.jpg\")
<\/p>\n
EBS-optimized mode, which was historically optional and is now the default, adds optimizations and dedicated communication paths for storage and traditional data networking. This allows consistent utilization of both \u2014 and is one required feature to support higher performance storage.<\/p>\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/EBSoptimized.jpg\")
<\/p>\n
<\/p>\n
Key Features<\/span><\/p>\n – A file system must be created<\/p>\n – RAID is supported if the OS supports it<\/p>\n – Automatically replicated in that zone<\/p>\n – Protects against hardware failure, not high availability<\/p>\n <\/p>\n Persistence<\/p>\n – Terminating the instance will not terminate the volume<\/p>\n – This behavior is changed by setting <\/p>\n Snapshots<\/p>\n <\/p>\n EBS snapshots<\/strong> are a point-in-time backup of an EBS volume stored in 53. The initial snapshot is a full copy of the volume. Future snapshots only store the data changed since the last snapshot.<\/p>\n Snapshots can be used to create new volumes and are a great way to move or copy instances between AZs. When creating a snapshot of the root\/boot volume of an instance or busy volume, it’s recommended the instance is powered off, or disks are “flushed.”<\/p>\n Snapshots can be copied between regions, shared, and automated using Data Lifecycle Manager (DLM).<\/p>\n <\/p>\n Performance<\/span><\/p>\n EBS uses IOPS (input\/output operations per second) as a performance measure, measured in KiB (kibibytes = 1024 bytes).<\/p>\n Burst Buckets:\u00a0 <\/em>Allows an EBS volume to “burst” above the baseline performance Volumes earn credits Credits are then spent whenever the volume needs more performance There is a maximum number of credits<\/p>\n \u2022 Not available for Provisioned IOPS SSD (I01)<\/p>\n \u2022 Reported as a <\/p>\n SSD<\/strong> <\/span><\/p>\n Consistent performance with sequential and random operations<\/p>\n Good for frequent read\/writes using small I\/O sizes (10PS) IOPS measured with 256 KiB I\/O size (chunks of data)<\/p>\n \u2022 One 1024 KiB operation = 4 IOPS<\/p>\n \u2022 Four 64 KiB sequential operations = 1 IOPS<\/p>\n \u2022 Four 64 KiB random operations = 4 IOPS<\/p>\n <\/p>\n General Purpose SSD Volumes ( gp2 )<\/strong><\/p>\n \u2022 5.4 million credits to start (max 3,000 IOPS for 30 minutes)<\/p>\n \u2022 Credits earned at 3 IOPS per GiB of volume size<\/p>\n \u2022 Maximum credits = 5.4 million<\/p>\n \u2022 Volumes greater than 1,000 GiB never deplete (baseline = burst max)<\/p>\n <\/p>\n Provisioned IOPS SSD volumes ( iol )<\/strong><\/p>\n <\/p>\n <\/p>\n HDD <\/strong><\/span><\/p>\n Optimal performance with large and sequential operations \u2022 One 1024 KiB operation = 1 IOPS<\/p>\n \u2022 Eight 128 KiB sequential operations = 1 IOPS<\/p>\n \u2022 Eight 128 KiB random operations = 8 IOPS<\/p>\n <\/p>\n Throughput Optimized HDD volumes ( stl<\/span> )<\/strong><\/p>\n Cold HDD volumes ( scl<\/span> )<\/strong><\/p>\n Magnetic volumes<\/strong><\/p>\n <\/p>\n Join multiple gp2, lot st1, or sc1 volumes together in a RAID 0 configuration (stripe set) to use the available bandwidth, improving throughput.<\/p>\n <\/p>\n Cloudwatch Metrics<\/span><\/p>\n \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 \u2022 <\/p>\n EBS Status Checks<\/p>\n <\/p>\n Resizing or changing root volumes<\/span><\/p>\n Modify the size, IOPS, or type of an EBS volume For Nitro-based instances (e.g. t3.micro):<\/p>\n For T2 instances:<\/p>\n <\/p>\n The “Automated” Method:<\/p>\n <\/p>\n Ensuring data durability upon EC2 instance termination<\/span><\/p>\n – Uncheck “Delete on Termination” in the console: Also a CLI parameter with run-instances<\/p>\n – Create a snapshot before deletion<\/p>\n – We can create a separate volume and attach to the instance:\u00a0 Attached volumes persist when the instance is terminated<\/p>\n","protected":false},"excerpt":{"rendered":" Elastic Block Store (EBS) is a storage service that creates and manages volumes based on four underlying storage types. Volumes are persistent, can be attached and removed from EC2 instances, and are replicated within a single AZ.<\/p>\n","protected":false},"author":1,"featured_media":2655,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[77],"tags":[],"_links":{"self":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/2646"}],"collection":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/comments?post=2646"}],"version-history":[{"count":6,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/2646\/revisions"}],"predecessor-version":[{"id":3342,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/posts\/2646\/revisions\/3342"}],"wp:featuredmedia":[{"embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/media\/2655"}],"wp:attachment":[{"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/media?parent=2646"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/categories?post=2646"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/miro.borodziuk.eu\/index.php\/wp-json\/wp\/v2\/tags?post=2646"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\n
\n
DeleteOnTermination<\/code> attribute to false<\/p>\n\n
![\"\"](\"http:\/\/miro.borodziuk.eu\/wp-content\/uploads\/EBSSnapshot.jpg\")
<\/p>\nBurstBalance<\/code> metric in CloudWatch<\/p>\n\n
\n
\nGood for large streaming workloads (throughput) IOPS measured with 1024 KiB I\/O size (chunks of data)<\/p>\n\n
\n
\n
\n
VolumeReadBytes, VolumeWriteBytes<\/code><\/p>\nVolumeReadOps, VolumeWriteOps<\/code><\/p>\nVolumeTotalReadTime, VolumeTotalWriteTime<\/code><\/p>\nVolumeIdleTime<\/code><\/p>\n VolumeQueueLength<\/code><\/p>\n\n
VolumeThroughputPercentage <\/code><\/p>\nVolumeConsumedReadWri teOps<\/code><\/p>\n\n
BurstBalance<\/code><\/p>\n\n
\nThe Manual Method:<\/p>\n\n
lsblk\r\ndf -h\r\nsudo file -s \/dev\/nvme?n*\r\nsudo growpart \/dev\/nvmeenl 1\r\nsudo xfs_growfs -d \/<\/pre>\n
sudo file -s \/dev\/xvd*\r\nsudo growpart \/dev\/xvda 1\r\nsudo resize2fs \/dev\/xvda\r\n<\/pre>\n
\n
\n