<?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"><channel><title><![CDATA[Arijit's DevOps & Cloud Notes]]></title><description><![CDATA[Arijit's DevOps & Cloud Notes]]></description><link>https://arijitkumarpandab.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/67947ff6ca7b2e9956f5b65b/1c8ebdcd-7ac3-483c-8a7b-14769c3b42f9.jpg</url><title>Arijit&apos;s DevOps &amp; Cloud Notes</title><link>https://arijitkumarpandab.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 15:43:55 GMT</lastBuildDate><atom:link href="https://arijitkumarpandab.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[AWS VPC Explained: The Network Shield Holding Your Entire Cloud Infrastructure]]></title><description><![CDATA[A practical, production-focused guide to Amazon VPC. Learn how subnets, NAT/Internet Gateways, Route Tables, and firewalls work to secure AWS.]]></description><link>https://arijitkumarpandab.hashnode.dev/aws-vpc-explained-the-network-shield-holding-your-entire-cloud-infrastructure</link><guid isPermaLink="true">https://arijitkumarpandab.hashnode.dev/aws-vpc-explained-the-network-shield-holding-your-entire-cloud-infrastructure</guid><category><![CDATA[AWS]]></category><category><![CDATA[Devops]]></category><category><![CDATA[networking]]></category><category><![CDATA[Cloud Computing]]></category><category><![CDATA[vpc]]></category><dc:creator><![CDATA[Arijit Kumar Pandab]]></dc:creator><pubDate>Mon, 16 Nov 2026 16:11:17 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/67947ff6ca7b2e9956f5b65b/14c98dbc-2aa4-4a2d-a8cb-9d6a40b5151c.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Before you launch a single EC2 instance, spin up an EKS cluster, or create an RDS database, everything starts with one service: Amazon VPC (Virtual Private Cloud).</p>
<p>In the AWS world, a VPC isn't just "networking." It is your isolated data center inside AWS—the outer boundary and security shield that contains your compute, storage, and databases, while strictly controlling what gets in and what goes out. If you misconfigure your VPC, your application is either completely unreachable or dangerously exposed to the public internet.</p>
<p>Here is a straightforward, production-focused breakdown of every core VPC component and how they work together to protect your infrastructure.</p>
<ol>
<li>VPC &amp; CIDR Block (Your Private Territory) A VPC is your logically isolated virtual network within an AWS Region. When you create one, you assign it an IP address range using a CIDR block (for example, 10.0.0.0/16, which gives you 65,536 private IP addresses). Every server, load balancer, and database you launch inside this VPC gets an IP from this pool.</li>
<li>Subnets: Public vs. Private (The Isolation Layers) You never dump all your resources into one flat network. Instead, you slice your VPC CIDR block into smaller chunks called Subnets, each tied to a specific Availability Zone (AZ) for high availability:</li>
</ol>
<p>Public Subnets: Resources here can reach the internet directly. This is where you place public-facing Load Balancers (ALB) and Bastion hosts—not your application servers or databases.</p>
<p>Private Subnets: Completely isolated from direct inbound internet traffic. Your EC2 app servers, ECS/EKS worker nodes, and RDS databases live here behind the shield.</p>
<ol start="3">
<li>Internet Gateway (IGW) (The Front Door) An Internet Gateway is what connects your VPC to the public internet. Without an IGW attached to your VPC, nothing inside can talk to the outside world, and no user can reach your app. Attaching an IGW is what turns a subnet with a route to it into a "Public Subnet."</li>
<li>Route Tables (The Traffic GPS) Subnets don't know where to send packets on their own—Route Tables decide where network traffic goes. Every subnet is associated with a route table:</li>
</ol>
<p>A Public Route Table has a rule (0.0.0.0/0 -&gt; igw-xxxx) sending internet-bound traffic straight to the Internet Gateway.</p>
<p>A Private Route Table has no route to the IGW, ensuring external internet requests can never reach your private workloads directly.</p>
<ol start="5">
<li>NAT Gateway (One-Way Outbound Access) Your private servers still need to download OS patches, pull Docker images, or call third-party APIs—without letting anyone on the internet initiate a connection back to them. A NAT Gateway sits inside a public subnet and lets instances in private subnets initiate outbound internet traffic while blocking all unsolicited inbound connections.</li>
<li>Security Groups vs. Network ACLs (The Dual Firewall Shield) AWS gives you two layers of defense inside your VPC, and understanding the difference is a classic interview question and a daily operational must:</li>
</ol>
<p>Security Groups (Instance-Level Firewall): Acts as a virtual firewall directly around your EC2 instances, ENIs, or RDS databases. They are stateful (if you allow inbound traffic on port 443, the return traffic is automatically allowed out) and only support Allow rules.</p>
<p>Network ACLs / NACLs (Subnet-Level Firewall): Sits at the boundary of your entire subnet. Unlike Security Groups, NACLs are stateless (you must explicitly configure both inbound and outbound rules) and support both Allow and Deny rules—making them ideal for blocking malicious IP ranges before traffic ever reaches an instance.</p>
<ol start="7">
<li>VPC Endpoints (Staying Off the Public Internet) Normally, when a private EC2 instance talks to S3 or DynamoDB, traffic leaves your VPC over the public internet via a NAT Gateway—costing you data-processing fees and exposing traffic outside the AWS backbone. VPC Endpoints (Gateway Endpoints for S3/DynamoDB, Interface Endpoints via AWS PrivateLink for services like Secrets Manager or ECR) keep all traffic strictly inside the private AWS network.</li>
<li>VPC Peering &amp; Transit Gateway (Connecting Multiple VPCs) As your architecture grows across environments (dev, staging, prod), you need VPCs to talk privately:</li>
</ol>
<p>VPC Peering: A direct one-to-one private network link between two VPCs. Simple for two or three VPCs, but becomes a management nightmare at scale because peering is non-transitive.</p>
<p>AWS Transit Gateway: A central cloud router acting as a hub-and-spoke network, connecting dozens of VPCs and on-premises data centers cleanly without complex peering meshes.</p>
<ol start="9">
<li>VPC Flow Logs (Your Network CCTV) When packets get dropped and you don't know whether a Security Group, NACL, or Route Table is blocking them, VPC Flow Logs capture metadata about all IP traffic going in and out of your network interfaces and ship it straight to CloudWatch Logs or S3 for troubleshooting and security audits.</li>
</ol>
<p>How the Shield Works End-to-End Picture a typical production request hitting your application:</p>
<p>A user request enters through the Internet Gateway into a Public Subnet, hitting an Application Load Balancer protected by a Security Group (allowing port 443).</p>
<p>The ALB forwards the request to your backend containers sitting safely inside a Private Subnet (guarded by its own NACL and Security Group allowing traffic only from the ALB).</p>
<p>Your app fetches database credentials privately via a VPC Endpoint to Secrets Manager, queries RDS in an isolated database subnet, and pulls updates through a NAT Gateway—never exposing your core infrastructure to the public internet.</p>
<p>Master these nine building blocks, and AWS networking stops feeling intimidating. You aren't just wiring up IP addresses—you are designing the perimeter that keeps your entire cloud environment secure.</p>
]]></content:encoded></item><item><title><![CDATA[You Don’t Need to Learn 200+ AWS Services: The Exact 17 That Actually Make You a Cloud Engineer]]></title><description><![CDATA[If you open the AWS Management Console today, you are staring at more than 240 services. Trying to learn all of them is impossible—and honestly, a waste of…]]></description><link>https://arijitkumarpandab.hashnode.dev/you-don-t-need-to-learn-200-aws-services-the-exact-17-that-actually-make-you-a-cloud-engineer</link><guid isPermaLink="true">https://arijitkumarpandab.hashnode.dev/you-don-t-need-to-learn-200-aws-services-the-exact-17-that-actually-make-you-a-cloud-engineer</guid><dc:creator><![CDATA[Arijit Kumar Pandab]]></dc:creator><pubDate>Thu, 12 Nov 2026 13:00:11 GMT</pubDate><content:encoded><![CDATA[<p>If you open the AWS Management Console today, you are staring at more than 240 services. Trying to learn all of them is impossible—and honestly, a waste of time. Even in production environments, 90% of day-to-day cloud engineering revolves around a remarkably small subset of tools.</p>
<p>Whether you are preparing for DevOps/Cloud interviews or trying to survive your first production on-call shift, you don't need to memorize the entire AWS catalog. You just need the right sequence.</p>
<p>Here is the exact roadmap I rely on—broken down into what you need <strong>before</strong> AWS, what gets you <strong>hired and productive</strong>, and what turns you into a <strong>well-rounded Cloud Engineer</strong>.</p>
<h3>Step 0: Don't Touch AWS Until You Know Linux</h3>
<p>Before you spin up a single cloud resource, learn <strong>Linux</strong>. Everything in the cloud runs on it, and if you don't understand SSH, file permissions, systemd, DNS resolution, and basic networking commands, AWS will feel like a black box you can't troubleshoot when things break.</p>
<h3>Tier 1: The Core 7 (Daily Work &amp; Standard Interviews)</h3>
<p>If you master these seven services deeply, you can handle daily operations and pass the vast majority of regular cloud and DevOps interviews:</p>
<ol>
<li><strong>EC2</strong> – Where your actual compute lives when you need full control over the OS and runtime.</li>
<li><strong>EBS</strong> – The persistent hard drives keeping your EC2 data alive across reboots and snapshots.</li>
<li><strong>VPC</strong> – Your private network perimeter where you control subnets, routing, and who gets in or out.</li>
<li><strong>S3</strong> – Your default dumping ground for application assets, logs, backups, and Terraform state files.</li>
<li><strong>IAM</strong> – The gatekeeper deciding which user or service is allowed to touch what—and where most security mistakes happen.</li>
<li><strong>CloudWatch</strong> – Your eyes and ears when production starts throwing errors or spiking CPU at 2 AM.</li>
<li><strong>Lambda</strong> – Your go-to for running quick automation scripts and event glue without managing a server.</li>
</ol>
<h3>Tier 2: The Next 10 (Becoming a Complete Cloud Engineer)</h3>
<p>Once the Core 7 are second nature, adding these ten services is what takes you from managing basic servers to architecting resilient, production-grade systems:</p>
<ol start="8">
<li><strong>RDS</strong> – Managed relational databases so you aren't manually patching PostgreSQL or MySQL on an EC2 box.</li>
<li><strong>DynamoDB</strong> – Predictable, single-digit millisecond NoSQL storage when relational schemas become a bottleneck.</li>
<li><strong>Route 53</strong> – The DNS layer connecting human-readable domain names to your cloud infrastructure.</li>
<li><strong>ELB</strong> – The traffic cop distributing incoming requests across healthy instances without dropping user connections.</li>
<li><strong>SQS</strong> – The shock absorber between microservices so a traffic spike doesn't crash your backend.</li>
<li><strong>SNS</strong> – Your instant broadcast system for triggering alerts, emails, and downstream event workflows.</li>
<li><strong>KMS</strong> – The cryptographic backbone handling encryption keys across your storage, databases, and secrets.</li>
<li><strong>Secrets Manager</strong> – Keeps database passwords and API keys out of your Git repositories and rotates them automatically.</li>
<li><strong>ECS</strong> – The simplest way to run Docker containers in production without drowning in cluster management.</li>
<li><strong>EKS</strong> – Managed Kubernetes for when your team genuinely needs complex container orchestration at scale.</li>
</ol>
<h3>How They Fit Together in Real Life</h3>
<p>Notice that none of these exist in isolation. In a standard production setup, a user hits <strong>Route 53</strong>, gets routed through an <strong>ELB</strong> into containers running on <strong>ECS/EKS</strong> (inside a <strong>VPC</strong>), reads data from <strong>RDS</strong> using credentials pulled from <strong>Secrets Manager</strong> (encrypted by <strong>KMS</strong>), pushes background jobs to <strong>SQS</strong>, and streams logs to <strong>CloudWatch</strong>—all governed by <strong>IAM</strong>.</p>
<p>Stop chasing every new service AWS announces. Master Linux, lock down the Core 7, and build real projects with the Next 10. That alone will put you ahead of most candidates in the room.</p>
]]></content:encoded></item></channel></rss>