Elastic block store (EBS) Flashcards
What i Elastic block store (EBS), and what is it designed for?
EBS are storage volumes you can attach your EC2 instances to.
They can be viewed basically as a virtual harddisk where you can install operating systems, applications, data etc. And then you can attach them to your EC2 instance.
- It’s designed for mission-critical workloads
- It’s automatically replicated within a single availability zones to protect against hardware failures, meaning the “virtual disk” exist in multiple disks in multiple data centers.
- It’s very scaleable. You can increase capacity and chance the volume type with no downtime or performance impact to live systems.
What are the EBS volume types and the details about them?
- General purpose SSD (gp2)
- General purpose SSD (gp3)
- Provisioned IOPS SSD (io1)
- Provisioned IOPS SSD (io2)
- Throughput optimized HDD (st1)
- Cold HDD (SC1)
What are the stats of General purpose SSD (gp2)?
- 3 IOPS per GiB, up to a maximum of 16,000 IOPS per volume
- gp2 volumes smaller than 1 TB can burst up to 3,000 IOPS
- Good for boot volumes or development and test applications that are not latency sensitive.
What are the stats of General purpose SSD (gp3)?
- Predictable 3,000 IOPS baseline performance and 125 MiB/s regardless of volume size
- Ideal for applications that require high performance at a low cost, such as MySQL, Cassandra, virtual desktops, and Hadoop analytics.
- Customers looking for higher peformance can scale up to 16,000 IOPS and 1,000 MiB/s for an additional fee.
- The top performance of gp3 is 4 times faster than max throughput of gp2 volumes.
- The default use cases for gp2/3 is to inst
What are the stats of Provisioned IOPS SSD (io1)?
- Up to 64,000 IOPS per volume 50 IOPS per GiB.
- Use it if you need more than 16,000 IOPS
- Designed for I/O-intensive applications, large database, and latency-sensitive workloads
- This is the fast, but expensive option
What are the stats of the Provisioned IOPS SSD (io2)?
- Up to 500 IOPS per GiB up to 64,000 IOPS
- 99.999% durability instead of up to 99.9%
- I/O-instensive apps, large databases, and latency-sensitive workloads. Basically all applications that need high levels of durability.
What are the stats of the Throughput optimized HDD (st1)?
- Throughput optimized HDD (st1)
- It’s the old school harddrives
- Low cost HDD volumen
- Baseline throughput of 40 MB/s per TB
- Ability to burst up to 250 MB/s per TB
- Useful for frequently accessed, throughput-intensive workloads like Big data, data warehouses, ETL and log processing.
- Cost effective way to store mountains of data
- Cannot be a boot volume, and is only used generally for data work.
What are the stats of the Cold HDD (sc1)?
- The lowest cost options
- Baseline throughput of 12 MB/s per TB
- Ability to burst up to 80 MB/s per TB
- Max throughtput of 250 MV/s per volume
The use case if for applications that need the lowest cost and performance is not a factor.
cannot be a boot volume.
What are the difference between IOPS and Throughput?
- IOPS
- Measures the number of read and write operations per second.
- Important metrics for quick transactions, low-latency apps, transactional workloads
- The ability to action reads and writes very quickly.
- Choose provisioned IOPS SSD(io1 or io2)
- A use case example could be you a transactional database for transactions like in a webshop.
- Throughput
- Measures the number of bits read or written per second (MB/s).
- Important metrics for large datasets, large I/O sizes, complex queries.
- The ability to deal with large datasets and big data.
- Choose throughput optimized HDD (st1)
What are volumes?
Volumes are simply virtual hard disks. You need a minimum of 1 volume per EC2 instance.
This is called the root device volume, and is where your operatins system is installed like Windows and Linux.
What are snapshots?
- Snapshots exist on S3
- Snapshots are point in time
- When you take a snapshot, it’s a point-in-time copy of a volume - Snapshots are incremental
- Only the data that been changed since the last snapshot are moved to S3 - The first snapshot takes some time since there is no previous point-in-time.
- It’s recommended to stop your instance before you take a snapshot in case there is data that is not written to your EBS yet.
- If you take a snapshot of an encrypted EBS the snapshot will be encrypted automatically.
- You can share snapshots within the region they were created. To save to other regions you need to copy them to the destinations region first. This is handy way to move instances to other regions for instance.
How do you copy an instance across regions?
- Take a snapshot of the root volume of the instace .
- Copy that snapshot to the desired region
- Create an image of the copied snapshot in the new region.
- Create an instance based of that copied image.
How is EBS encryption handled?
EBS encrypts your volume with a data key using the industry-standard AES-256 algorithm.
Amazon EBS encryption uses AWS key management service (AWS KMS) customer master keys (CMK) when creating encrypted volumes and snapshots.
When it comes to management of the keys you can both manage that yourself or you can have amazon manage it for you.
What happens when you encrypt an EBS volume.
Encryption happens end-to-end
- Data at rest is encrypted inside the volume
- All data in flight moving between the instance and the volume is encrypted.
- All snapshots are encrypted
- All volumes created from the snapshot are encrypted
- Copying an unencrypted snapshot allows encryption.
- Snapshots of encrypted volumes are encrypted.
How do you encrypt an unencrypted volume?
- Create a snapshot of the unencrypted root device volume.
- Create a copy of the snapshot and select the encrypt option
- create an image (AMI) from the encrypted snapshot
- Us that image (AMI) to launch new encrypted instances.