DevOps Week 1: Networking Fundamentals

Welcome to Week 1 of the 90DaysOfDevOps – 2025 Edition! Whether you’re from an IT background or not, this blog is for you*. Let’s understand networking in the simplest way possible.* 🌐


🔹 What is Networking in DevOps?

In simple terms, networking means connecting computers or devices together so they can talk to each other. In DevOps, networking is important because we work with cloud servers, deploy apps, and ensure everything communicates safely and smoothly.


📘 1. OSI & TCP/IP Models — The Basics

Think of sending a message to your friend. You type, press send, the message travels, reaches your friend, and they reply. Similarly, computer communication happens through layers.

🧩 OSI Model (7 Layers):

LayerExample in Real LifeWhat it Does
7. ApplicationUsing a browser like ChromeInterface with users
6. PresentationData formats, encryptionMakes data readable
5. SessionWhatsApp call sessionManages connection
4. TransportTCP, UDPEnsures correct delivery
3. NetworkIP AddressChooses path for data
2. Data LinkMAC AddressDeals with local delivery
1. PhysicalEthernet cable/Wi-FiPhysical transfer of bits

📦 TCP/IP Model (4 Layers):

It’s a simplified real-world model:

  • Application (e.g., HTTP)

  • Transport (e.g., TCP/UDP)

  • Internet (e.g., IP)

  • Network Access (Wi-Fi, Ethernet)

👉 Real Example:
When you visit www.google.com:

  • Your browser (Application Layer) sends a request.

  • TCP breaks the request into packets (Transport).

  • IP finds the best path to Google (Internet).

  • Data is transferred over Wi-Fi (Network Access).


🌐 2. Protocols & Ports Every DevOps Engineer Must Know

ProtocolPortUse in DevOps
HTTP80Web apps
HTTPS443Secure web apps
FTP21File transfers
SSH22Login to servers
DNS53Resolving domain names

Protocols & Ports

🛠 Task: Learn which service runs on which port.
Example: If a server isn’t responding on port 22, SSH access may be blocked!


☁️ 3. AWS EC2 + Security Groups

Amazon EC2 = Virtual Computer in the Cloud.

🔐 What Are Security Groups?

They act like firewalls – allowing/blocking incoming/outgoing traffic.

✅ You allow port 22 to connect via SSH.
✅ You allow port 80/443 for web access.

This image explains how only allowed network traffic (via open ports like 22 or 80/443) can reach your server, while malicious traffic is blocked by a firewall or port configuration.

📋 Step-by-Step:

  1. Go to AWS EC2 Dashboard.

  2. Launch a free-tier Ubuntu instance.

  3. In Security Groups:

    • Allow port 22 (SSH)

    • Allow port 80 (HTTP)

    • Allow port 443 (HTTPS)

  4. Connect to instance using:

ssh -i "your-key.pem" ubuntu@your-public-ip

💻 4. Common Networking Commands Cheat Sheet

CommandUse
ping google.comCheck if a server is reachable
traceroute google.comSee path your data takes
netstat -tulnShow open ports
curl ifconfig.meCheck your public IP
dig google.comDNS lookup
nslookup google.comAnother way to check DNS

👉 These commands help you debug network issues and ensure your apps can connect properly.


📝 Summary of Week 1

✅ Understood OSI & TCP/IP with real-world examples
✅ Learned key networking protocols & ports
✅ Launched AWS EC2 instance with correct Security Groups
✅ Practiced essential networking commands


📢 Final Thoughts

Networking is the base of everything in DevOps. From cloud servers to CI/CD pipelines, good networking knowledge saves time and prevents errors.

💡 If you can ping it, you can reach it! If you can't — troubleshoot the layers! 😄


📤 Connect With Me

Blog Series: https://hashnode.com/@VaishnaviTandekar
GitHub Repo: 90DaysOfDevOps
#90DaysOfDevOps #Networking #DevOpsBeginner

0
Subscribe to my newsletter

Read articles from Vaishnavi Tandekar directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Vaishnavi Tandekar
Vaishnavi Tandekar

Hey there! I’m Vaishnavi 👋 Learning DevOps step by step 🛠️ Writing what I learn so no one learns alone ✨