<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sonu Bilwal on Medium]]></title>
        <description><![CDATA[Stories by Sonu Bilwal on Medium]]></description>
        <link>https://medium.com/@bilwalsonu08?source=rss-efb7fca05e75------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*4Lufaddg2ENjPD1YpybtjQ.jpeg</url>
            <title>Stories by Sonu Bilwal on Medium</title>
            <link>https://medium.com/@bilwalsonu08?source=rss-efb7fca05e75------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 03:43:08 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bilwalsonu08/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Day 13 of My #AWS Journey -Subnet,CIDR,Subnet mask in details]]></title>
            <link>https://medium.com/@bilwalsonu08/day-13-of-my-aws-journey-subnet-cidr-subnet-mask-in-details-c13bf6378b44?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/c13bf6378b44</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Sun, 31 Aug 2025 14:33:32 GMT</pubDate>
            <atom:updated>2025-08-31T14:33:32.324Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Everyone👋</p><h3>1. Subnet (Sub-network)</h3><p>A <strong>Subnet</strong> is a smaller, logical division of a larger network.<br> It allows you to organize, secure, and efficiently use IP addresses.</p><ul><li>An IP network can be broken into <strong>subnets</strong> to:</li><li>Separate departments or functions (HR, IT, Finance, etc.)</li><li>Improve security (restrict traffic between subnets)</li><li>Reduce network congestion</li></ul><p>Example:<br> If your company has the network 192.168.0.0/24 (256 IPs),<br> you can split it into <strong>two subnets</strong>:</p><ul><li>192.168.0.0/25 → 126 usable IPs</li><li>192.168.0.128/25 → 126 usable IPs</li></ul><h3>2. Subnet Mask</h3><p>A <strong>Subnet Mask</strong> defines which part of an IP address is the <strong>Network ID</strong> and which part is the <strong>Host ID</strong>.</p><ul><li><strong>Network ID</strong> → identifies the network</li><li><strong>Host ID</strong> → identifies devices within that network</li></ul><p>Subnet mask is written in <strong>dot-decimal</strong> format (like IP addresses).</p><ul><li>Example: 255.255.255.0</li></ul><p>Binary form:</p><ul><li>255.255.255.0 → 11111111.11111111.11111111.00000000</li><li>The <strong>1s</strong> = network portion, <strong>0s</strong> = host portion</li></ul><p>Example:<br> IP: 192.168.1.10<br> Subnet Mask: 255.255.255.0</p><ul><li>Network ID: 192.168.1.0</li><li>Host Range: 192.168.1.1 – 192.168.1.254</li><li>Broadcast: 192.168.1.255</li></ul><h3>3. CIDR (Classless Inter-Domain Routing)</h3><p>CIDR is a <strong>compact way</strong> of writing subnet masks.<br> Instead of writing 255.255.255.0, we use a <strong>slash notation</strong> → /24.</p><p>/n means <strong>n bits are fixed (network portion)</strong>.</p><ul><li>Example:</li><li>/8 → 255.0.0.0</li><li>/16 → 255.255.0.0</li><li>/24 → 255.255.255.0</li><li>/30 → 255.255.255.252</li></ul><p>Example:</p><ul><li>Network: 10.0.0.0/16 → 65,536 IPs</li><li>Network: 10.0.0.0/24 → 256 IPs</li></ul><h3>4. Relationship Between Them</h3><ul><li><strong>Subnet Mask</strong>: Old way of writing network division (255.255.255.0)</li><li><strong>CIDR</strong>: Modern, simplified form (/24)</li><li><strong>Subnet</strong>: The actual logical division of the network using subnet mask/CIDR</li></ul><h3>Summary</h3><ul><li><strong>Subnet</strong> = Logical smaller networks inside a bigger network.</li><li><strong>Subnet Mask</strong> = Defines how much of the IP is network vs host.</li><li><strong>CIDR</strong> = Shorthand for subnet masks (e.g., /24).</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c13bf6378b44" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 12 of My #AWS Journey –Package Management in Linux]]></title>
            <link>https://medium.com/@bilwalsonu08/day-12-of-my-aws-journey-package-management-in-linux-1388b9134d27?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/1388b9134d27</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Sun, 31 Aug 2025 14:18:39 GMT</pubDate>
            <atom:updated>2025-08-31T14:18:39.264Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello Everyone👋</p><h3>* Package Management in Linux:-</h3><p>In Linux, <strong>packages</strong> are bundles of software that include the program, configuration files, and metadata (dependencies, version, description).<br> <strong>Package management</strong> means installing, updating, upgrading, configuring, and removing these packages.</p><h3>1. Types of Package Managers</h3><p>Linux distributions use <strong>different package managers</strong>, depending on their family.</p><h3>a) Debian-based (Ubuntu, Debian, Mint)</h3><ul><li><strong>Package Format</strong> → .deb</li><li><strong>Low-level tool</strong> → dpkg (handles .deb files directly)</li><li><strong>High-level tools</strong> → apt, apt-get, apt-cache (manage dependencies automatically)</li></ul><h3>b) Red Hat-based (RHEL, CentOS, Fedora, Rocky, AlmaLinux)</h3><ul><li><strong>Package Format</strong> → .rpm</li><li><strong>Low-level tool</strong> → rpm (manages .rpm files)</li><li><strong>High-level tools</strong> →</li><li>yum (older versions, CentOS/RHEL 7)</li><li>dnf (newer versions, Fedora, RHEL 8+)</li></ul><h3>c) Other Examples</h3><ul><li><strong>Arch Linux</strong> → pacman</li><li><strong>OpenSUSE</strong> → zypper</li><li><strong>Gentoo</strong> → emerge (Portage system)</li></ul><h3>2. Debian/Ubuntu Package Management</h3><h3>dpkg (low-level)</h3><pre>sudo dpkg -i package.deb       # install .deb package<br>sudo dpkg -r package_name      # remove package<br>sudo dpkg -l                   # list installed packages</pre><h3>APT (high-level)</h3><pre>sudo apt update                # refresh package list<br>sudo apt upgrade               # upgrade all packages<br>sudo apt install vim           # install vim<br>sudo apt remove vim            # remove package<br>sudo apt purge vim             # remove + config files<br>sudo apt search vim            # search for package<br>sudo apt show vim              # show package details</pre><h3>3. RHEL / Fedora / CentOS Package Management</h3><h3>rpm (low-level)</h3><pre>sudo rpm -ivh package.rpm      # install<br>sudo rpm -e package_name       # erase (remove)<br>sudo rpm -qa                   # query all installed packages<br>sudo rpm -qi package_name      # show info about package</pre><h3>yum / dnf (high-level)</h3><pre>sudo yum install httpd         # install Apache<br>sudo yum remove httpd          # remove package<br>sudo yum update                # update system<br>sudo yum search httpd          # search package</pre><p>On newer systems:</p><pre>sudo dnf install nginx<br>sudo dnf remove nginx<br>sudo dnf upgrade</pre><h3>4. Arch Linux (Pacman)</h3><pre>sudo pacman -S package_name    # install<br>sudo pacman -R package_name    # remove<br>sudo pacman -Ss package_name   # search<br>sudo pacman -Sy                # refresh package database<br>sudo pacman -Syu               # update + upgrade</pre><h3>5. Package Repositories</h3><ul><li>Packages are stored in <strong>repositories (repos)</strong>.</li><li>Each distro has its own repos. Example:</li><li>Ubuntu → archive.ubuntu.com</li><li>Fedora → mirrors.fedoraproject.org</li><li>Users can add <strong>third-party repos</strong> (e.g., PPAs in Ubuntu).</li></ul><h3>6. Source-based Installation</h3><p>Some distros (like Gentoo) or advanced users compile software from <strong>source code</strong>:</p><pre>./configure<br>make<br>sudo make install</pre><p>But this is harder to manage than package managers.</p><h3>7. Universal Package Managers (Work Across Distros)</h3><ul><li><strong>Snap</strong> (Canonical, Ubuntu):</li><li>sudo snap install package</li><li><strong>Flatpak</strong>:</li><li>flatpak install package</li><li><strong>AppImage</strong> → portable, no installation needed.</li></ul><h3>Summary</h3><ul><li><strong>Low-level tools</strong> (dpkg, rpm) → handle individual package files.</li><li><strong>High-level tools</strong> (apt, yum, dnf, pacman) → manage dependencies &amp; repositories.</li><li><strong>Universal tools</strong> (snap, flatpak, AppImage) → work across multiple distros.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1388b9134d27" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 11 of My #AWS Journey — Linux→ Flags , Redirection, Vim Editor.]]></title>
            <link>https://medium.com/@bilwalsonu08/day-11-of-my-aws-journey-linux-flags-redirection-vim-editor-628474142575?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/628474142575</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Sun, 31 Aug 2025 14:12:33 GMT</pubDate>
            <atom:updated>2025-08-31T14:12:33.039Z</atom:updated>
            <content:encoded><![CDATA[<h3>Day 11 of My #AWS Journey — Linux→ Flags , Redirection, Vim Editor.</h3><p>Hello Eveeryone 👋👋</p><h3>1. Flags in Linux</h3><p>In Linux, <strong>flags</strong> (also called <strong>options</strong> or <strong>switches</strong>) are additional arguments given to a command to modify its behavior.<br> They usually start with - (short option) or -- (long option).</p><h3>Examples of Flags</h3><ol><li><strong>Listing files</strong></li></ol><ul><li>ls</li></ul><p>→ Lists files in current directory (basic).</p><ul><li>ls -l</li></ul><p>→ -l flag shows detailed info (permissions, owner, size, date).</p><ul><li>ls -a</li></ul><p>→ -a shows hidden files (files starting with .).</p><ul><li>ls -la</li></ul><p>→ Combine flags (-l + -a) for detailed + hidden files.</p><p><strong>2. Copy command</strong></p><ul><li>cp -i file1.txt file2.txt</li></ul><p>→ -i asks for confirmation before overwriting.</p><p><strong>3. Remove command</strong></p><ul><li>rm -r folder/</li></ul><p>→ -r flag deletes recursively (all subfolders &amp; files).</p><ul><li>rm -f file.tx</li></ul><p>→ -f forces deletion without confirmation.</p><h3>Key Point:</h3><p>Flags modify how commands behave, making them flexible and powerful.</p><h3>2. Redirection in Linux</h3><p>Redirection allows us to <strong>control input/output (I/O)</strong> of commands.<br> By default:</p><ul><li><strong>STDIN</strong> (standard input) → Keyboard (file descriptor 0)</li><li><strong>STDOUT</strong> (standard output) → Terminal screen (file descriptor 1)</li><li><strong>STDERR</strong> (standard error) → Terminal screen (file descriptor 2)</li></ul><p>We can <strong>redirect</strong> these to files, devices, or even other commands.</p><h3>Types of Redirection</h3><ol><li><strong>Output Redirection (</strong><strong>&gt; and </strong><strong>&gt;&gt;)</strong></li></ol><ul><li>echo &quot;Hello World&quot; &gt; file.txt</li></ul><p>→ Writes (overwrites) into file.txt.</p><ul><li>echo &quot;Another Line&quot; &gt;&gt; file.txt</li></ul><p>→ Appends to file.txt.</p><p><strong>2. Input Redirection (</strong><strong>&lt;)</strong></p><ul><li>sort &lt; file.txt</li></ul><p>→ Reads from file.txt instead of keyboard input.</p><p><strong>3. Error Redirection (</strong><strong>2&gt;)</strong></p><ul><li>ls nofile 2&gt; error.txt</li></ul><p>→ Sends error message to error.txt.</p><p><strong>4. Redirect STDOUT and STDERR Together</strong></p><ul><li>command &gt; output.txt 2&gt;&amp;1</li></ul><p>→ Sends both output and errors into one file.</p><p>Or shorter (Bash 4+):</p><ul><li>command &amp;&gt; output.txt</li></ul><p><strong>5. Pipe (</strong><strong>|)</strong><br> Sends output of one command to another as input.</p><ul><li>ls -l | grep &quot;txt&quot;</li></ul><p>→ Lists all .txt files.</p><p><strong>6. Null Redirection (</strong><strong>/dev/null)</strong></p><ul><li>command &gt; /dev/null 2&gt;&amp;1</li></ul><p>→ Discards both output and errors (silent run).</p><h3>3. Vim Editor:-</h3><p>Vim (<strong>Vi IMproved</strong>) is a powerful text editor in Linux.<br> It has <strong>modes</strong>:</p><ul><li><strong>Normal Mode (default)</strong> → navigation, commands</li><li><strong>Insert Mode</strong> → editing text</li><li><strong>Command Mode (Ex Mode)</strong> → saving, quitting, running commands</li></ul><h3>Basic Workflow</h3><ol><li>Open a file:</li></ol><ul><li>vim file.txt</li></ul><p>2. Switch to <strong>Insert Mode</strong>:</p><ul><li>Press i → insert before cursor</li><li>Press a → append after cursor</li><li>Press o → open new line below</li></ul><p><strong>3. Save &amp; Quit</strong></p><ul><li>:w → save (write)</li><li>:q → quit</li><li>:wq or ZZ → save &amp; quit</li><li>:q! → quit without saving</li></ul><p><strong>4.Navigation</strong></p><ul><li>h → left</li><li>l → right</li><li>j → down</li><li>k → up</li><li>0 → beginning of line</li><li>$ → end of line</li><li>gg → top of file</li><li>G → bottom of file</li></ul><p><strong>5.Editing</strong></p><ul><li>x → delete character</li><li>dd → delete line</li><li>yy → yank (copy) line</li><li>p → paste below cursor</li><li>u → undo</li><li>Ctrl + r → redo</li></ul><p><strong>6.Search</strong></p><ul><li>/word → search forward for &quot;word&quot;</li><li>?word → search backward</li><li>n → next match</li><li>N → previous match</li></ul><p><strong>7.Replace</strong></p><ul><li>:%s/old/new/g</li></ul><p>→ Replace all “old” with “new” in file.</p><p><strong>In summary:</strong></p><ul><li><strong>Flags</strong>: Modify command behavior (ls -l -a)</li><li><strong>Redirection</strong>: Control I/O (e.g., &gt;, &lt;, 2&gt;, |)</li><li><strong>Vim</strong>: A modal editor with commands for navigation, editing, and saving</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=628474142575" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 10 of My #AWS Journey — Cloud Deployment Models]]></title>
            <link>https://medium.com/@bilwalsonu08/day-10-of-my-aws-journey-cloud-deployment-models-58cc0ad33fa8?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/58cc0ad33fa8</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Sun, 24 Aug 2025 06:16:08 GMT</pubDate>
            <atom:updated>2025-08-24T06:16:08.564Z</atom:updated>
            <content:encoded><![CDATA[<h3>Day 10 of My #AWS Journey — Cloud Deployment Models</h3><p>Hello Everyone👋👋</p><p>A <strong>cloud deployment model</strong> defines <strong>where the infrastructure resides</strong>, <strong>who owns/controls it</strong>, and <strong>how services are delivered to users</strong>.<br> AWS (and other cloud providers) support different deployment models based on <strong>business needs, cost, security, and scalability</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jka-Pj4hG0Cwu6_D-qcNew.png" /></figure><p>There are <strong>four major deployment models</strong>:</p><h3>1️⃣ Public Cloud</h3><ul><li>Cloud resources are <strong>owned and operated by a third-party provider</strong> like <strong>AWS, Azure, or GCP</strong>.</li><li>Resources (servers, storage, networking) are <strong>shared across multiple customers</strong>.</li><li>Customers pay on a <strong>pay-as-you-go</strong> basis.</li></ul><h3>2️⃣ Private Cloud</h3><ul><li>Cloud infrastructure <strong>dedicated to a single organization</strong>.</li><li>Can be hosted <strong>on-premises</strong> or by a third-party vendor.</li><li>Gives organizations <strong>full control</strong> over data and resources.</li></ul><h3>3️⃣ Hybrid Cloud</h3><ul><li>A <strong>combination of Public and Private Cloud</strong>.</li><li>Workloads are split: sensitive workloads run in private, scalable workloads run in public.</li><li>Data and applications can move between environments.</li></ul><h3>4️⃣ Community Cloud</h3><ul><li>A <strong>shared cloud infrastructure</strong> for a group of organizations with similar needs (security, compliance, research).</li><li>Managed internally or by a third-party.</li></ul><h3>AWS Context:-</h3><ul><li><strong>Public Cloud</strong> → AWS itself is a public cloud provider.</li><li><strong>Private Cloud on AWS</strong> → AWS Outposts lets enterprises run AWS services <strong>on-premises</strong>.</li><li><strong>Hybrid Cloud</strong> → AWS Direct Connect + VPNs + Outposts connect on-prem with AWS.</li><li><strong>Community Cloud</strong> → AWS GovCloud (for U.S. government workloads).</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58cc0ad33fa8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 9 of My #AWS Journey — Firewall]]></title>
            <link>https://medium.com/@bilwalsonu08/day-9-of-my-aws-journey-firewall-5b8ebd7a7c70?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b8ebd7a7c70</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Sat, 23 Aug 2025 06:44:22 GMT</pubDate>
            <atom:updated>2025-08-23T06:44:22.740Z</atom:updated>
            <content:encoded><![CDATA[<h3>Day 9 of My #AWS Journey — Firewall</h3><p>Hello Everyone👋</p><h3>1. What is a Firewall in AWS?</h3><p>A <strong>firewall</strong> is a security system that controls incoming and outgoing traffic based on defined rules. In AWS, firewalls protect your cloud resources like <strong>EC2 instances, VPCs, and applications</strong> from unauthorized access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/892/1*f2ARCLOFdeUusMcqe9CibA.png" /></figure><h3>Types of Firewalls in AWS</h3><h3>1. Security Groups (SG)</h3><ul><li><strong>Virtual firewall at instance level</strong>.</li><li>Controls <strong>inbound &amp; outbound traffic</strong> for EC2 instances.</li><li>Stateful → if you allow inbound traffic, return traffic is automatically allowed.</li></ul><p>Example Rule: Allow <strong>port 22 (SSH)</strong> from your IP, block all others.</p><h3>2. Network Access Control Lists (NACLs)</h3><ul><li><strong>Firewall at subnet level</strong> (within a VPC).</li><li>Controls traffic for entire subnet.</li><li>Stateless → need to allow both inbound &amp; outbound rules separately.</li></ul><p>Example: Allow HTTP(80) inbound, Deny SSH(22).</p><h3>3. AWS Network Firewall</h3><ul><li>Managed firewall service for VPCs.</li><li>Provides <strong>advanced filtering</strong> (IPs, domains, protocols).</li><li>Deep packet inspection &amp; intrusion prevention.</li><li>Useful for <strong>enterprise-level compliance</strong>.</li></ul><h3>4. Web Application Firewall (WAF)</h3><ul><li>Protects <strong>web applications (Layer 7)</strong>.</li><li>Stops <strong>SQL injection, XSS attacks, bot traffic</strong>.</li><li>Works with CloudFront, API Gateway, and ALB (Application Load Balancer).</li></ul><h3>Real-World Example</h3><p>Imagine you run a <strong>web server on EC2</strong>:</p><ul><li>Security Group → Allows HTTP(80) &amp; HTTPS(443) from public, SSH(22) only from admin IP.</li><li>NACL → Deny all traffic except web and SSH ports.</li><li>WAF → Protects the website from hackers injecting malicious scripts.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b8ebd7a7c70" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Day 8 of My #AWS Journey — Unlocking Secure Access with SSH Keys ”]]></title>
            <link>https://medium.com/@bilwalsonu08/day-8-of-my-aws-journey-unlocking-secure-access-with-ssh-keys-4462c3ddecf5?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/4462c3ddecf5</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Sat, 23 Aug 2025 06:15:18 GMT</pubDate>
            <atom:updated>2025-08-23T06:15:18.457Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>“Day 8 of My #AWS Journey — Unlocking Secure Access with SSH Keys ”</strong></h3><p>Hello Everyone👋</p><h3>1. What are SSH Keys?</h3><p>SSH (Secure Shell) keys are a <strong>pair of cryptographic keys</strong> used to authenticate and securely connect to remote systems like AWS EC2 instances.</p><ul><li><strong>Public Key</strong> → Stored on the server (EC2).</li><li><strong>Private Key</strong> → Kept by the user locally (in .pem or .ppk file).</li></ul><p>Instead of typing a password, the private key is matched with the public key to grant access.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ItkymxzzzsLCP3rDdaXrA.png" /></figure><h3>SSH Key Pair Basics</h3><ul><li><strong>Public Key</strong> → Stored on AWS EC2 instance (~ ~/.ssh/authorized_keys)</li><li><strong>Private Key (.pem file)</strong> → Kept securely by you, used while connecting</li></ul><p>🔑 Without the private key, nobody can log into your instance.</p><h3>2. Why Use SSH Keys in AWS?</h3><ul><li><strong>Stronger Security</strong> → No password-based login.</li><li><strong>Automation Friendly</strong> → Used in DevOps tools (Terraform, Ansible, Jenkins).</li><li><strong>Compliance</strong> → Prevents brute force attacks.</li><li><strong>AWS Integration</strong> → Key pairs are directly supported when launching EC2.</li></ul><h3>3. How SSH Key Pairs Work in AWS</h3><ol><li>You <strong>create a key pair</strong> (via AWS Console or CLI).</li><li>AWS saves the <strong>public key</strong> to the EC2 instance.</li><li>You download the <strong>private key (.pem file)</strong> and keep it safe.</li><li>When you SSH into EC2, AWS checks if the private key matches the stored public key.</li></ol><p>If matched → Secure login.<br> If not → Access denied.</p><h3>4. Creating SSH Keys in AWS</h3><h3>a) From AWS Console</h3><ol><li>Open <strong>EC2 → Key Pairs → Create Key Pair</strong>.</li><li>Choose:</li></ol><ul><li>Name → e.g., aws-key-demo</li><li>File format → .pem (Linux/macOS) or .ppk (Windows PuTTY).</li></ul><ol><li>Download and save the private key securely.</li></ol><h3>b) From AWS CLI</h3><pre>aws ec2 create-key-pair --key-name aws-key-demo --query &#39;KeyMaterial&#39; --output text &gt; aws-key-demo.pem<br>chmod 400 aws-key-demo.pe</pre><h3>5. Connecting to an EC2 Instance with SSH</h3><ol><li>Set correct permissions for the key:</li></ol><pre>chmod 400 aws-key-demo.pem</pre><ol><li>Connect to your instance:</li></ol><pre>ssh -i &quot;aws-key-demo.pem&quot; ec2-user@&lt;Public-IP&gt;</pre><p>Note:</p><ul><li>Use ec2-user for Amazon Linux</li><li>Use ubuntu for Ubuntu instances</li></ul><h3>6. Best Practices for SSH Keys</h3><p>🔹 Use <strong>different keys</strong> for different projects/environments<br> 🔹 Keep private keys in a <strong>secure location</strong> (never share them)<br> 🔹 Rotate keys regularly<br> 🔹 Remove unused keys from EC2 instances<br> 🔹 Consider <strong>AWS Systems Manager Session Manager</strong> as a safer alternative (no SSH keys required!)</p><h3>7. Real-World Example</h3><p>Imagine you launched a <strong>production EC2 instance</strong>. Instead of setting a password, AWS will only let you connect with the correct private key. This ensures:</p><ul><li>Even if someone gets the public IP, they can’t brute-force login.</li><li>Only authorized team members with the private key can access.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4462c3ddecf5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Day 7 of My #AWS Journey — Mastering User Administration & File Permissions in Linux”]]></title>
            <link>https://medium.com/@bilwalsonu08/day-7-of-my-aws-journey-mastering-user-administration-file-permissions-in-linux-07611840640f?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/07611840640f</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 10:30:18 GMT</pubDate>
            <atom:updated>2025-08-20T10:30:18.372Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>“Day 7 of My #AWS Journey — Mastering User Administration &amp; File Permissions in Linux”</strong></h3><p>Hello Everyone👋👋</p><p>When working on <strong>AWS EC2 Linux instances</strong> (Ubuntu or Amazon Linux), two key tasks for system admins are:</p><ol><li><strong>User Administration</strong> — managing users, groups, and privileges.</li><li><strong>File Permissions</strong> — controlling who can access, modify, or execute files and directories.</li></ol><h3>1. User Administration</h3><h3>What is User Administration?</h3><p>User administration in Linux refers to the <strong>creation, management, and removal of users and groups</strong>, and assigning them the proper permissions.<br> In AWS Linux (Ubuntu or Amazon Linux EC2):</p><ul><li>Each EC2 instance comes with a <strong>default system user</strong> (ubuntu or ec2-user).</li><li>Additional users should be created for team members, instead of sharing the same login.</li><li>Permissions should follow the <strong>Principle of Least Privilege</strong> (give only required access).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/425/1*Y82t8o2Knt9D8lMidAdQPw.png" /></figure><h3>Key User Administration Tasks</h3><ol><li><strong>Create a New User</strong></li></ol><ul><li>sudo adduser devuse</li><li>Creates a user devuser with home directory /home/devuser.</li></ul><p><strong>2. Set User Password</strong></p><ul><li>sudo passwd devuser</li><li>Assigns a login password (useful if password login is enabled).</li></ul><p><strong>3. Grant Admin (Sudo) Rights</strong></p><ul><li>On <strong>Ubuntu</strong>:</li><li>sudo usermod -aG sudo devuser</li><li>On <strong>Amazon Linux</strong>:</li><li>sudo usermod -aG wheel devuser</li></ul><p>🔹 Difference: Ubuntu uses <strong>sudo group</strong>, Amazon Linux uses <strong>wheel group</strong>.</p><p><strong>4. Switch to Another User</strong></p><ul><li>su - devuse</li></ul><p><strong>5. Delete a User</strong></p><ul><li>Ubuntu:</li><li>sudo deluser devuser</li><li>Amazon Linux:</li><li>sudo userdel devuser</li></ul><p>Add -r to delete home directory too:</p><ul><li>sudo userdel -r devuser</li></ul><p><strong>6. Group Management</strong></p><ul><li>Create a group:</li><li>sudo groupadd developers</li><li>Add user to a group:</li><li>sudo usermod -aG developers devuser</li><li>Show user groups:</li><li>groups devuser</li></ul><h3>2. File Permissions</h3><h3>What are File Permissions?</h3><p>Linux is a <strong>multi-user OS</strong>. File permissions decide:</p><ul><li>Who can <strong>read</strong> a file (r)</li><li>Who can <strong>write/modify</strong> a file (w)</li><li>Who can <strong>execute</strong> a file/script (x)</li></ul><p>Permissions apply to:</p><ol><li><strong>Owner</strong> → User who created or owns the file</li><li><strong>Group</strong> → Users in the same group</li><li><strong>Others</strong> → Everyone else</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/1*bJRHn0wWDnXZmNJ31Oc7Rg.png" /></figure><h3>File Permission Commands</h3><ol><li><strong>Check File Permissions</strong></li></ol><ul><li>ls -l</li></ul><p>Example:</p><ul><li>-rw-r--r-- 1 ec2-user ec2-user 1200 Aug 20 test.txt</li><li>rw- → Owner has read &amp; write</li><li>r-- → Group has read only</li><li>r-- → Others have read only</li></ul><p><strong>2. Change File Owner</strong></p><ul><li>sudo chown devuser:developers test.txt</li><li>Owner becomes devuser, group becomes developers.</li></ul><p><strong>3. Change File Permissions</strong></p><ul><li>chmod 755 script.sh</li></ul><p>🔹 Meaning:</p><ul><li>Owner = <strong>7 (rwx)</strong> → full rights</li><li>Group = <strong>5 (r-x)</strong> → read + execute</li><li>Others = <strong>5 (r-x)</strong> → read + execute</li></ul><p><strong>4. Change Group Ownership</strong></p><ul><li>sudo chgrp developers project/</li></ul><h3>* Special Permissions</h3><ol><li><strong>SetUID (s)</strong> → Run as file owner.</li></ol><ul><li>chmod 4755 script.sh</li></ul><p><strong>2. SetGID (s)</strong> → Run as group.</p><ul><li>chmod 2755 project/</li></ul><p><strong>3. Sticky Bit (t)</strong> → Only file owner can delete in shared directory.</p><ul><li>chmod +t /shared_folder</li></ul><h3>* AWS-Specific Best Practices</h3><ol><li><strong>Never use </strong><strong>root user directly</strong> – always log in as ec2-user or ubuntu and use sudo.</li><li><strong>Use IAM roles</strong> to give AWS resource access, not root credentials.</li><li><strong>Each person should have their own Linux user account</strong> (with SSH key)</li><li><strong>Secure PEM file</strong> used for login:</li></ol><ul><li>chmod 400 my-key.pem</li></ul><p><strong>5. Enable CloudTrail &amp; CloudWatch</strong> to track user activity.</p><h3>✅ Quick Recap</h3><ul><li><strong>User Administration</strong> → adduser, passwd, usermod, deluser/userdel, groupadd</li><li><strong>File Permissions</strong> → ls -l, chmod, chown, chgrp</li><li><strong>Special Permissions</strong> → SetUID, SetGID, Sticky Bit</li><li><strong>AWS Best Practice</strong> → Least privilege, IAM roles, individual users with SSH keys</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07611840640f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Day 6 of My #AWS Journey — Linux: Unlocking the Cloud’s Engine”]]></title>
            <link>https://medium.com/@bilwalsonu08/day-6-of-my-aws-journey-linux-unlocking-the-clouds-engine-020a7fbb735d?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/020a7fbb735d</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 08:25:12 GMT</pubDate>
            <atom:updated>2025-08-20T08:25:12.289Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Day 6 of My #AWS Journey — Linux: Unlocking the Cloud’s Engine”</h3><p><strong>Hello Everyone👋</strong></p><p>Today, I explored <strong>Linux</strong>, the backbone of most cloud systems, including AWS.<br> Linux is an <strong>open-source operating system</strong> built around the <strong>kernel</strong> and is widely used because of its <strong>stability, security, and flexibility</strong>.</p><h3>1. What is Linux?</h3><ul><li><strong>Open-source Operating System</strong> built on the <strong>Linux Kernel</strong> (created by Linus Torvalds in 1991).</li><li>Acts as a <strong>bridge between hardware and software</strong>.</li><li>Unlike proprietary systems (Windows, macOS), Linux is <strong>free, customizable, and secure</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*zB3WtiWwkSCciL7mxZ8B8g.png" /></figure><h3>2. Why Linux is Important in AWS and Cloud Computing</h3><ol><li><strong>Dominates the Cloud</strong> — More than 90% of public cloud workloads run on Linux.</li><li><strong>Lightweight &amp; Scalable</strong> — Ideal for spinning up thousands of EC2 instances.</li><li><strong>Secure by Design</strong> — Built-in permission model, SELinux, firewalls, and auditing.</li><li><strong>Automation Friendly</strong> — Shell scripting + tools like Ansible, Terraform, and AWS CLI rely on Linux.</li><li><strong>Flexibility</strong> — You can choose <strong>Amazon Linux 2</strong>, Ubuntu, CentOS, RHEL, or SUSE for your workloads.</li><li><strong>DevOps Ecosystem</strong> — CI/CD pipelines, Docker, Kubernetes, and monitoring tools are Linux-native.</li></ol><h3>3. Key Linux Concepts for AWS</h3><ul><li><strong>File System Structure</strong>:</li><li>/home → User files</li><li>/etc → Configuration files</li><li>/var → Logs, temporary files</li><li>/bin, /sbin → System binaries</li><li>/root → Root user’s home directory</li><li><strong>Users &amp; Permissions</strong>:</li><li>Every file has <strong>Owner, Group, Others</strong>.</li><li>Permissions: r (read), w (write), x (execute).</li><li>Managed using chmod, chown, and groups.</li><li><strong>Package Management</strong>:</li><li>yum, dnf (RHEL, CentOS, Amazon Linux)</li><li>apt (Debian, Ubuntu)</li><li><strong>System Services</strong>:</li><li>Managed using systemctl (start, stop, enable services).</li><li><strong>Process Management</strong>:</li><li>ps, top, kill → monitor and manage processes.</li><li><strong>Networking</strong>:</li><li>ifconfig, ip addr, ping, netstat, ss</li><li>Crucial for EC2 network troubleshooting.</li></ul><h3>4. Essential Linux Commands for Cloud Engineers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*HnlosvLnX2HGhzwW0uc3ew.png" /></figure><h3>5. Real AWS Example: Using Linux on EC2</h3><ul><li>When you launch an <strong>EC2 instance</strong> (Amazon Linux 2 or Ubuntu), you:</li></ul><ol><li><strong>SSH into the instance</strong> → ssh -i key.pem ec2-user@public-ip</li><li>Navigate directories, install packages, run scripts.</li><li>Secure the system by updating packages (sudo yum update -y).</li><li>Configure web servers (Apache, Nginx) or app servers.</li></ol><h3>6. Key Takeaway</h3><p>Linux is not just an OS; it’s the <strong>foundation of AWS and modern cloud computing</strong>.<br> Mastering Linux skills — command-line navigation, permissions, networking, package management, and shell scripting — makes you a <strong>stronger AWS cloud engineer</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=020a7fbb735d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Day 5 of My #AWS Journey — “AWS Global Infrastructure”]]></title>
            <link>https://medium.com/@bilwalsonu08/day-5-of-my-aws-journey-aws-global-infrastructure-4e8e582a7150?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e8e582a7150</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Tue, 19 Aug 2025 06:47:07 GMT</pubDate>
            <atom:updated>2025-08-19T06:47:07.396Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Day 5 of My #AWS Journey — “AWS Global Infrastructure”</h3><p>Hello Guyss👋👋</p><h3>1. Definition of AWS Global Infrastructure</h3><p>Cloud global infrastructure refers to the <strong>physical and virtual network of data centers, servers, networks, and services</strong> that a cloud provider operates across the world to deliver computing resources, storage, and services globally.</p><p>It’s the backbone that allows users to access cloud services <strong>anywhere, anytime</strong>, with high availability, low latency, and scalability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/893/1*Q2pj460836f3_kXiu415eQ.png" /></figure><h3>*Why AWS Global Infrastructure is Important in Cloud Computing</h3><p>In cloud computing, <strong>global infrastructure is crucial because it ensures reliable, high-performance, and scalable services worldwide</strong>. By distributing resources across multiple regions, Availability Zones, and edge locations, cloud providers reduce latency, enable rapid scaling, and provide disaster recovery in case of failures. It also ensures data security, regulatory compliance, and cost efficiency while allowing businesses to deploy applications globally and innovate faster without investing in physical infrastructure</p><h3>2. Core Components</h3><h3>A. Regions</h3><ul><li>A <strong>region</strong> is a <strong>geographical area</strong> where the cloud provider has one or more data centers.</li><li>Example:</li><li>AWS: US East (N. Virginia), Asia Pacific (Mumbai)</li><li>Azure: Central India, West US</li></ul><h3>B. Availability Zones (AZs)</h3><ul><li>A region is divided into <strong>Availability Zones</strong>, which are <strong>physically separate data centers</strong> within the same region.</li><li>Characteristics:</li><li>Redundant power, networking, and cooling.</li><li>Connected via <strong>low-latency links</strong>.</li><li>Purpose: <strong>High availability and fault tolerance</strong>.</li><li>Example: AWS’s <strong>US East (N. Virginia)</strong> has 6 AZs.</li></ul><h3>C. Edge Locations / Points of Presence (PoPs)</h3><ul><li>Edge locations are smaller sites <strong>closer to end users</strong>.</li><li>Used for:</li><li>Content delivery (CDN)</li><li>DNS queries</li></ul><h3>D. Data Centers</h3><ul><li>Physical buildings hosting <strong>servers, storage, and networking hardware</strong>.</li><li>Contain:</li><li>Compute servers (VMs, containers)</li><li>Storage systems (block, file, object storage)</li></ul><h3>E. Network Backbone</h3><ul><li>Cloud providers maintain <strong>private global fiber networks</strong>.</li><li>Connect regions, AZs, and edge locations.</li></ul><h3>3. Key Characteristics of Global Cloud Infrastructure</h3><p>FeatureDescription<strong>Scalability</strong>Add/remove resources as needed across the global <strong>High Availability</strong>AZs and replication ensure uptime (99.99% SLA)<strong>Low Latency</strong>Edge locations serve content close to users<strong>Disaster Recovery</strong>Multi-region deployment protects against failures<strong>Security &amp; Compliance</strong>Global compliance standards (ISO, GDPR, HIPAA)</p><h3>4. Examples of Global Infrastructure by Major Providers</h3><h3>AWS</h3><ul><li>31 regions, 100+ AZs, 400+ edge locations.</li><li>Global backbone network for low-latency communication.</li><li>Services deployed regionally but accessible globally.</li></ul><h3>Microsoft Azure</h3><ul><li>70+ regions, 170+ edge locations.</li><li>Focus on hybrid cloud with Azure Stack.</li><li>Strong compliance and enterprise focus.</li></ul><h3>Google Cloud (GCP)</h3><ul><li>35 regions, 106 zones, 150+ edge PoPs.</li><li>Emphasis on AI/ML and fast global networking.</li></ul><h3>Oracle Cloud</h3><ul><li>44 regions, multiple ADs (Availability Domains) per region.</li><li>High-performance Exadata Cloud infrastructure across regions.</li></ul><h3>5. How Global Infrastructure Works Together</h3><ol><li><strong>User requests</strong> data or service.</li><li><strong>DNS directs</strong> request to the nearest edge location.</li><li>If needed, request is sent via <strong>private cloud backbone</strong> to the closest AZ.</li><li>AZ handles <strong>compute/storage/network services</strong>.</li><li>If one AZ fails, traffic is <strong>automatically routed</strong> to another AZ in the region.</li><li>For extreme failures, multi-region replication ensures <strong>disaster recovery</strong>.</li></ol><h3>6. Benefits</h3><ul><li><strong>Global Reach:</strong> Serve users worldwide without building physical infrastructure locally.</li><li><strong>Resilience:</strong> Multiple AZs and regions reduce downtime.</li><li><strong>Performance:</strong> Low-latency access using edge locations.</li><li><strong>Cost Efficiency:</strong> Pay-as-you-go model reduces infrastructure investment.</li><li><strong>Security &amp; Compliance:</strong> Centralized monitoring and compliance certifications.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e8e582a7150" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Day 5 of My #AWS Journey — “Launching and Managing EC2 Instances in AWS”]]></title>
            <link>https://medium.com/@bilwalsonu08/day-5-of-my-aws-journey-launching-and-managing-ec2-instances-in-aws-30899bf65442?source=rss-efb7fca05e75------2</link>
            <guid isPermaLink="false">https://medium.com/p/30899bf65442</guid>
            <dc:creator><![CDATA[Sonu Bilwal]]></dc:creator>
            <pubDate>Fri, 15 Aug 2025 07:35:35 GMT</pubDate>
            <atom:updated>2025-08-15T07:35:35.307Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Day 5 of My #AWS Journey — “Launching and Managing EC2 Instances in AWS”</h3><p>Hello Everyone👋👋</p><h3>1. What EC2 Is?</h3><ul><li><strong>Elastic</strong> → You can scale up or down the number and size of instances as needed.</li><li><strong>Compute</strong> → It gives you processing power (CPU, RAM, storage) to run applications.</li><li><strong>Cloud</strong> → It’s hosted on AWS infrastructure, so you don’t need physical servers.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*SAbr-AAbd3qTxKvnUsAM1Q.png" /></figure><h3>* What is an EC2 Instance?</h3><p>An <strong>EC2 instance</strong> is a virtual server hosted in the AWS cloud. It lets you run applications without buying and maintaining physical hardware. You can choose the CPU, RAM, storage, operating system, and network settings according to your needs.</p><h3>2. Uses of EC2:-</h3><ol><li><strong>Website Hosting</strong></li></ol><ul><li>Run web servers like Apache, Nginx, or IIS to serve websites and apps.</li></ul><p><strong>2. Application Hosting</strong></p><ul><li>Deploy business apps, APIs, or back-end systems.</li></ul><p><strong>3. Development &amp; Testing</strong></p><ul><li>Create temporary servers for coding, debugging, and QA testing.</li></ul><p><strong>4. Big Data Processing</strong></p><ul><li>Handle analytics, machine learning, and large datasets.</li></ul><p><strong>5. Game Servers</strong></p><ul><li>Host online multiplayer games with low latency.</li></ul><p><strong>6. Disaster Recovery</strong></p><ul><li>Keep backup servers ready to run in case your main system fails.</li></ul><p><strong>7. High-Performance Computing (HPC)</strong></p><ul><li>Run heavy simulations, rendering, or scientific workloads.</li></ul><h3>3. Navigating to EC2 Service</h3><ul><li>In the search bar, type <strong>EC2</strong> and click it.</li><li>You’ll land on the <strong>EC2 Dashboard</strong>, where you can see:</li></ul><p>• Number of running instances</p><ul><li>Security groups</li><li>Key pairs</li><li>Elastic IP addresses</li></ul><h3>4. Launching an EC2 Instance</h3><h4>Step-by-step</h4><ol><li><strong>Click “Launch Instance”</strong>.</li><li><strong>Name your instance</strong> (e.g., <em>MyFirstEC2</em>).</li><li><strong>Choose an Amazon Machine Image (AMI)</strong>:</li></ol><ul><li>Amazon Linux, Ubuntu, Windows, etc.</li></ul><p><strong>4. Choose an Instance Type</strong>:</p><ul><li><em>t2.micro</em> is free-tier eligible.</li></ul><p><strong>5. Configure Key Pair</strong>:</p><ul><li>Create or choose an existing .pem key for SSH login.</li></ul><p><strong>6. Configure Network &amp; Security</strong>:</p><ul><li>Select a <strong>VPC</strong> and <strong>subnet</strong>.</li><li>Open port <strong>22</strong> for SSH (Linux) or <strong>3389</strong> for RDP (Windows).</li></ul><p><strong>7. Configure Storage</strong>:</p><ul><li>Default is 8 GB (you can increase if needed)</li></ul><p><strong>8. Review &amp; Launch</strong>:</p><ul><li>Click <strong>Launch Instance</strong>.</li></ul><h3>5. Connecting to Your Instance:-</h3><ul><li><strong>Linux EC2</strong>: Use an SSH client or terminal command:</li><li>ssh -i mykey.pem ec2-user@&lt;Public-IP&gt;</li><li><strong>Windows EC2</strong>: Use Remote Desktop (RDP) with the .rdp file from AWS.</li></ul><h3>6. Working with Your EC2 Instance</h3><ul><li>Install software, deploy apps, or run scripts.</li><li>Update OS packages:</li><li>sudo yum update -y # For Amazon Linux</li><li>sudo apt update &amp;&amp; sudo apt upgrade -y # For Ubuntu</li></ul><h3>7. Stopping, Starting, or Terminating</h3><ul><li><strong>Stop</strong>: Saves instance state but billing for storage continues.</li><li><strong>Start</strong>: Restarts a stopped instance.</li><li><strong>Terminate</strong>: Deletes the instance (data loss unless backed up).</li></ul><h3>8. Security Best Practices</h3><ul><li>Use <strong>strong key pairs</strong> and store them safely.</li><li>Restrict <strong>security group rules</strong> to trusted IPs.</li><li>Keep OS and software <strong>up-to-date</strong>.</li><li>Use IAM roles instead of storing credentials on the instance.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30899bf65442" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>