- Snapshots are incremental
- Snapshots are stored on s3
- New volumes can be created from snapshots
- Snapshots can be copied from 1 region to another.
- EBS volume is only available in a single AZ
- All writes are replicated to multiple AZs within a region
- Offers encryption through AWS KMS
- Snapshots taken from encrypted volumes will also be encrypted.
- Can create a default encryption region to ensure all EBS volumes created within a region will be encrypted.
- Can only be attached to EC2 instances within the same AZ.
- temporary storage
- multi-instance access is needed (Use EFS)
- Very high durability/availability (Use EFS or S3)
- Better suited for smaller blocks (database or boot instances)
- Balance price and Performance
- System Boot Volumes
- Virtual Desktops
- Low Latency interactive apps
- Development and test environments
- Highest performance, Mission critical apps.
- Require IOPs performance > 16,000 or 250MiB/s throughput
- Large database workloads
- Higher rate of throughput, logging
- Cannot be a root volume
- Low cost HDD designed for frequently accessed, throughput intensive workloads.
- Streaming
- Big Data/data warehouse
- Log Processing
- Cannot be a root volume
- Lowest Cost HDD
- Designed for less frequently access workloads
- Used when the lowest cost is the target.
- Can create a blank volume, or a volume based off an existing EBS Snapshot.
- Need to specify:
- size
- volume type
- Encrypt
- Destroy or retain volume upon instance termination