Chapter 4: Linux Ops Refresh for DevOps
4.9 What this chapter deliberately skips
| Topic | Where to learn it |
|---|---|
| Launch EC2, choose AMI, Security Groups, Elastic IP | AWS course — EC2 chapter |
| Deep Linux users, networking tools, advanced permissions | AWS course — Linux chapters |
| VPC design, subnets, Route 53 DNS | AWS course — networking / VPC / DNS |
| Full Nginx or Apache install and vhosts | AWS course — web server chapters |
Here you only need to operate: is it up, which counter (port) is open, is disk OK, can I read logs, can I copy a file safely.
One sentence for interviews: "When production looks down, I check process, listening port, disk and recent logs before I change application code."
Thodkyaat sangaycha tar
- Triage: process → port (shop counter) → disk → logs.
systemctl/service: start now vs enable on boot.journalctl -f/tail -fwhile youcurl— watch and reproduce together.- SSH private keys never enter Git; scp/rsync from the laptop with clear paths.
- Deep Linux/EC2/VPC stay in the AWS course — this was a refresh only.
Samajla ka? Nasel tar triage steps (4.5) laptop/VM var ekda chalva – process, port, disk, logs. Aata pudhe jaauya Bash scripting kade.