What to know about Amazon Elastic Block Store (EBS)
•
0 likes•229 views
This document provides information about Amazon Elastic Block Store (EBS). It begins with an introduction to the author and their experience and certifications. It then discusses EBS as a block storage service from AWS that is network-attached storage for EC2 instances. Key points made include that EBS volumes can be independently created, attached to EC2 instances, resized, and snapshotted for backups. Different EBS volume types like GP2, IO1, ST1, and SC1 are suited for different use cases based on their performance characteristics and cost. Choosing the right volume type depends on factors like throughput needs, IOPS requirements, and whether sequential or random access is more important.
More Related Content
What's hot
What's hot (20)
Similar to What to know about Amazon Elastic Block Store (EBS)
Similar to What to know about Amazon Elastic Block Store (EBS) (20)
More from LCloud
More from LCloud (13)
Recently uploaded
Recently uploaded (20)
What to know about Amazon Elastic Block Store (EBS)
- 1. What to know about Amazon Elastic Block Store (EBS)
- 2. About me ● 13+ years of professional experience in System and 9+ years in Cloud Computing architecting and administration (jacek.biernat@lcloud.pl) ● AWS Certifications: ○ AWS Certified Solutions Architect from 2013 (Professional from 2016) ○ AWS Certified SysOps Administrator from 2014 ● Founder and CEO at LCloud, ex. Linxsys ○ AWS Partner from 2012 (Advanced Partner from 2016) in Poland ○ We are after 200+ AWS projects
- 4. Storage service Block File Object Amazon Elastic Block Store Amazon Elastic File System Amazon Simple Storage Service Amazon Glacier
- 5. Block storage offering EC2 instance store AWS block storage
- 6. Amazon EC2 instance store Non-persistent data store Data not replicated No snapshot support SSD or HDD
- 7. What is EBS? Ec2 instance != EBS volume
- 8. What is EBS? Ec2 instance - Create, attach volumes through an API - Block storage as a service over the network EBS volume - EBS encryption is supported
- 9. What is EBS? - EBS is independent of Ec2 - Detach and attach between Ec2 - EBS and Ec2 must be in the same AZ
- 10. What is EBS? - EBS attach to one Ec2 at a time - Many EBS can attach to one Ec2 - Separate boot volume
- 11. What is EBS? Ec2 instance EBS volume
- 12. What is EBS? - SLA EBS is 99.999% - AFR (annual failure rate) is 0.1% - 0.2%
- 13. What is EBS snapshot? - SLA S3 is 99.999999999% - No specific AZ - Backup of modified volume blocks - Next snapshots are incremental
- 14. What can we do with a snapshot? - Create AMI from snapshot - Create new size EBS from snapshot
- 15. What can we do with a snapshot?
- 16. What is an EBS-optimized instance? ~125 MB/s Ec2 Internet
- 17. What is an EBS-optimized instance? ~125 MB/s Ec2 Internet ~125 MB/s EBS - Default for c4, d2, m4, p2, x1 Ec2 instances - Some 8xlarge Ec2 have 10 Gbps network bandwidth and don’t
- 18. Block storage offering EC2 instance store AWS block EBS HDD-backed magnetic storage volume
- 19. Block storage offering EC2 instance store AWS block EBS HDD-backed magnetic storage volume EBS SSD-backed gp2 io1
- 20. Block storage offering EC2 instance store AWS block EBS HDD-backed magnetic st1 sc1 storage volume EBS SSD-backed gp2 io1
- 21. EBS volume types Magnetic General Purpose Provisioned IOPS Throughput Optimized Cold HDD (sc1) SSD (gp2) SSD (io1) HDD (st1) 1GB - 1TB 1GB - 16TB 4GB - 16TB 500GB - 16TB 500GB-16TB Av. 100 IOPS 3 IOPS @ GB Max. 20,000 IOPS Max. 500 IOPS Max. 250 IOPS Max. 10,000 IOPS Av. 65 MB/s Max. 160 MB/s Max. 320 MB/s 40 MB/s @ TB 12 MB/s @ TB Max. 500 MB/s Max. 192 MB/s Burst: - Burst: 3,000 IOPS (1TB) Burst: - Burst: 250 MB/s @ TB Burst: 80MB/s @ TB
- 22. gp2 - burst performance
- 23. gp2- how long can I burst? Max I/O credit is 5.4 million I/O credits, accumulating 3 IOPS per GB per second
- 25. st1 - throughput Burst to 125-500MB/s per TB, Accumulating 40 MB per TB per second,
- 26. sc1 - throughput Burst to 80MB/s per TB, Accumulating 12 MB per TB per second,
- 27. EBS volume types Magnetic - data is infrequently accessed General Purpose SSD (gp2) - boot volumes, low-latency applications, bursty database, Development and test environments Provisioned IOPS SSD (io1) - critical applications and large databases with sustained IOPS Throughput Optimized HDD (st1) - large-block, high-throughput sequential workloads (streaming), Big Data, Data warehouses, Log processing Cold HDD (sc1) - sequential throughput workloads, such as logging and backup
- 28. Choosing an EBS volume type
- 29. When to RAID? - Storage requirement > 16TB - Throughput requirement > 500 MB/s - IOPS requirement > 20,000 @ 16K
- 30. Avoid RAID for redundancy - EBS data is already replicated - RAID1 halves available EBS bandwidth - RAID5/6 loses 20% - 30% of usable I/O
- 31. Thank you for your attention.
Editor's Notes
- Everything from what makes up the service all the characteristics of it performance, best practices around reliability, security and performance durable, block-level storage device
- Everything from what makes up the service all the characteristics of it performance, best practices around reliability, security and performance durable, block-level storage device
- temporary block-level storage for your instance. This storage is located on disks that are physically attached to the host computer. Instance store is ideal for temporary storage of information that changes frequently, such as buffers, caches, scratch data.
- EBS volumes are highly available and reliable storage volumes that can be attached to any running instance that is in the same Availability Zone. EBS volumes that are attached to an EC2 instance are exposed as storage volumes that persist independently from the life of the instance. Attach both encrypted and unencrypted, support all EBS volume types, snapshots are encrypted, support currently generation instances
- Massive distributed system They are blocks that are distributed across many physical devices
- annual failure rate - roczna stopa awaryjności, gives the estimated probability that a device or component will fail during a full year of use For enterprise architecture hard disk is about 4%, for 1000 EBS for 1 year, we can expect to lose 1-2 EBS,
- First snapshot copy every modified block on S3
- Volume the same size or bigger
- Another region or AWS account We can share snapshot private/public
- Throughput a network bandwidth
- Dedicated bandwitdth to EBS
- What is most important for you IOPS or throughput or we are not sure Io1 daje podwojne wartosci z gp2