Amazon Elastic Block Store (EBS) is an easy to use, high performance block storage service designed for use with Amazon Elastic Compute Cloud (EC2) for both throughput and transaction intensive workloads at any scale
EBS volumes are created in a specific Availability Zone. You can make a volume available outside of the Availability Zone, you can create a snapshot and restore that snapshot to a new volume anywhere in that Region
Instance storage is temporary block level storage for your instance.
Instance store persists during reboots. It is lost when the disk drive fails and the instance stops or terminates.
You can specify the instance store volumes only when you lunch an instance. You cannot add a new instance after lunch
Not all instance types support instance store volumes
EBS-optimized instance provides additional, dedicated capacity for Amazon EBS I/O. This provides the best performance for your EBS volumes
EBS provides SSD and HDD volume types
- SSD-backed volumes optimized for transactional workloads, frequent read/write
- HDD-backed volumes optimized for large streaming workloads
General purpose SSD: These volumes are ideal for a broad range of use cases such as boot volumes, small and medium-size databases, and development and test environments
Provisioned iOPS SSD: For low-latency or high throughput workloads (require more IOPS than General Purpose SSD, large database workloads).
Throughput Optimized HDD volumes provide low-cost magnetic storage that defines performance in terms of throughput rather than IOPS. These volumes are ideal for large, sequential workloads such as Amazon EMR, ETL, data warehouses, and log processing
Cold HDD volumes provide low-cost magnetic storage that defines performance in terms of throughput rather than IOPS. These volumes are ideal for large, sequential, cold-data workloads. If you require infrequent access to your data and are looking to save costs, these volumes provides inexpensive block storage
Yes, you can.
These data types are encrypted when you create volume and attach it to an instance. Encrypted volumes are not supported on all instance types
- data inside volume
- data moving between instance and volume
- all snapshots created from volume
- all volumes created from snapshot
These tips represent best practices for getting optimal performance from your EBS volumes in a variety of user scenarios.
- Use EBS-optimized instances
- Understand how performance is calculated
- Understand your workload
You cannot remove encryption from an encrypted volume or snapshot, which means that a volume restored from an encrypted snapshot, or a copy of an encrypted snapshot, is always encrypted.
There is no direct way to encrypt an existing unencrypted volume or snapshot, but you can encrypt them by creating either a volume or a snapshot
What are the Encryption scenarios? (E.g.: enable/disable encryption when creating snapshot/volume etc)
The following examples illustrate how you can manage the encryption state of your volumes and snapshots:
- Restore an unencrypted volume (encryption by default not enabled)
- Restore an unencrypted volume (encryption by default enabled)
- Copy an unencrypted snapshot (encryption by default not enabled)
- Copy an unencrypted snapshot (encryption by default enabled)
- Re-encrypt an encrypted volume
- Re-encrypt an encrypted snapshot
- Migrate data between encrypted and unencrypted volumes
- Encryption outcomes