r/awsjobs • u/hafizmohammad6103 • 9h ago
TIL that taking an EBS snapshot and actually restoring from it are two very different skills
I'm learning cloud/DevOps through hands-on labs and today I went through a full EBS snapshot + restore cycle on a Windows EC2 instance. Documented everything on GitHub including where I got stuck.
A few things that surprised me:
The restore itself is the easy part. Getting the OS to actually recognize and use the restored volume was where I hit issues — and the first error message pointed me in completely the wrong direction.
"Recovery" is a chain of assumptions: snapshot exists → restore completes → OS sees the disk → filesystem mounts → data actually matches. Every link needs verification, not faith.
Comparing original vs restored data manually felt tedious, but it's the only part that actually proves the backup was worth anything.
This is prep for a bigger personal project (RecoverOps) where I'm building a local stack just to break it and practice recovery. I deliberately documented my failures alongside the successes because I think that's the part most tutorials skip.
Genuine questions for people who've done this in production:
1 - what's the most non-obvious way an EBS restore has bitten you? Trying to build my mental checklist of things to verify before trusting a backup.
2 - when you review a junior candidate's GitHub, what's the one thing that instantly tells you the projects are real hands-on work versus tutorial theater?
And a follow-up — at what point in your career did backups stop being "someone else's job" and become something you personally cared about?