Before you start: Review IP addresses, subnets and DNS if they are new to you.
What to aim for
Distinguish cloud service models and shared responsibility.
Explain the roles of EC2, S3, VPC, Route 53 and Lambda.
Try it yourself: Sketch a VPC, subnet and EC2 instance, then explain the route and access controls needed for internet connectivity. A drawing needs no cloud account.
Suggested preparation, not an entry requirement. Every track stays free to open.
Learn with Network Kings videos, ordered chapters and practical explanations. Choose a subject to see what to study and which lessons to watch first.
A little time. A new idea.
Bite-sized tech lessons from the channel
CCNP & CCIE
286 views
Explore more
452 views
Networking
353 views
CCNP & CCIE
2.3K views
Networking
1K views
Networking
599 views
Linux & DevOps
620 views
Networking
363 views
Explore more
368 views
Networking
608 views
Explore more
489 views
AWS
315 views
Video · Linux & DevOps
Your browser paused autoplay. Press Play inside the video to start.
Top 10 Linux Commands Every Beginner Should Know
Linux & DevOps · 17:09
LEARNING CHAPTER
Understand. Remember. Apply.
Linux commands
Shell navigation
File inspection
Command help
lscpu CPU information
free memory and swap
df filesystem space
uptime and load averages
systemctl service state
ss listening TCP ports
Topic guide · Not a video summary
Diagnose a Linux host with evidence
Build a read-only troubleshooting checklist around the lesson's published topics: listing files, CPU/RAM/filesystem information, performance and uptime, services and listening ports. Keep each observation separate: low unused memory is not the same as low available memory, a running service is not proof of remote access, and load average is not CPU percentage. This reference guide expands the topic outline; it is not a transcript summary.
Key takeaways
Start with pwd and ls to confirm your current location and inspect entries. Use each command's help or manual to understand options before changing files.
Use lscpu for CPU architecture, free -h for memory and swap, and df -h for mounted filesystem space. In free, compare available memory as well as free memory; cache use alone does not establish a shortage.
Read uptime's 1-, 5- and 15-minute load averages as workload context, not CPU percentages. Compare them with the machine's CPU count and process observations rather than diagnosing a bottleneck from one number.
On a systemd-based host, systemctl status UNIT reports a unit's current state. Enabled and active describe different things: a unit can be enabled without running, or running without being enabled.
Use ss -lnt to inspect listening TCP sockets with numeric addresses and ports. Check the bind address: a listener on 127.0.0.1 is local to that host. A listening socket alone does not prove that routes, firewall rules and remote connectivity work.
Put it into practice
Paper scenario: a web service reports active, but ss -lnt shows only 127.0.0.1:8080 and a remote browser cannot connect. Explain why active status alone is insufficient. List the bind-address, local connectivity, routing and firewall evidence you would collect before proposing a change. Separately, explain why high cache use in free -h should be compared with available memory before declaring a RAM shortage.
Explore the diagram / topology
Illustrative concept diagram for study.
Use the reference guide's paper scenario to compare three kinds of evidence. An active service alone does not prove remote access, and a listener bound only to 127.0.0.1 serves that host locally. The arrows group investigation steps; they are not packet hops or a compulsory command order. This study map accompanies the topic guide, rather than depicting a verified video lab.
8 lessons
