Ravindra BagaleCourses & study guides मराठी Track your progress

Chapter 13: Amazon EBS (Elastic Block Store)

13.8 EBS best practices

By Last updated:

Friends, I use this list as a checklist at the end of every project. gp3, a separate data volume, encryption, automatic snapshots – and delete the volumes you don't need.

  • Use gp3 by default; convert old gp2 volumes to gp3.
  • Keep data on separate volumes from the OS; use UUID + nofail in fstab.
  • Encrypt volumes (set EBS encryption by default in EC2 settings for the region).
  • Automate snapshots with Data Lifecycle Manager / AWS Backup, and test restores.
  • Monitor free space (df -h) and CloudWatch metrics; grow before the disk is full.
  • Delete unattached volumes and old snapshots to save money.
  • Check Delete on termination settings: root volumes default to deleted, extra volumes default to kept.

Ravindra Bagale's Tip

After every lab take two minutes: look for Available (unattached) volumes in Volumes and old snapshots in Snapshots. They quietly keep eating money – delete them if you don't need them.

Lab

Chala, tumchya account madhe EC2 → Volumes aani Snapshots bagha aani unattached volumes aani june snapshots chi list banva. Pratyekasathi thevaycha ki delete karaycha te karanasah liha, aani nako asleli delete kara.

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)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. 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.