ebs Flashcards
storage volumes that you can attach to your ec2 instances
Elastic Block Store
designed for production workloads
EBS
highly available and automatically replicated within a single availability zone to protect against failures
EBS
Dynamically increase capacity and change the volume type with no downtime or performance impact to live systems
EBS
3 iops per GB up to a max of 16000 OPS per volume
General Purpose (Gp2)
good for boot volumes or development and test applications that are not latency sensitive
gp2
ideal for applications that require high performance at a low cost
Gp3
up to 64000 IOPS per volume 50 IOPS per GiB
Provisioned IOPS SSD (io1)
volume used if you need more that 16000 IOPS
io1/io2
designed for I/o intensive applications, large databases and latency sensitive workloads
io1/io2
low cost hdd volume that is magnetic storage
Throughput Optimized HDD (st1)
volume used for frequently accessed throughput-intenstive workloads
St1
volume used for big data, data warehouses, ETL and log processing
st1
volume used to maximize cost-reduction
cold hdd (sc1)
volume that is good for lowest cost with performance not being a factor
sc1
volume used for transactions (OLTP)
io1/io2
point in time photograph of the virtual disk/volume stored in s3
snapshot
only data that has been changed since your last are moved to s3
snapshot
if you take a snapshot of an encrypted ebs volume the snapshot will be encrypted automatically
encrypted snapshots
can only share snapshots in the region they were created in, must copy to destination region first
sharing snapshots
ebs volumes will always be in the same az as the ec2 instance
volumes
ebs encrypts volumes with a data key using the industry-standard AES-256 algorithm
ebs encryption
used when amazon EBS encryption happens when creating enrypted volumes and snapshots
AWS KMS,
instances boot much faster because the in-memory state (RAM) is preserved on persistent storage (EBS)
EC2 Hibernation
