SAA-C03 ยท High-performing storage
Object, block and file storage
Characteristics and use cases of object (S3), block (EBS, instance store) and file (EFS, FSx) storage, including instance store as ephemeral storage.
Key points
- Object (Amazon S3): whole objects by key via HTTP API; no capacity planning, not mountable.
- Block: raw volumes for an OS.
- EBS: network-attached, one AZ, survives stop/start; boot disks, databases.
- Instance store: host disk, in instance price, fast, ephemeral: survives reboot, lost on stop, hibernate, terminate; caches, scratch.
- File: shared mounts; EFS (Linux NFS), FSx (Windows File Server, Lustre, NetApp ONTAP, OpenZFS).
Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-lifetime.html
Practice questions
Which storage option uses disks physically attached to the EC2 host and loses its data when the instance is stopped?
- An instance store volume
- An Amazon EBS gp3 volume
- An Amazon EFS One Zone file system
- An Amazon S3 general purpose bucket
Show answer
Answer: A. An instance store volume
Instance store volumes sit on the host itself, so their data does not survive a stop, hibernate or terminate. An EBS gp3 volume is network-attached and keeps its data across stop and start.
Which statements about Amazon EBS volumes are true?
- A volume attaches only to instances in its own Availability Zone
- A volume can be detached and attached to another instance in that AZ
- A volume can be attached to instances in any AZ of the Region
- Applications read and write volume data through HTTP GET and PUT
- Every EBS volume type supports Multi-Attach to several instances
Show answer
Answer: A. A volume attaches only to instances in its own Availability Zone, B. A volume can be detached and attached to another instance in that AZ
An EBS volume is created in one Availability Zone and attaches only to instances in that AZ, and you can detach it and attach it to another instance there. EBS is block storage used by the OS, not an HTTP object API, and Multi-Attach is supported only on Provisioned IOPS (io1, io2) volumes, not on every type.
Data on an instance store volume survives an instance stop and start, as long as the instance is never terminated.
Show answer
Answer: False
False. Instance store data persists through a reboot, but it is lost when the instance is stopped, hibernated or terminated. Keep anything valuable on EBS, S3 or EFS.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
