Classify the data
Temporary processing files and business records have different needs. I would separate files that can be recreated from files requiring recovery protection. If losing a file means losing important information, temporary storage alone is not enough.
Check the lifecycle
Instance-store data is lost on events such as stopping or terminating the instance. With EBS, inspect deletion settings and backup arrangements. Do not assume the instance status alone tells you whether every associated disk remains or disappears.
Test reconstruction and recovery
A scratch workspace can use temporary storage when the application can rebuild it. Keep source data elsewhere and test that process. For persistent data, plan how you would restore a damaged or accidentally deleted file. Persistence and backup are separate questions.
Try it yourself
List three application files and mark which can be rebuilt. Describe their expected behaviour after the instance is terminated.
A common question
Does persistence remove the need for backups?
No. Persistent storage can still be affected by deletion, corruption or application mistakes.
References & video notes
Use the video to follow the topic with me. Console screens and older offers can change, so check the current AWS documentation before performing a lab.
Keep learning
- Block, file and object storage: choose the access pattern
- EBS volume types: understand IOPS and throughput
- EBS snapshots: include a restore in your backup lab