<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>VPC on Daman Arora</title>
    <link>https://damanarora.netlify.app/tags/vpc/</link>
    <description>Recent content in VPC on Daman Arora</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 18 May 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://damanarora.netlify.app/tags/vpc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS VPC: Your Private Network in the Cloud</title>
      <link>https://damanarora.netlify.app/posts/aws-vpc-private-network/</link>
      <pubDate>Mon, 18 May 2026 12:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-vpc-private-network/</guid>
      <description>Every resource you run in AWS — an EC2 instance, an RDS database, a load balancer — sits inside a network. That network is the VPC: a private, isolated slice of the AWS cloud that you control. Understanding it means understanding how traffic actually reaches your resources, and how you keep them protected. The single most important distinction to walk away with is security groups versus NACLs, so that gets special attention below.</description>
    </item>
    
  </channel>
</rss>
