Week 1: Networking Challenge (Phase 2)

Table of contents
- ๐ 1. HTTP & HTTPS โ Talking to the Web
- ๐ 2. FTP โ File Transfer Protocol
- ๐ 3. SSH โ Secure Shell
- ๐ 4. DNS โ Domain Name System
- ๐ก 5. ARP & RARP โ Finding Your Neighbors
- ๐งฎ 6. CIDR โ Smarter IP Grouping
- ๐ฏ 7. MAC โ The Hardware Address
- โ๏ธ AWS EC2 & Security Groups: A Beginner's Step-by-Step Guide
- ๐ What You'll Learn:
- ๐งฐ Tools Youโll Need:
- ๐งญ Step 1: Log In to AWS Console:
- ๐ฅ Step 2: Launch an EC2 Instance:
- ๐ Step 3: Configure a New Security Group:
- ๐ Step 4: Create or Select a Key Pair ๐:
- โ Step 5: Launch Your EC2 Instance!:
- ๐ Summary Table:
- ๐ฆ Wrap-Up:
- ๐ก Final Tip:

๐ DevOps Key Protocols & Ports You Should Know!
You've undoubtedly heard a lot of lingo, including HTTP, SSH, DNS, and more, whether you're an IT professional or simply interested in the collaboration between modern development and operations, or DevOps.
๐ 1. HTTP & HTTPS โ Talking to the Web
Protocols: HTTP (Port 80), HTTPS (Port 443)
๐ What it does:
/HyperText Transfer Protocol is referred to as HTTP. It's how webpages communicate with your browser. With HTTPS, your data is encrypted, making it the secure version (๐).๐ Why it matters in DevOps:
Utilized in monitoring tools, online apps, and APIs. DevOps developers use HTTP/HTTPS to automate the deployment of online services.
๐ก Example:
When your app talks to PayPal, it's using HTTPS to keep payment info secure.๐ 2. FTP โ File Transfer Protocol
Protocol: FTP (Port 21)
๐ What it does:
It enables file transfers between your computer and a server.
๐ Why it matters in DevOps:
Used to move backups, logs, and builds.
FTP procedures are still used by some legacy systems.๐ก Example:
Uploading a new version of a website to a server manually using FileZilla (a popular FTP client).๐ 3. SSH โ Secure Shell
Protocol: SSH (Port 22)
๐ What it does:
SSH allows you to safely access a computer from a distance, such as your cloud server.
๐ Why it matters in DevOps:
Used to deploy code, run scripts, and log into servers.
A daily resource for cloud developers and system administrators.๐ก Example:
Typing
ssh
user@myserver.com
to log into a remote machine.๐ 4. DNS โ Domain Name System
Protocol: DNS (Port 53)
๐ What it does:
It converts domain names into IP addresses, such as google.com.
๐ Why it matters in DevOps:
Apps must search for services by name. U tilized in multi-cloud configurations, load balancing, and automation.
๐ก Example:
When a server makes a call to
api.mycompany.com
, DNS finds the right machine to talk to.๐ก 5. ARP & RARP โ Finding Your Neighbors
Protocols:
ARP (Address Resolution Protocol)
RARP (Reverse Address Resolution Protocol)
๐ What they do:
ARP: Determines which hardware address (MAC) corresponds to an IP address.
RARP: Does the oppositeโfinds out the IP address based on MAC
๐ Why it matters in DevOps:
Cloud networking is essential for debugging networks.
Supports Kubernetes and other container orchestration platforms.๐ก Example:
Your laptop asking, "Hey, who has 192.168.1.1?" ARP replies with, โThatโs me, hereโs my MAC!โ
๐งฎ 6. CIDR โ Smarter IP Grouping
Term: CIDR (Classless Inter-Domain Routing)
๐ What it does:
CIDR helps define IP address ranges using a format like/24
,/16
, etc.๐ Why it matters in DevOps:
Used to configure Kubernetes clusters, cloud VPCs, and firewalls.
limits the IPs that can access services.๐ก Example:
192.168.1.0/24
means all IPs from.1
to.254
in that network are part of the same group.๐ฏ 7. MAC โ The Hardware Address
Term: MAC (Media Access Control) Address
๐ What it is:
Similar to a fingerprint, each device has a distinct MAC address. Like a fingerprint. It's used for local networking.
๐ Why it matters in DevOps:
Beneficial for troubleshooting, access control, and network security.
Required occasionally for static DHCP reservations.๐ก Example:
A router assigns your laptop the same IP every time, based on its MAC address.
Protocol/Term | Port | Function | DevOps Role |
HTTP/HTTPS | 80/443 | Web access | API, app deployment |
FTP | 21 | File transfers | Backups, deployments |
SSH | 22 | Remote access | Server management |
DNS | 53 | Name resolution | Service discovery |
ARP/RARP | N/A | IP โ MAC resolution | Network setup |
CIDR | N/A | IP grouping | Firewall rules, VPCs |
MAC | N/A | Unique device ID | Access control |
โ๏ธ AWS EC2 & Security Groups: A Beginner's Step-by-Step Guide
๐ What You'll Learn:
โ
How to launch a Free Tier EC2 instance
โ
How to create and configure Security Groups
โ
Why Security Groups are the firewalls of the cloud
๐งฐ Tools Youโll Need:
โ An AWS account (Free Tier is perfect!)
โ Basic understanding of web interfaces
โ About 20 minutes โฐ
๐งญ Step 1: Log In to AWS Console:
๐ Go to: https://aws.amazon.com
Sign in with your AWS credentials.
In the search bar, type
EC2
and click the result.
๐ฅ Step 2: Launch an EC2 Instance:
Click โLaunch Instanceโ.
Name your instance something fun like
MyFirstServer
.
๐งฉ Choose the AMI (Amazon Machine Image)
- Pick Amazon Linux 2023 or Ubuntu 20.04 LTS โ both are Free Tier eligible.
๐ป Choose Instance Type
- Select t2.micro โ Free Tier eligible โ
๐ Step 3: Configure a New Security Group:
What is a Security Group?
๐ก Itโs like your cloud serverโs personal firewall. It controls:
Who can access it
Which ports are open (e.g., web, SSH, database)
๐ Step-by-Step: Create Security Group
Choose โCreate new security groupโ
Name it something like
my-ec2-security-group
Add Inbound rules:
โ SSH (Port 22) โ from My IP only (for secure remote login)
- ๐ This prevents others from accessing your server via terminal
๐ Optional: HTTP (Port 80) โ from Anywhere (for websites)
๐ Optional: HTTPS (Port 443) โ from Anywhere (for secure websites)
Leave Outbound rules as default (all traffic allowed) โ
๐ Step 4: Create or Select a Key Pair ๐:
Youโll need a key pair to access your server via SSH.
Choose โCreate new key pairโ
Name it (e.g.,
my-key
)Select format:
.pem
for Mac/Linux.ppk
for Windows (for PuTTY)
Download the key file โ keep it safe!
โ Step 5: Launch Your EC2 Instance!:
Review everything
Click Launch Instance
Wait a few seconds โฑ
๐ Boom! Your server is live!
๐ Summary Table:
Port | Protocol | Purpose | Who to Allow |
22 | SSH | Remote login | Your IP only |
80 | HTTP | Website access | Anywhere |
443 | HTTPS | Secure website access | Anywhere |
๐ฆ Wrap-Up:
๐น You've just set up a safe AWS EC2 instance!
๐นReady to launch websites, execute scripts, or experiment with cloud magic?
๐น Set up your first Security Group like a pro ๐ง
๐ก Final Tip:
"In the world of DevOps/Cloud computing, security isn't a one-time setup โ it's a mindset. ๐ค๏ธ
Start small, stay curious, and build with security in every step. The cloud gives you the power to scale โ but itโs your knowledge that makes it resilient. ๐๐ช
Keep exploring, keep learning. The more you automate wisely, the more time you gain to innovate boldly." ๐โจ
๐ Thanks for reading! If this helped you, feel free to drop a like, comment your thoughts, or share it with your cloud-curious friends.
Subscribe to my newsletter
Read articles from Purvesh Shapariya directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by
