AWS Associate Architect Storage Options (Instance Store (Disadvantages…
AWS Associate Architect Storage Options
Ephemeral Data (Volume only exists for life of instance.
A stop, shutdown or terminate erases the data
but a reboot doesn't erase the data
Physically attached to host computer and magnitudes faster than EBS volumes
Good for swap files, cache files, replicated data, nosql db
You don’t get to provision the number of volumes and the size of the volumes.
How much Instance Storage you get available to you, depends on the instance type and the size
If your data needs to be durably stored, use EBS
Instance Store available Instances
- c3, f1, g2, i3, m3, r3, x1 (if you are looking for Instance Storage, you are limited to these instance type)
- h1, d2
- t2, m4, m5, c4, c5, g3, p2, p3, r4 (Doesn’t have Instance Storage)
Elastic Block Storage (EBS)
Persistent Storage over the Network
SSD - Fast Random Access, High IOPS
General Purpose (GP2)
For dev/test environments
Baseline 100 - 10,000 IOPS
Bursts up to 32,000 IOPS (credit based)
Volume size 1GiB to 16TiB
What do you think happens when you burst and you burn up all your credits?
Well you get pushed back down to the lower baseline. One way of dealing with that if you don’t want to use provision is to have a larger EBS volume because the baseline performance and how quickly you accumulate credits goes up proportional to the size of the volume.
For mission critical applications that require sustained IOPS performance (Large DB workloads)
Volume size of 4GiB to 16TiB
Can provision up to 64,000 IOPS per volume
Note: EC2 instances have a max of 80,000 IOPS total
Hard disk - Optimised for throughput, Sequential Access, Streaming & Big Data
Throughput Optimised (st1)
Low storage cost
Used for frequently accessed, throughput-intensive workloads (Streaming, Big data)
Cannot be a boot volume
Volume size 500 GiB - 16 TiB
Max throughput of 500 MiB/s
Note: EC2 instances have a maximum throughput of 1750 MiB/s
Cold Hard disk (sc1)
Infrequently accessed data
Cannot be a boot volume
Volume size of 400 GiB - 16 TiB
Max throughput of 250 MiB/s
Must be initialised or 50% performance hit (Read all data manually)
Persistent storage if you uncheck
Delete on Termination
Only one instance per EBS, but can have many EBS's attached to an instance
Can take a snapshot of EBS onto S3
Instances have a 2nd network interface optimised for EBS traffic
Can provision up to 16 TiB storage
Can detach and reattach to another instance if instance fails
9.999% availability due to RAID 1 Mirror
Provisioned IOPS’ may not produce the performance, so you might need to use an EBS optimised instance type is required
Snapshots can be used to
create AMIs if it is a boot volume
and restore EBS volumes
A snapshot only stores the changes since the most recent snapshot, thus reducing costs by only having to pay for storage for the incremental changes between snapshots.
if an old snapshot is deleted, blocks required to restore the other snapshots are retained.
Snapshots are available for EBS volumes, but it is not available for Instance Store.
Snapshots are best stored in S3.
you should actually stop the writes to your volume before issuing the snapshot command. Use the
command to stop the writes.
If the volume happens to be the boot volume for an instance, then it is recommended that you stop the instance first, then take the snapshot, then restart the instance. That way you will have a nice consistent snapshot
You can use Cloudwatch events to schedule those snapshots.
you can attach another EBS volume.
That volume would be attached to any instances automatically that use that AMI.
Elastic File Share
Instance Store is local ephemeral storage which gives you really high IOPS and ...
EBS is persistent network block storage that can have a life cycle independent of the EC2 instance.
However both of those operate very similar to a disk drive. Where a disk drive cannot be physically be mounted on more than one server at a time.
EFS can be mounted by many EC2 Instances (unlike EBS, Instance Store)
EFS supports your standard unix style permissions for files and folders.
EFS can provision multiple mount points in multiple availability zones.