<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cost Analysis on Patrick Contes blog</title><link>https://pconte.tech/tags/cost-analysis/</link><description>Recent content in Cost Analysis on Patrick Contes blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 08 Jul 2025 22:00:32 +1000</lastBuildDate><atom:link href="https://pconte.tech/tags/cost-analysis/index.xml" rel="self" type="application/rss+xml"/><item><title>Designing Egress in AWS</title><link>https://pconte.tech/p/designing-egress-in-aws/</link><pubDate>Tue, 08 Jul 2025 22:00:32 +1000</pubDate><guid>https://pconte.tech/p/designing-egress-in-aws/</guid><description>
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;AWS networking is fairly straightforward in a small setup. As a singular environment, you will generally have a single VPC that consists of:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Subnets&lt;/li&gt;
&lt;li&gt;Route tables&lt;/li&gt;
&lt;li&gt;Network ACLs (NACLs)&lt;/li&gt;
&lt;li&gt;Security groups&lt;/li&gt;
&lt;li&gt;An Internet Gateway (IGW)&lt;/li&gt;
&lt;li&gt;NAT Gateway(s)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;There are other components, and even some of the ones mentioned here may not be required. You might have a single subnet for all of your resources. Likewise, a NAT Gateway may not even be necessary (this is rare — and anyone exposing private workloads to the internet unnecessarily is not following best practice).&lt;/p&gt;</description></item></channel></rss>