Please enable JavaScript.
Coggle requires JavaScript to display documents.
EBS - Coggle Diagram
EBS
EBS Encryption
When you create an encrypted EBS volume:
- Data at rest is encrypted inside the volume
- All data in flight moving between instance and volume is encrypted
- All snapshots are encrypted
- Al volumes created from the snapshot are encrypted
Features:
- Has minimal impact on latency
- Leverages keys from AWS KMS (AES-256)
- By using my own keys in AWS KMS
- EBS does not support asymmetric KMS keys
To encrypt an unencrypted EBS volume
- Create Snapshot of the unencrypted Volume
- Encrypt Snapshot using Copy
- Create new volume from the encrypted Snapshot
- Attach the encrypted Volume
-
EBS RAID Options
-
RAID 0 (image)
Features:
- Combine 2 or more volumes and getting the total disk space and I/O
- Data is written across multiple disks
- Pros:
- Increase performance
- Big disk with lot of IOPS
- Cons: 1 disk fails, all data is failed
- Use Cases:
- Application that needs a lot of IOPS and does not need fault-tolerance
- Database that has replication already built-in
RAID 1 (image)
Features:
- Mirroring a volume to another
- Pros: If 1 disk fails, logical volume is still working
- Cons: Have to send the data to 2 EBS volume at the same time (2x network)
- Use Cases:
- Application that need increase volume fault tolerance
- Application where you need to service disks
EBS Volume
EBS Volume Types
gp2/ gp3 (SSD)
Features:
- General purpose SSD volume that balances price and performance for a wide variety of workloads
- Size: 1GB to 16 TB
- Pros:
- Cost effective storage
- Low-latency
- Use cases: System boot volumes, virtual desktops, development and test environments
- gp3 (SSD): Independently set the IOPS and throughput
- gp2 (SSD): IOPS and throughput are linked together
- gp2 ability to burst to 3,000 IOPS for extended periods of time
-
SSD:
- Only gp2/ gp3 and io1/ io2 can be used as boot volumes
- Small, Random I/O operations
HDD
Features:
- Cannot be a boot volume
- Size: 125MB to 16TB
- st1 (HDD):
- Low cost HDD volume designed for frequently accessed, throughput-intensive workloads
- Throughout optimized HDD
- Use cases: Big data, Data warehouse, Log processing
- sc1 (HDD):
- Lowest cost HDD volume designed for less frequently accessed workloads
- Large, Sequential I/O operations
Features:
- Network drive attach to instance
- Pros: Can be detached from 1 EC2 instance to another 1 quickly
- Cons: A bit of latency
- Persist data even after instance is terminated
- 1 EBS mount to 1 instance only (at CCP level)
- Bound to specific AZ
- Use Snapshot to move a volume across
- Free tier: 30GB of free EBS storage
- Have a provisioned capacity
- Can have 2 EBS attached to 1 instance
- Can have unattached EBS which does not mount to any instance
- Delete on Termination
- Controls EBS behavior when EC2 instance terminates
- By default root EBS volume is deleted
- By default any other attached EBS volume is not deleted
- Can be controlled by the AWS management console/ AWS CLI
- Support live configuration changes while in production which means that I can modify the volume type, volume size, and IOPS capacity without service interruptions
EBS Snapshot:
- Snapshot is a backup
- Not necessary to detach volume but recommended
- Can copy snapshots across AZ or Region
- Create volume from the Snapshot in a new AZ to restore the volume
- Can use Amazon DLM (Data Lifecycle Manager) to automate the creation, retention, and deletion of snapshots taken to back up my EBS volumes