<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking Essentials on 🏠</title><link>https://tofl.github.io/docs/2-networking-essentials/</link><description>Recent content in Networking Essentials on 🏠</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://tofl.github.io/docs/2-networking-essentials/index.xml" rel="self" type="application/rss+xml"/><item><title>3. VPC Fundamentals</title><link>https://tofl.github.io/docs/2-networking-essentials/vpc-fundamentals/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/2-networking-essentials/vpc-fundamentals/</guid><description>&lt;h2 id="vpc-fundamentals"&gt;VPC Fundamentals&lt;a class="anchor" href="#vpc-fundamentals"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Amazon Virtual Private Cloud (VPC) lets you launch AWS resources inside a logically isolated virtual network that you define. Think of it as your own private data center within AWS — you control the IP address ranges, subnets, routing, and access rules. The core problem it solves is &lt;strong&gt;network isolation&lt;/strong&gt;: without a VPC, your resources would be exposed on a flat shared network. With a VPC, you decide what&amp;rsquo;s reachable from the internet, what&amp;rsquo;s reachable only internally, and what can talk to what.&lt;/p&gt;</description></item><item><title>4. Route 53</title><link>https://tofl.github.io/docs/2-networking-essentials/route-53/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/2-networking-essentials/route-53/</guid><description>&lt;h2 id="route-53"&gt;Route 53&lt;a class="anchor" href="#route-53"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Route 53 is AWS&amp;rsquo;s managed DNS (Domain Name System) service. DNS is the internet&amp;rsquo;s phone book — it translates human-readable domain names like &lt;code&gt;api.myapp.com&lt;/code&gt; into IP addresses that computers use to route traffic. Route 53 goes beyond basic DNS by adding health checking, traffic routing logic, and deep integration with AWS services. For developers, understanding Route 53 at an awareness level is enough to wire up custom domains, configure failover, and reason about how traffic reaches your application.&lt;/p&gt;</description></item></channel></rss>