Chapter 13: Amazon EBS (Elastic Block Store)

13.7 Detaching a volume safely

By Ravindra Bagale Last updated: 15 October 2026

Detaching a mounted volume can corrupt data. Always unmount inside Linux first. Friends, remember the order: first umount in Linux, then fstab, and finally detach in the console.

# 1. Stop anything using the disk
sudo lsof +f -- /data            # list open files on /data (install lsof if missing)
cd ~                             # make sure your shell is not inside /data

# 2. Unmount
sudo umount /data                # "target is busy" = something still uses it

# 3. Remove or comment the fstab line so boot does not look for it
sudo sed -i.bak '\#[[:space:]]/data[[:space:]]#s/^/#/' /etc/fstab
cat /etc/fstab

Console: Volumes → select → Actions → Detach volume → confirm. State becomes Available.
If you no longer need it: take a snapshot (optional) → Actions → Delete volume (stops billing).

Force detach

Force detach is only for emergencies when a normal detach is stuck; it can cause data loss or filesystem corruption.

Extended teaching notes

Why this lesson matters

Cloud security is mostly IAM, network exposure, logging and secure defaults. The shared responsibility model means the provider patches the metal; you patch what you configure.

No public databases or public admin panels.
Roles / OIDC instead of long-lived access keys.
CloudTrail / Activity Logs / Audit Logs on and retained.
S3/Blob/GCS: Block Public Access; encrypt; least privilege.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

Write the lesson title, date and the exact lab target you are allowed to use.
List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
Run one safe check from the lesson on a lab system only. Paste the command and output.
Write a two-sentence fix you would give a teammate.
Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

Control: a safeguard (patch, config, process, detection).
Finding: a weakness backed by evidence.
Remediation: the fix plus how you verified it.
Scope: systems you have written permission to touch.
Least privilege: only the access the task needs.
Defence in depth: several layers so one failure does not end the story.

Common mistakes

Skipping written permission "just for a quick scan".
Practising on hostel, office or public targets without authorisation.
Collecting tool output without writing the fix.
Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

Evidence, fix, owner, date.
Own lab only.
Fix > spectacle.